*** This bug is a duplicate of bug 1097467 ***
https://bugs.launchpad.net/bugs/1097467
Merging with LP: #1097467, as documentation fixes are happening there to
reflect long-standing upstream desired behavior.
** This bug has been marked a duplicate of bug 1097467
bash does not fulfill --rcfile option properly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/589496
Title:
bash --rcfile does not behave as documented
Status in bash package in Ubuntu:
Confirmed
Status in bash package in Debian:
New
Bug description:
Binary package hint: bash
the bash manpage says this about --rcfile
--rcfile file
Execute commands from file instead of the system wide initial‐
ization file /etc/bash.bashrc and the standard personal initial‐
ization file ~/.bashrc if the shell is interactive (see INVOCA‐
TION below).
under INVOCATION it says
When an interactive shell that is not a login shell is started, bash
reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if
these files exist. This may be inhibited by using the --norc option.
The --rcfile file option will force bash to read and execute commands
from file instead of /etc/bash.bashrc and ~/.bashrc.
but when i execute
$ bash --rcfile somercfilewhichreallydoesexistandisreadableandall
it will still read /etc/bash/bashrc (can be verified by adding --verbose)
using lucid with bash 4.1-2ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
