Misleading text at start of manual

2012-04-04 Thread Reuben Thomas
(Checked against bash 4.2; for some reason, the manual on gnu.org is only 4.1.) The top node, "Bash Features", says: "The following menu breaks the features up into categories based upon which one of these other shells inspired the feature." But the following menu doesn't seem to bear that out.

Re: Expanding aliases to full command before execution

2012-04-04 Thread dethrophes
Am 04.04.2012 17:27, schrieb jrrand...@gmail.com: On Tue, Apr 3, 2012 at 5:22 PM, jrrand...@gmail.com wrote: Hi everyone, In bash, is it possible to expand my aliases either before they are executed or when they are stored in the history file? For example, if I have: alias ll='ls -l' defined

Re: Expanding aliases to full command before execution

2012-04-04 Thread Linda Walsh
jrrand...@gmail.com wrote: function expand_alias() # expand an alias to full command { if [ "$1" = "." ]; then argument="\\$1" else argument="$1" fi match=$( alias -p | grep -w "alias $argument=" ) if [ -n "$match" ]; then expanded="`

Re: weird behavior of set -e

2012-04-04 Thread Linda Walsh
mhenn wrote: Am 24.06.2011 11:51, schrieb Harald Dunkel: Hi folks, A colleague pointed me to this problem: If I run ( set -e; ( false; echo x ) ) in bash 4.1.5, then there is no screen output, as expected. If I change this to ( set -e; ( false; echo x ) || echo y ) then I get

Re: Expanding aliases to full command before execution

2012-04-04 Thread jrrand...@gmail.com
On Tue, Apr 3, 2012 at 5:22 PM, jrrand...@gmail.com wrote: > Hi everyone, > > In bash, is it possible to expand my aliases either before they are executed > or when they are stored in the history file? > For example, if I have:  alias ll='ls -l'  defined in my .bashrc, when I > execute "ll" from t