Description:
it's not a bug, but a strange behavior
the flag interactive_comments is accessible from both shopt and shopt -o
shopt | grep interactive_comments
shopt -o | grep interactive_comments
in your documentation (bashref), shopt -o (set -o) does not have this
flag...
thanks for y
[EMAIL PROTECTED] wrote:
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/
antonio wrote:
Description:
it's not a bug, but a strange behavior
the flag interactive_comments is accessible from both shopt and shopt -o
shopt | grep interactive_comments
shopt -o | grep interactive_comments
in your documentation (bashref), shopt -o (set -o) does not have this
flag...
Dmitry V. Levin wrote:
Hi,
I wonder whether such difference in "trap" behavior is valid:
$ sh -c 'f() { echo f; }; t() { trap f EXIT; trap; }; t'
trap -- 'f' EXIT
f
$ sh -c 'f() { echo f; }; t() { trap f EXIT; trap; }; t&'
trap -- 'f' EXIT
$ sh -c 'f() { echo f; }; t() { trap f EXIT; trap; }; (
E4) If I pipe the output of a command into `read variable', why doesn't
the output show up in $variable when the read command finishes?
Would it cause a great deal of upset if the last section of a
pipeline ran in the current process?
Regards, Max
Hi All,
I have noticed that any number larger than 10 items in my select menu list
will wrap the menu.
I am not sure if this is a terminal issue or it is the way the BASH select
function works
Current Example:
1) mark3) paul 5) greg 7) mike9) justin
2) james 4) simon 6) kate 8) a