Chet Ramey wrote:
Roman Rakus wrote:
I have found one message for this:
http://lists.gnu.org/archive/html/bug-bash/2008-05/msg00074.html
And I have added some others patches. Oh, 1 patch for this 3 things :)
Please say if this patch will be applied.
Thanks for the updates.
Chet
So, will it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[redirecting to bug-bash, as this is a bash-specific question]
According to Yu Cha Yung on 6/23/2008 12:24 AM:
|Hi,
|I am trying to export the output of time into a text file but failed
=sing
|the following command:
|time ls > time.tx
Eric Blake wrote:
> According to Yu Cha Yung on 6/23/2008 12:24 AM:
> |time ls > time.txt
> |It doesnt show the information of time in time.txt.
>
> That's because in bash, time is a reserved word, and because time's output
> goes to stderr, not stdout.
[...]
> \time ls >time.txt 2>&1
O
Alexis Huxley wrote:
Bash Version: 3.2
Patch Level: 39
Release Status: release
Description:
[[ ... =~ ... ]] is broken when RHS is quoted
The behavior changed, intentionally, between bash-3.1 and bash-3.2.
# As described by OP, =~ has stopped working:
lasagne$ bash
B wrote:
I am guessing here. Something with multiple instances of bash acessing the
history. Are duplicates checked when a bash session is closed?
No, only when adding commands to the history list. It's impractical to
check every line in the history file when appending a session's history
to i
grarpamp wrote:
And when using --disable-nls, these appear in the output of make.
These are all the result of assigning literal strings to char * variables.
When compiled with nls/locales, are assigned the return value from
gettext(3), which returns a char *. I'm not really inclined to change
