Dear All, =========Environment=========
GNU bash, version 3.00.16(1)-release (i686-pc-linux-gnu) Copyright (C) 2004 Free Software Foundation, Inc. Linux 2.6.15.1 #2 PREEMPT i686 Intel(R) Pentium(R) III Mobile CPU 1133MHz GenuineIntel GNU/Linux on IBM T23 laptop. =========Environment========= =========BUG============ Executing: man bash and in the INVOCATION section, it reads: " When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. " While this is true for interactive login shells, it's not for non-interactive login shells. Executing: bash -l -c echo $- will not source ~/.bash_logout ==============BUG============ ===========Suggested Solution======== Change it to: " When an interactive login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. " ===========Suggested Solution======== ===========Other Suggestions ======== In INVOCATION section, after: " A login shell is one whose first character of argument zero is a -, or one started with the --login option. " It's really confusing unless you already know about this (then the purpose of this is? :p ). Can we add an example for added clarity, such as: " A login shell is one whose first character of argument zero is a -, or one started with the --login option. E.g., logging in to a system will provide a shell with `echo $0` = '-bash' if executed immediately after login, which is a login shell. Xterm login shells are not login shells. " Another suggestions goes into the same section (INVOCATION): Can we explain a little about what a non-interactive, non-login shell will do, regarding startup files, etc.? Thank you for your consideration. ===========Other Suggestions ======== BTW, the people at irc://irc.freenode.net #bash really helped! Please join us there! Regards, Q.D. _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash