Bug 9950
Summary: | Put fancy stuff in ~/.bashrc, not /etc/bashrc | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthew Miller <mattdm> |
Component: | bash | Assignee: | Bernhard Rosenkraenzer <bero> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | dr, pekkas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-04-14 12:29:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matthew Miller
2000-03-04 04:58:10 UTC
I agree. Perhaps related, note what happens when bash 1.14.7(1) does when provided with an invalid command-line argument: $ bash --version bash --version bash: --: bad option echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD}\007" Note that those escape codes are *displayed* as shown above. If you have e.g. 100 users on a box, it can be pretty tedious to put some new features in their .bashrc. I like addition like this in /etc/bashrc better. It's an opinion I guess. A little bug: if you have an SSH connection to somewhere and that connection breaks, the prompt isn't refreshed to reflect to your original source HOSTNAME. Just my 0.02c. If it's a new machine, it doesn't matter if this is in the skel .bashrc or in the system-wide one -- everybody gets it anyway. And if it's an upgrade, a lot of people would prefer to not have changes like this "forced" on them. If you as the sysadmin _do_ like the change, it's easy for you to add this to /etc/bashrc, but it's nicer for that to be your decision. (Or actually, you could use a simple shell script to add it to the individual ~/.bashrc files.) As for the "bug" you mention -- that's pretty unavoidable. (And one of several reasons people may not like this feature.) Users who don't like it can just undo it in their .bashrc - I think it's better off in the system wide file so Joe Stupid User gets nice settings even after a "What's this .bashrc file, I've never used it, open kfm/gmc click .bashrc, click delete" session. I don't mind that there /is/ an /etc/bashrc file where admins can place system-wide stuff. What I do object to is Red Hat deciding what constitutes a 'nice setting' and putting it there for us. I've just upgraded to 6.2 from 6.1, and had to waste time figuring out where the broken PROMPT_COMMAND stuff was coming from. Now I'm going to have to remember to fix this crap everytime I do an installation. It's the same with the Red Hat-supplied /etc/inputrc, which breaks vi mode in bash. Yes, these are only opinions, but I don't like having other people's opinions installed by default. Keep it policy-free, folks. |