Re: Man page incorrect for "continue & break", "suspend" and "fg"
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 be apllied? begin:vcard fn:Roman Rakus n:Rakus;Roman org:Red Hat;BaseOS adr:;;;Brno;;;Czech Republic email;internet:[EMAIL PROTECTED] title:Associate software engineer tel;cell:+420 774 891 861 x-mozilla-html:FALSE version:2.1 end:vcard
Re: time command
-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.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. You need a compound command, such as:
{ time ls; } >time.txt 2>&1
or avoid the bash reserved word to invoke /bin/time (assuming you have a
replacement program installed):
\time ls >time.txt 2>&1
|basically i try all the option for time and only -p option works. Do
youhave any ideas on this matter? Thx!
That's because the bash reserved word time only supports -p (try 'help
time' to see this).
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkhfk3gACgkQ84KuGfSFAYC69QCfULlCIQM2wSqOsHaqBk7UFfpT
zUMAn0PMCpluzJqO9SO7wVbzMjI5Drai
=+z1I
-END PGP SIGNATURE-
Re: time command
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 Or use Bash's builtin "command" command, like this: command time ls >time.txt 2>&1 -- Fran
Re: [[ ... =~ ... ]] is broken when RHS is quoted
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 -c '[[ "apple" =~ "^(apple)" ]]; echo ${BASH_REMATCH[1]}'
<--- no output!
And this is how. Quoting any part of the rhs forces it to be matched
as a string.
Patch 39, which you appear to have applied, introduces a `compat31' shell
option which you may enable to restore the bash-3.1 behavior.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
Re: Bug on history control, don't erase no dups
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 it. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
Re: Rollup: Build issues with bash-3.2
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 this. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
