being explicit.
If you don't understand the copy descriptor and all of a sudden see yet
another use for the character to the left of a redirection operator, you're
going to be even more confused.
--
Dan Douglas
.
$ bash -s \EOF
f() {
trap 'trap - RETURN; cat /dev/fd/$x -; exec {x}-' RETURN
local x
: inner {x}0
cat /dev/fd/$x -
} middle
f outer
EOF
inner
middle
inner
outer
--
Dan Douglas
are located
within the main loop then monitor mode needs to be toggled off around them.
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
://lists.gnu.org/archive/html/bug-bash/2012-05/msg00055.html
I think you might be experiencing other known bugs. Chet pushed several
wait/job related commits within the last few weeks. I haven't tested these
yet. http://git.savannah.gnu.org/cgit/bash.git/tree/CWRU/CWRU.chlog?h=devel
--
Dan Douglas
system.
EOF
esac
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
overload this mail by reporting that nearly every issue
I've ever sent to this list over the last year or so (that turned out being
legitimate) appears to have been addressed in devel (at least, according to
a few minutes of testing). Thanks! :)
--
Dan Douglas
()
if [ $1 -ge 0 ]; then
printf $1
exec dash -c ${2}f '$(($1-1)) $2' -- $@
fi
( f 100 $(typeset -f f)$'\n' )
Joking of course :o)
FUNCNEST is usually good enough for me. No other shell I'm aware of
even has that.
--
Dan Douglas
to continue.
--
Dan Douglas
; })
: $({ case . in .) :; esac; })
: $(for x in .; do case . in .) :; esac; done)
: $(for x in .; do case . in .) :; esac; done)
EOF
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
method is to keep track of which variables have been
visited and error if any are referenced twice, rather than counting the
arithmetic evaluator stack depth, so this isn't possible in that shell.
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
-a a='([0]=foo [1]=foo [2]=foo [3]=foo)'
...
--
Dan Douglas
precludes its use.
--
Dan Douglas
[@]} ' and not `${#@}', and also that you did
not set IFS=: for count_args? If you use exactly the function you sent with
the default IFS then you should get 4 here.
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
On Wednesday, July 04, 2012 05:37:25 PM Rainer Blome wrote:
Original-Nachricht
Datum: Fri, 29 Jun 2012 18:03:13 -0500
Von: Dan Douglas orm...@gmail.com
An: bug-bash@gnu.org
CC: Rainer Blome rainer.bl...@gmx.de
Remember that my main suggestion is to clearly document
other possible RETURN traps, but most people won't have to worry
about that.
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
From: Dan Douglas
To: bug-bash@gnu.org
Subject: mapfile -n seeks ahead an extra line
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE
safe extensible libraries written for a shell.
--
Dan Douglas
On Wed, May 30, 2012 at 4:57 PM, Greg Wooledge wool...@eeg.ccf.org wrote:
On Wed, May 30, 2012 at 10:14:42AM -0600, Bill Gradwohl wrote:
What say you Chet? Bug or feature? There is no middle ground.
That's unrealistic. There are plenty of things that occupy that middle
ground -- unexpected
check for the correctness of:
$(rm -rf somepath; echo '[') x == x ]
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
: 1.61 MiB
# equery s bash
* app-shells/bash-4.2_p28
Total files : 464
Total size : 6.33 MiB
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
5foo
1 2 3 4 51
1 2 3 4 5foo
123451
12345foo
bash:
1 2 3 4 51
1 2 3 4 5foo
1 2 3 4 51
1 2 3 4 5foo
1 2 3 4 51
1 2 3 4 5foo
zsh:
1 2 3 4 51
1 2 3 4 5foo
1 2 3 4 51
1 2 3 4 5foo
1 2 3 4 51
1 2 3 4 5foo
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
Ugh, Sorry, I forgot to strip trailing whitespace. If that wasn't
comprehensible for anyone, the heredoc in the preceeding the testcase was:
args() { printf '%s ' $@; echo; }
args ${@}${1}
args ${@}foo
args ${@}${1}
args ${@}foo
IFS=
args ${@}${1}
args ${@}foo
EOF
--
Dan Douglas
again. (not overly anxious for a fix.)
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
explaination and example here:
http://wiki.bash-hackers.org/commands/builtin/unset#scope
Hopefully most of that is correct.
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
found before. Looks like this applies to
anything that has this sort of replacement context that contains valid brace
expansion syntax inside quotes.
Bash 4.2.24 - Gentoo amd64
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
On Monday, March 26, 2012 01:44:58 PM you wrote:
Dan Douglas orm...@gmail.com writes:
Hi, hopefully a self-explanatory one today:
~ $ ( set -x -- {a..c}; echo ${*-{1..3}} )
+ echo 'a b c' 'a b c' 'a b c'
a b c a b c a b c
~ $ ( set -x -- {a..c}; echo ${*/{1..3
On Monday, March 26, 2012 08:07:00 AM you wrote:
On 03/26/2012 07:56 AM, Dan Douglas wrote:
Don't know how much I'm allowed to quote here, but a quick read of the
POSIX parsing rules and parameter expansion sections suggest to me that
the start of the parameter expansion should be the most
would consider
it
as a bug.
imadev:~$ q=\'
imadev:~$ input=foosomethingbar
imadev:~$ echo ${input//something/$q}
foo'bar
I meant without temporary variable.
RR
ormaaj@ormaajbox ~ $ ( x=abc; echo ${x/b/$'\''} )
a'c
--
Dan Douglas
signature.asc
Description: This is a digitally
On Tuesday, February 28, 2012 06:38:22 PM John Kearney wrote:
On 02/28/2012 06:31 PM, Dan Douglas wrote:
On Tuesday, February 28, 2012 05:53:32 PM Roman Rakus wrote:
On 02/28/2012 05:49 PM, Greg Wooledge wrote:
On Tue, Feb 28, 2012 at 05:36:47PM +0100, Roman Rakus wrote:
And that means
On Tuesday, February 28, 2012 06:52:13 PM John Kearney wrote:
On 02/28/2012 06:43 PM, Dan Douglas wrote:
On Tuesday, February 28, 2012 06:38:22 PM John Kearney wrote:
On 02/28/2012 06:31 PM, Dan Douglas wrote:
On Tuesday, February 28, 2012 05:53:32 PM Roman Rakus wrote:
On 02/28/2012 05
On Monday, February 27, 2012 02:07:25 PM Davide Baldini wrote:
FROM Davide Baldini
On 02/27/12 04:11, Dan Douglas wrote:
If word is unquoted, all lines of the here-document are subjected to
parameter expansion, command substitution, and arithmetic expansion.
No pathname expansion
trap where you
could just set trace on functions where you want it, but looks like even
redefinitions break recursively, so you're stuck. Fortunately, there aren't a
lot of good reasons to have extglob disabled to begin with (if any).
--
Dan Douglas
signature.asc
Description: This is a digitally
lines of the here-document are subjected to
parameter expansion, command substitution, and arithmetic expansion.
No pathname expansion.
--
Dan Douglas
.
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
O_NONBLOCK is up there in things I wouldn't mind using. Namely, having access
to errno. I don't see any way of determining the fullness of a buffer even
through /proc/self/fdinfo/ on Linux.
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
on Gentoo Linux amd64.
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
) at shell.c:688
i = optimized out
code = optimized out
old_errexit_flag = 0
saverst = 0
locally_skip_execution = 0
arg_index = 3
top_level_arg_index = 3
--
Dan Douglas
signature.asc
Description: This is a digitally signed message part.
On Wednesday, December 14, 2011 10:57:21 AM Chet Ramey wrote:
On 12/13/11 3:13 PM, Dan Douglas wrote:
I imagine this is ok because Bash's declare -p is intended to be human-
readable only, whereas Ksh guarantees -p produces output in a format
reusable as input.
Bash's `declare -p' output
On Wednesday, December 14, 2011 05:47:24 PM Peng Yu wrote:
Hi,
I looks a little wired why 'until' is the way it is now. According to
the manual until is before the do-done block.
until test-commands; do consequent-commands; done
A common design of until in other language is that it
On Tuesday, December 13, 2011 12:14:41 PM lhun...@mbillemo.lin-k.net wrote:
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: darwin11.2.0
Compiler: /Developer/usr/bin/clang
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
))'
Segmentation fault
The segfault on the subshell there is a bit odd if it were merely a syntax
error.
GNU bash, version 4.2.10(1)-release (x86_64-pc-linux-gnu)
-Dan Douglas
201 - 241 of 241 matches
Mail list logo
