On 07/30/2012 04:05 PM, jida...@jidanni.org wrote:
> Well -x works right away, but -v gets stuck until all depths of nested { } are
> over with.
Yes, this point has been made before, and the conclusion is unchanged -
this is not a bug. By the way, alias definitions have the same behavior.
--
Er
Well -x works right away, but -v gets stuck until all depths of nested { } are
over with.
Configuration Information [Automatically generated, do not change]:
Machine: ia64
OS: hpux11.31
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='ia64'
-DCONF_OSTYPE='hpux11.31' -DCONF_MACHTYPE='ia64-hp-hpux11.31'
-DCONF_VENDOR='hp' -DLOCALEDIR='/u
sr/local/share/locale' -DPACKAGE
On Sun, Jul 29, 2012 at 10:23 AM, Jason Vas Dias
wrote:
>
> function count_colons { IFS=':' ;v=($@); echo ${#v[@]}; }
>
>
count_colons() { local n=${*//[!:]}; printf '%s\n' "${#n}"; }
On Tue, Jul 31, 2012 at 12:12:42AM +0800, jida...@jidanni.org wrote:
> Why does -v not work until after "}" in this script?
>
> # su - nobody
> No directory, logging in with HOME=/
> $ cat /tmp/o
> {
> set -v
> # NO STDERR
> }
> # YES STDERR
> $ sh /tmp/o
> # YES STDERR
Because bash reads its
Why does -v not work until after "}" in this script?
# su - nobody
No directory, logging in with HOME=/
$ cat /tmp/o
{
set -v
# NO STDERR
}
# YES STDERR
$ sh /tmp/o
# YES STDERR
bash:
Installed: 4.2-4
On 07/25/2012 07:12 PM, Chet Ramey wrote:
On 7/25/12 10:57 AM, Roman Rakus wrote:
And there is also a problem when you change the `ulimit -u' value.
See https://bugzilla.redhat.com/show_bug.cgi?id=832997
It's not clear to me that it's desirable to attempt to remember a
potentially unlimited n
On Sun, Jul 29, 2012 at 03:04:21PM -0400, Chris F.A. Johnson wrote:
> On Sun, 29 Jul 2012, Jason Vas Dias wrote:
> >function count_args {v=($@); echo ${#v[@]}; }
>
>Always quote $@. Without quotes, it's the same as $*
>
> function count_args {v=( "
