-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide documentation on $PS1 customization #6
Comments
Two links that might become useful: |
I would more recommend implementing an elaborated $PS1 for the users, thus they have nice features like colours, time and directories in it. We can document these changes and provide also links like the suggest. |
$PS1 is something heavily influenced by personal taste. Finding THE right default is IMHO not feasible. We won't even manage to come to a common default within our office (complete dir paths or only last crumb? color scheme for dark or bright background? pastels versus bright colors? github information yes/no, which?). All a matter of taste and not worth the effort. Instead I'd rather stick to what it is now and empower the user to
|
As far as I saw it, the default is just We may want to discuss details with the whole office and agree to something. I tend for at least some color, machine name, and full path. Git branch and/or modification will anyways just be shown in git repos (conda does the same automatically with their envs). and time may also be nice. |
This is the default IMHO, isn't it? At least it is for an unprivileged user sberger on submit01 that did not do anything in his .bashrc nor .bash_profile: [sberger@submit01 .ssh]$ So, we have $USER, As it is a matter of taste, I'd rather put up like 10 sensible example and people that want more than the above jost copy/paste the respective $PS1 from the documentation to .bash_profile and at that very moment also learn something about .bashrc and .bash_profile files - common root causes of troubles. |
Include stuff like: .bashrc |
Is your feature request related to a current shortcoming? Please describe.
The current default for $PS1 is ok, but there other possibilities
Describe the solution you'd like
Maybe we could provide a primer on $PS1 mangling on a new documentation page that is dedicated to setting up a cozy and sensible user environment that includes more things. The primer could show only the most important as a starting point, illustrate some basic recipes (copy/paste ready) and link to additional resources for the people that want to dive in.
Additional context
There is this id-inside thing that we never wrote an article for. Maybe this paragraph on $PS1 might be interessting for non-HPC users too?
The text was updated successfully, but these errors were encountered: