On Sat, May 24, 2008 at 10:46:40AM -0700, Dave Jarvis wrote:
> Description:
> It is possible to execute commands from the command-line
> without them appearing in the .bash_history file. This is a slight
> nuisance as any command that is accidentally preceded with a space
> will not appear
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='l$
uname output: Linux jaguar 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 200$
Machine Type: x86_64-pc-l
Juliano F. Ravasi wrote:
I got bitten by two unexpected (and undocumented) behaviors of
the 'read' builtin.
The first one is that it doesn't seem to handle word separators
equally, making distinction when spaces and non-space
separators are used to separate words.
Posix ma
On Saturday 24 May 2008 02:44, Juliano F. Ravasi wrote:
> Description:
>
> I got bitten by two unexpected (and undocumented) behaviors of
> the 'read' builtin.
>
> The first one is that it doesn't seem to handle word separators
> equally, making distinction when spaces and non-space
> separators
Juliano F. Ravasi wrote:
> The second one is that it chops leading and trailing whitespace
> when you provide one variable for assignment, and not when you
> use the default $REPLY.
>
> I don't know if these are intended behavior, but it doesn't seem
> to be documented, leadin
