On Tuesday 24 April 2012 15:49:57 Chet Ramey wrote:
> On 4/24/12 10:46 AM, Mike Frysinger wrote:
> > On Tuesday 24 April 2012 08:23:04 Chet Ramey wrote:
> >> On 4/24/12 12:00 AM, Mike Frysinger wrote:
> >>>> OK, so you've stripped the local readline copy ou
On Thursday 26 April 2012 23:47:39 Linda Walsh wrote:
> Anything else you wanna tell me NEVER/ALWAYS to do?
try ALWAYS being polite. but i guess that'll NEVER happen.
oh well, thankfully kmail can auto-mute based on sender.
-mike
signature.asc
Description: This is a digitally signed
> function JobFinised {
> jcnt=$((${jcnt}-1))
: $(( --jcnt ))
or a portable version:
: $(( jcnt -= 1 ))
> while [ $# -gt 0 ] ; do
> while [ ${jcnt} -lt ${mjobCnt} ]; do
> jcnt=$((${jcnt}+1))
same math suggestion as above
-mik
iltin -- that does what you want?
i wish there was a way to use `wait` that didn't block until all the pids
returned. maybe a dedicated option, or a shopt to enable this, or a new
command.
for example, if i launched 10 jobs in the background, i usually want to wait
for the first one to exit so i can queue up another one, not wait for all of
them.
-mike
signature.asc
Description: This is a digitally signed message part.
On Friday 04 May 2012 12:44:32 Greg Wooledge wrote:
> On Fri, May 04, 2012 at 12:41:03PM -0400, Mike Frysinger wrote:
> > i wish there was a way to use `wait` that didn't block until all the pids
> > returned. maybe a dedicated option, or a shopt to enable this, or a new
&g
On Friday 04 May 2012 13:46:32 Andreas Schwab wrote:
> Mike Frysinger writes:
> > i wish there was a way to use `wait` that didn't block until all the pids
> > returned. maybe a dedicated option, or a shopt to enable this, or a new
> > command.
> >
> > for
On Friday 04 May 2012 15:02:27 John Kearney wrote:
> Am 04.05.2012 20:53, schrieb Mike Frysinger:
> > On Friday 04 May 2012 13:46:32 Andreas Schwab wrote:
> >> Mike Frysinger writes:
> >>> i wish there was a way to use `wait` that didn't block until all the
>
On Friday 04 May 2012 16:17:02 Chet Ramey wrote:
> On 5/4/12 2:53 PM, Mike Frysinger wrote:
> > it might be a little racy (wrt checking cnt >= 10 and then doing a wait),
> > but this is good enough for some things. it does lose visibility into
> > which pids are live v
On Friday 04 May 2012 15:25:25 John Kearney wrote:
> Am 04.05.2012 21:13, schrieb Mike Frysinger:
> > On Friday 04 May 2012 15:02:27 John Kearney wrote:
> >> Am 04.05.2012 20:53, schrieb Mike Frysinger:
> >>> On Friday 04 May 2012 13:46:32 Andreas Schwab wrote:
On Saturday 05 May 2012 04:28:50 John Kearney wrote:
> Am 05.05.2012 06:35, schrieb Mike Frysinger:
> > On Friday 04 May 2012 15:25:25 John Kearney wrote:
> >> Am 04.05.2012 21:13, schrieb Mike Frysinger:
> >>> On Friday 04 May 2012 15:02:27 John Kearney wrote:
>
On Saturday 05 May 2012 23:25:26 John Kearney wrote:
> Am 05.05.2012 06:28, schrieb Mike Frysinger:
> > On Friday 04 May 2012 16:17:02 Chet Ramey wrote:
> >> On 5/4/12 2:53 PM, Mike Frysinger wrote:
> >>> it might be a little racy (wrt checking cnt >= 10 and then
On Sunday 06 May 2012 03:25:27 John Kearney wrote:
> Am 06.05.2012 08:28, schrieb Mike Frysinger:
> > On Saturday 05 May 2012 23:25:26 John Kearney wrote:
> >> Am 05.05.2012 06:28, schrieb Mike Frysinger:
> >>> On Friday 04 May 2012 16:17:02 Chet Ramey wrote:
On Monday 07 May 2012 09:08:33 Chet Ramey wrote:
> On 5/5/12 12:28 AM, Mike Frysinger wrote:
> > On Friday 04 May 2012 16:17:02 Chet Ramey wrote:
> >> On 5/4/12 2:53 PM, Mike Frysinger wrote:
> >>> it might be a little racy (wrt checking cnt >= 10 and then doin
0x42bb5f]
/bin/bash(execute_command+0x4e)[0x42ee2e]
/bin/bash(reader_loop+0x8c)[0x418fcc]
/bin/bash(main+0xdb9)[0x417919]
/lib64/libc.so.6(__libc_start_main+0xed)[0x7fe20e84a3ed]
/bin/bash[0x4181dd]
-mike
signature.asc
Description: This is a digitally signed message part.
On Friday 11 May 2012 13:37:58 Chet Ramey wrote:
> On 5/11/12 11:43 AM, Mike Frysinger wrote:
> > in light of the recent discussion, i thought i could switch posix mode
> > on/off on the fly so that i restricted myself to this mode only when
> > using `wait`.
> > u
On Friday 11 May 2012 14:25:08 Chet Ramey wrote:
> On 5/11/12 11:43 AM, Mike Frysinger wrote:
> > in light of the recent discussion, i thought i could switch posix mode
> > on/off on the fly so that i restricted myself to this mode only when
> > using `wait`.
>
> >
es confusing to people) behavior. you need to have
some byte in there that breaks up the tokens -- be it a tab, space, or
newline.
-mike
signature.asc
Description: This is a digitally signed message part.
On Tuesday 21 August 2012 07:45:49 Ondrej Oprala wrote:
> unless this bug is already fixed in some way
yes, please retest with very latest bash-4.2 and the released patchsets
-mike
signature.asc
Description: This is a digitally signed message part.
consider this simple code:
$ cat test.sh
#!/bin/bash
trap 'echo $BASH_COMMAND; exit 1' ERR
set -e
true
(false)
true
when run, we see:
$ ./test.sh
true 1
this can be confusing when utilized with automatic backtraces :(
even when using errtrace and debugtrace, BASH_COMMAND is incor
On Wednesday 22 August 2012 12:30:11 Mike Frysinger wrote:
> consider this simple code:
>
> $ cat test.sh
> #!/bin/bash
> trap 'echo $BASH_COMMAND; exit 1' ERR
> set -e
> true
> (false)
> true
>
> when run, we see:
> $ ./test.sh
> true 1
err,
Rather than using 1 byte reads, use the existing cache read logic.
This could be sped up more, but this change is not as invasive and
should (hopefully) be fairly safe.
Signed-off-by: Mike Frysinger
---
builtins/read.def | 21 -
externs.h | 1 +
lib/sh/zread.c
.
it's the ldso missing. if a lib was missing, the ldso would spit out a useful
message telling you exactly which lib could not be found. at least, that's
the standard Linux (glibc/uclibc/etc...) behavior.
$ ./a.out: error while loading shared libraries: libfoo.so: cannot open shared
object file: No such file or directory
-mike
signature.asc
Description: This is a digitally signed message part.
> found."?
> >
> > Because that's what strerror() in your libc reports. It's not bash's
> > fault if libc produces a shorter message (correct in the common case)
> > than what the man pages says is possible in the more comprehensive case.
>
> I
On Wednesday 02 January 2013 07:07:49 Roman Rakus wrote:
> On 01/02/2013 02:25 AM, Mike Frysinger wrote:
> > On Tuesday 01 January 2013 15:10:00 Chet Ramey wrote:
> >> On 1/1/13 2:49 PM, Aharon Robbins wrote:
> >>> Michael Williamson wrote:
> >>>> I h
this is the route to take ? seems like if bash is
handling SIGCHLD, there's no avoiding this sort of check.
-mike
signature.asc
Description: This is a digitally signed message part.
On Monday 19 November 2012 19:46:17 Mike Frysinger wrote:
> Rather than using 1 byte reads, use the existing cache read logic.
> This could be sped up more, but this change is not as invasive and
> should (hopefully) be fairly safe.
ping ...
-mike
signature.asc
Description: This is a
On Friday 18 January 2013 07:49:22 Chet Ramey wrote:
> On 1/18/13 1:31 AM, Mike Frysinger wrote:
> > On Monday 19 November 2012 19:46:17 Mike Frysinger wrote:
> >> Rather than using 1 byte reads, use the existing cache read logic.
> >> This could be sped up more, but thi
On Friday 18 January 2013 07:55:00 Chet Ramey wrote:
> On 1/18/13 1:30 AM, Mike Frysinger wrote:
> > this is somewhat a continuation of this thread:
> > http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html
> >
> > i've gotten more or less the
normally a better gauge of how portable your script is, than
> > bash in posix mode.
>
> It is, but it still has a couple of extensions over the standard
right. and there's optional parts of the standard that some shells implement
and others omit.
> As for the rationale, making it strictly compatible in order to test
> scripts probably requires quite some more work and I bet Chet would
> not be against a --lint option or something like that but it may not
> be his primary objective.
some tool to analyze would be nice
-mike
signature.asc
Description: This is a digitally signed message part.
The TOOL variant will automatically search for a $host prefixed program
(e.g. x86_64-pc-linux-gnu) rather than looking for `ar` only. This is
useful when cross-compiling and it matches the behavior of the other
tools that configure relies on (e.g. cc & ranlib).
Signed-off-by: Mike Frysi
Guessing it was added by accident while testing.
Signed-off-by: Mike Frysinger
---
-i | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 -i
diff --git a/-i b/-i
deleted file mode 100644
index e69de29..000
--
1.8.0.2
tput rmcup
exit 0
}
trap cleanup SIGINT
while ! read -t0.01 -n1; do : ; done
run it in a loop like so:
$ while ./test.sh ; do :; done
then hold down ctrl+c. eventually it'll crash.
[1] https://455990.bugs.gentoo.org/attachment.cgi?id=338214
-mike
signature.asc
Description: This is a digitally signed message part.
n times does not return automatically.
it's as if the -t option were not specified.
-mike
signature.asc
Description: This is a digitally signed message part.
On Wednesday 27 March 2013 11:44:32 Roman Rakus wrote:
> Support for the ARM 64 bit CPU architecture (aarch64) was introduced in
> autoconf 2.69. bash uses an earlier version of
> autoconf, preventing its being built.
are you talking about config.{sub,guess}, or something els
On Wednesday 27 March 2013 14:02:57 Chet Ramey wrote:
> On 3/27/13 1:07 PM, Mike Frysinger wrote:
> > On Wednesday 27 March 2013 11:44:32 Roman Rakus wrote:
> >> Support for the ARM 64 bit CPU architecture (aarch64) was introduced in
> >> autoconf 2.69. bash
hing possibly important.
i'm not interested in debating the "you should be familiar with the code base"
as that's not being realistic. large code bases in the open source world, by
their nature, accept drive by commits and accidents happen.
-mike
signature.asc
Description: This is a digitally signed message part.
On Wednesday 03 April 2013 21:38:19 Chet Ramey wrote:
> On 4/3/13 12:31 PM, Mike Frysinger wrote:
> > sounds like the fundamental limitation is that the person writing the
> > code can't declare their intentions. after your compromise, they now
> > can. if you follow
On Thursday 04 April 2013 10:20:50 Chet Ramey wrote:
> On 4/4/13 12:34 AM, Mike Frysinger wrote:
> >>> would it be possible to enable a mode where you had to explicitly
> >>> `declare +r` the var ? being able to "simply" do `local FOO` allows
> >>
simple code snippet:
$ cat test.sh
func() {
cat > / < / <
signature.asc
Description: This is a digitally signed message part.
On Saturday 01 June 2013 17:07:33 Chet Ramey wrote:
> On 5/31/13 10:37 PM, Mike Frysinger wrote:
> > simple code snippet:
> > $ cat test.sh
> > func() {
> > cat > / < > 11
> > EOF
> > }
> > declare -fp
> >
> > when run, we see the
g, using memory-mapped I/O, the machine might very well start
> executing garbage and your C program would dump core or similar.
pretty sure the linux kernel (and others?) would return ETXTBSY and not even
allow the write
-mike
signature.asc
Description: This is a digitally signed message part.
-root:
$ rm -rf /
rm: it is dangerous to operate recursively on `/'
rm: use --no-preserve-root to override this failsafe
-mike
signature.asc
Description: This is a digitally signed message part.
On Tuesday 11 June 2013 03:23:29 Chris Down wrote:
> On 11 Jun 2013 02:19, "Mike Frysinger" wrote:
> > On Monday 10 June 2013 18:20:44 Chris F.A. Johnson wrote:
> > > On Mon, 10 Jun 2013, Linda Walsh wrote:
> > > >> Point taken, but the
simple test code:
unset foo
printf -v foo ""
echo ${foo+set}
that does not display "set". seems to have been this way since the feature
was added in bash-3.1.
-mike
signature.asc
Description: This is a digitally signed message part.
On Monday 24 June 2013 16:13:01 Chet Ramey wrote:
> On 6/17/13 1:27 AM, Mike Frysinger wrote:
> > simple test code:
> > unset foo
> > printf -v foo ""
> > echo ${foo+set}
> >
> > that does not display "set". seems to hav
7;
plus also in 'csh' ( which is a different story and probably does not apply
here )
system/version details:
GNU bash, version 4.2.10(2)-release (x86_64-pc-linux-gnu)
compile flags used:
bashlogger, net, nls
Gentoo x86_64
E3-1245v2
fix? none ( workaround )
Thank you and have a good weekend,
Mike FIedler
a
> need to reiterate absolutely everything that is already required by
> POSIX.
on a GNU system, coreutils provides `true` and `false` as well as man & info
pages. i don't think having bash duplicate things would be useful in any way.
-mike
signature.asc
Description: This is a digitally signed message part.
in an env variable.
adding other features like this doesn't sound like a bad idea at all, but it
also doesn't sound like it should preclude a simple & useful extension to
existing bash code.
-mike
signature.asc
Description: This is a digitally signed message part.
s here. we aren't talking about any path that is
searched via $PATH, we're talking about a bash-internal pseudo path that is
checked explicitly. there is no such /dev/tcp/ path on *nix systems; bash
keys off that to do internal network parsing.
-mike
signature.asc
Description: This is a digitally signed message part.
ature should at least be switchable, or otherwise restricted.
it already is via a configure flag: --disable-net-redirections
-mike
signature.asc
Description: This is a digitally signed message part.
one click, provided
> there are no conflicts.
git has dirt simple integration with e-mail too.
-mike
signature.asc
Description: This is a digitally signed message part.
atic intmax_t exp2 __P((void));
guess it should be renamed to something else.
-mike
signature.asc
Description: This is a digitally signed message part.
regex_t preg;
int i1 = regcomp(&preg, argv[1], 0);
int i2 = regexec(&preg, argv[2], 0, NULL, 0);
printf("regcomp(%s) = %i\n"
"regexec(%s) = %i\n", argv[1], i1, argv[2], i2);
return 0;
}
$ gcc test.c
$ ./a.out '
On Thursday, January 30, 2014 23:12:18 Andreas Schwab wrote:
> Mike Frysinger writes:
> > $ ./a.out 'a\-b' a-b
> > regcomp(a\-b) = 0
>
> The effect of \- in a BRE is undefined.
yes, but that's kind of irrelevant for the point raised here. bash's =~ uses
On Thursday, January 30, 2014 23:53:55 Andreas Schwab wrote:
> Mike Frysinger writes:
> > yes, but that's kind of irrelevant for the point raised here. bash's =~
> > uses ERE, and passing in REG_EXTENDED to get ERE semantics with regcomp()
> > yields the same
get same behavior in <=bash-4.2 and >=bash-4.3 by using single quotes:
P="foo_bar"
MY_P=${P/_/'~'}
echo "${MY_P}"
-mike
signature.asc
Description: This is a digitally signed message part.
#x27; 'a b c ' '\n'
> > Sat 14:17:53 ip2 yost /Users/yost
> > 0 635 Z%
> >
> > It would be nice if there were an easy way to do this in bash.
>
> printf "%q" does that.
indeed -- also remember that you need "$@" and not $@ (a
ke ENOEXEC) and the parent could look for that.
alternatively, accept that it's not a real problem in practice for the
majority of people as Chet has pointed out ;).
-mike
signature.asc
Description: This is a digitally signed message part.
al search for its value. see how autoconf
implements its AC_CHECK_SIZEOF macro using only compile tests for the
algorithm.
-mike
signature.asc
Description: This is a digitally signed message part.
On Tue 18 Mar 2014 21:11:07 Linda Walsh wrote:
> Mike Frysinger wrote:
> > On Tue 18 Mar 2014 01:04:03 Linda Walsh wrote:
> >> Chet Ramey wrote:
> >>> Because the execution fails in a child process. You'd be able to fix it
> >>> for that process,
e bug.)
as noted, this is a feature of bash :)
POSIX also imposes annoying behavior that bash fixes:
unset foo
f() { :; }
foo=bar f
echo $foo
POSIX will show bar (ugh) while bash will not (yeah!)
-mike
signature.asc
Description: This is a digitally signed message part.
ys the wrong
answer. use unadorned globs:
for f in dog*; do ...
i'd point out that if any of the files in your dir have whitespace, your code
would also break:
touch 'dog a b c'
for f in `ls dog*`; do ...
-mike
signature.asc
Description: This is a digitally signed message part.
. i wish we had a native
option for it. maybe something like:
read -A files -r -d '' < <(find . -iname '*.mp3' -print0)
perhaps there is another shell out there that implements something that can
replace that loop that bash can crib ?
-mike
signature.asc
Description: This is a digitally signed message part.
On Thu 27 Mar 2014 19:15:13 Pierre Gaston wrote:
> On Thu, Mar 27, 2014 at 5:53 PM, Mike Frysinger wrote:
> > On Thu 27 Mar 2014 08:01:45 Greg Wooledge wrote:
> > > files=()
> > > while IFS= read -r -d '' file; do
> > >
> > > file
On Fri 28 Mar 2014 10:23:17 Chris Down wrote:
there's really nothing to add to Chris's wonderful post :)
-mike
signature.asc
Description: This is a digitally signed message part.
urceforge.net/
if you're still set on this amalgamation, then might i suggest looking into
the expect-lite package ?
http://expect-lite.sourceforge.net/
-mike
signature.asc
Description: This is a digitally signed message part.
ll attempt to execute.
>
> ---
> It's not in the hash table, but type -P still
> returns the non-executable.
read what Chet said. type -P reflects what the shell will attempt, not what
is useful. the fact that it's not usable is irrelevant.
if you want to see if i
ee any reason to change it now.
>
> The only concerns I can think of are inconsistency with programs that use
> execvp(), or possibly double-expansion in the event of a user name or any
> path containing ~.
how so ? execvp doesn't do tilde expansion. only the shell does, and it does
it once at assignment.
-mike
signature.asc
Description: This is a digitally signed message part.
ffffff601000 r-xp 00:00 0
[vsyscall]
Aborted (core dumped)
-mike
signature.asc
Description: This is a digitally signed message part.
simple enough code:
foo=(0 0 0); [[ -z ${foo[@]#0} ]]; echo $?
with bash-4.3_p13 and older, this would show 0. starting with bash-4.3_p14,
this now shows 1.
i can't tell from the thread whether this was intentional:
https://lists.gnu.org/archive/html/help-bash/2014-04/msg4.html
any reason to not include the -e (scheduling priority) and -r (rt
priority) options that Fedora has been using ?
-mike
Ripped from Fedora
Add support for RLIMIT_NICE/RLIMIT_RTPRIO and add missing documentation
for many other options
--- builtins/ulimit.def
+++ builtins/ulimit.def
@@ -34,18 +
near unexpected token `('
however, this works:
func() { local -a foo=() ; local -a bar=() ; }
tested current Gentoo ebuild and vanilla tarball, both go boom
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
(RL_STATE_ISEARCH))
+if (RL_ISSTATE (RL_STATE_ISEARCH) && _rl_iscxt)
...
-else if (RL_ISSTATE (RL_STATE_NSEARCH))
+else if (RL_ISSTATE (RL_STATE_NSEARCH) && _rl_nscxt)
...
-else if (RL_ISSTATE (RL_STATE_NUMERICARG))
+else if (RL_ISSTATE (RL_STATE_NUMERICARG) && _rl_argcxt)
-mike
find attached a patch which:
- fixes misc warnings about unused variables
- missing xmalloc() prototype in callback.c
- fix warning misc.c:rl_digit_loop() about missing a return ...
not sure if 0 is the correct default return value though
-mike
--- readline-5.1.orig/bind.c2005-10-14 11
On Sunday 11 December 2005 20:59, Mike Frysinger wrote:
> Description:
> attempting to declare multiple local empty arrays fails with bash-3.1.
probably related, this syntax fails too:
$ eval foo=( "bar" )
bash: syntax error near unexpected
he binutils you are
using is older which is why binutils segfaulted ... it should be fixed
in newer versions to error out gracely when attempting to combine 32
and 64 bit objects incorrectly
someone just mentioned in on this list actually which is why i signed
up :)
-mike
_
ter than the one i posted earlier :)
http://lists.gnu.org/archive/html/bug-bash/2005-12/msg00033.html
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
most assignments that involve ()
these fail too:
a=() b=()
eval foo=()
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
On Wed, Dec 14, 2005 at 08:40:30AM -0500, Chet Ramey wrote:
> Mike Frysinger wrote:
>
> > this is the same thing as cross-compiling which doesnt work correctly
> > when it comes to generating the signal lists ... the binutils you are
> > using is older which is why bi
://lists.gnu.org/archive/html/bug-bash/2005-12/msg00051.html
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
quot;127.0.0.1/8 brd 127.255.255.255"
with bash-3.1 though, we get no output at all ...
changing expand_parameters() slightly is one workaround:
-local -a a=( ${x} )
+local -a a ; a=( ${x} )
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
On Saturday 24 December 2005 13:27, Chet Ramey wrote:
> Mike Frysinger wrote:
> > On Thu, Dec 22, 2005 at 09:24:06AM -0500, Chet Ramey wrote:
> >> Bash-Release: 3.1
> >> Patch-ID: bash31-001
> >>
> >> Bug-Description:
> >>
> >>
+++ bash/parse.y2006-01-07 16:12:40.0 -0700
@@ -2906,8 +2906,8 @@
{
if (open == ch) /* undo previous increment */
count--;
- if (ch == '(')/* ) */
- nestret = parse_matched_pair (0, '(', ')'
On Monday 09 January 2006 11:25, U-DULI2Krzysiek wrote:
> Bash Version: 3.0
> Patch Level: 16
> Release Status: release
>
> Description:
> bash -c time stackdumps. Not Cygwin specific.
bash-3.0 crashes but bash-3.1 does not
-mike
__
7;
- hold down a letter until it gets to the edge of the terminal
- observe the line wrapping too soon and overwriting current line
- hit enter/resize terminal/etc...
- hold down a letter until it gets to the edge of the terminal
- observe the line wrapping properly now
-mike
nd he was able to reproduce the bad
behavior (he uses gnome-terminal) ...
not quite sure where to take this next as ive never poked around readline or
bash before and terminals scare me :)
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
ASCII satisfies my needs :)
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
On Friday 13 January 2006 22:02, Mike Frysinger wrote:
> On Friday 13 January 2006 21:16, Chet Ramey wrote:
> > Someone who can reproduce this is going to have to gdb bash, attach to
> > the shell producing the bad behavior, and find out what _rl_screenwidth
> > and _rl_ter
On Friday 13 January 2006 12:11, Tim Waugh wrote:
> Description:
> If bash has argv[0] as '-/bin/bash' it does not become a login
> shell.
>
> Repeat-By:
> exec -l /bin/bash
> shopt
>
> Fix:
patch works for me usin
On Wednesday 18 January 2006 18:34, Jeff Chua wrote:
> GNU bash, version 3.1.5(1)-release
>
> sh -c "echo -n ok" returns "-n ok".
works correctly for me:
[EMAIL PROTECTED] 0 ~ $ sh -c "echo -n ok"
[EMAIL PROTECTED] 0 ~ $
-mike
_
-func
bash: typeset: `some-func': not a valid identifier
in other words, everything ive shown here is expected behavior except for the
very last 'typeset -f some-func' line ... this is with bash-3.1_p5, but
tested bash-3.0_p16 and got the sam
't bash behave like csh? Which bash does do at this time.
>
> csh -c 'echo a-{b{d,e}}-c'
> a-bd-c a-be-c
> bash -c 'echo a-{b{d,e}}-c'
> a-bd-c a-be-c
>
> What is the basis for the belief that it should get the other output?
b
are used, and while the inner braces used
commads, the outer braces did not
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
On Sunday 29 January 2006 19:23, William Park wrote:
> Let's see...
> a-{b{d,e}}-c
> a-{bd,be}-c
i'm pretty sure the commas are consumed in the expansion
side note, this also fails:
$ echo {a}{b,c}
{a}{b,c}
-mike
___
Bug-ba
a-bd-c a-be-c
> > >
> > >It looks okey, I think.
> >
> > Except that b{d,e} expands to 'bd be', not 'bd,be'.
>
> Hmm... no. Internally,
arguing for what goes on internally shouldnt have bearing on what the user
result is ... and in this case, th
${array[#]} isnt supported as well as [EMAIL PROTECTED] ?
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
h builtin, then that'd work
with some `echo | tr` magic, but it something like
${foo//[[:lower:]]/[[:upper:]]} would be nice
-mike
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
we've been using a patch in Gentoo for sometime which adds support
for /etc/inputrc as a fallback after $INPUTRC and ~/.inputrc ... i couldnt
seem to find anything in the archives where someone proposed this be added to
readline, but maybe i just missed it ?
nputrc
4. /etc/inputrc
which makes more sense to me ... if you want your ~/.inputrc to also use
the /etc/inputrc, then you should use an include directive yourself in
~/.inputrc rather than it always being forced ...
-mike
___
Bug-bash mailin
101 - 200 of 524 matches
Mail list logo
