Re: Bash-4.3-rc2 available for FTP

2014-01-30 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/30/14, 7:18 PM, Mike Frysinger wrote: >> The effect of \- in an ERE is still undefined. > > so it is. yet still irrelevant. the GNU library defines behavior explicitly: > https://www.gnu.org/software/gnulib/manual/html_node/The-Backslash-Chara

Re: Bash-4.3-rc2 available for FTP

2014-01-30 Thread Mike Frysinger
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 result (at least with glibc) as above

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Stephane Chazelas
2014-01-30 12:45:58 +0200, Pierre Gaston: > On Thu, Jan 30, 2014 at 12:37 PM, Dan Jacobson wrote: > > > Thanks fellows but now bash has become very slow to the touch that way. > > > > Maybe try something like: PROMPT_COMMAND='read -t0 && sleep 10' Or PROMPT_COMMAND="perl -MPOSIX -e 'tcflush 0,

Re: Bash-4.3-rc2 available for FTP

2014-01-30 Thread Andreas Schwab
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 result (at least with glibc) as above. The effect of \- in an ERE is still undefined. Andreas. -- A

Re: Bash-4.3-rc2 available for FTP

2014-01-30 Thread Mike Frysinger
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 ERE, and passing in REG_EXTENDED to get

Re: Bash-4.3-rc2 available for FTP

2014-01-30 Thread Andreas Schwab
Mike Frysinger writes: > $ ./a.out 'a\-b' a-b > regcomp(a\-b) = 0 The effect of \- in a BRE is undefined. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."

Re: Bash-4.3-rc2 available for FTP

2014-01-30 Thread Mike Frysinger
On Thursday, January 30, 2014 10:48:34 Chet Ramey wrote: > o. The shell now handles backslashes in regular expression arguments to the >[[ command's =~ operator slightly differently, resulting in more >consistent behavior. hmm, i seem to be running into a bug here. the bash man page sugge

Re: Bash-4.3-rc2 available for FTP

2014-01-30 Thread Mike Frysinger
general.c is missing traps.h include: general.c: In function ‘bash_tilde_expand’: general.c:991:3: warning: implicit declaration of function ‘any_signals_trapped’ [-Wimplicit-function-declaration] if (any_signals_trapped () < 0) unicode.c is missing stdio.h

Bash-4.3-rc2 available for FTP

2014-01-30 Thread Chet Ramey
The second release candidate of bash-4.3 is now available with the URL ftp://ftp.cwru.edu/pub/bash/bash-4.3-rc2.tar.gz This tar file does not include the formatted documentation (you should be able to generate it yourself). This release fixes many outstanding bugs in bash-4.2 and introduces seve

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Dan Jacobson
OK fixed spelling. Put in .bashrc to prevent accidental execution of many line clipboard paste dumps: case $- in *i*) safety_seconds=5 SECONDS=1 PROMPT_COMMAND="if ((SECONDS==0)); then echo TOO FAST HOLMES, waiting \ $safety_seconds seconds or hit ^C; sleep $saftey_seconds; else SEC

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Dan Jacobson
case $- in *i*) saftey_seconds=5 SECONDS=1 PROMPT_COMMAND="if ((SECONDS==0)); then echo TOO FAST HOLMES, waiting \ $saftey_seconds seconds or hit ^C; sleep $saftey_seconds; else SECONDS=0; fi" esac

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Dan Jacobson
Ah ha! Thanks for the private tip 4 minutes ago. This works!: saftey_seconds=5 PROMPT_COMMAND='if ((SECONDS==0)); then echo TOO FAST HOLMES, waiting '\ $saftey_seconds' seconds or hit ^C; sleep '$saftey_seconds'; else SECONDS=0; fi' Hope somebody documents it somewhere as otherwise, well, "the sh

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Pierre Gaston
On Thu, Jan 30, 2014 at 12:56 PM, Dan Jacobson wrote: > > "PG" == Pierre Gaston writes: > PG> Maybe try something like: PROMPT_COMMAND='read -t0 && sleep 10' > > But how will that on its own stop me from dumping tons of lines of junk > into bash via one accidental mouse click? > Well if the

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Dan Jacobson
> "PG" == Pierre Gaston writes: PG> Maybe try something like: PROMPT_COMMAND='read -t0 && sleep 10' But how will that on its own stop me from dumping tons of lines of junk into bash via one accidental mouse click?

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Pierre Gaston
On Thu, Jan 30, 2014 at 12:37 PM, Dan Jacobson wrote: > Thanks fellows but now bash has become very slow to the touch that way. > Maybe try something like: PROMPT_COMMAND='read -t0 && sleep 10'

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Dan Jacobson
Can you somehow give the user his prompt first and then wait, instead of the other way around? Also rapid ^P RET ^P RET should somehow be exempt.

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-30 Thread Dan Jacobson
Thanks fellows but now bash has become very slow to the touch that way.