The below patch to the Bash man page adds some prose to explain the
recent change to how regular expressions are parsed with the =~
operator. I hope this helps.
One of the lines in the patch is kind of long. I could not figure out
how to break it in a way that did not mess up the appearance of t
This patch fixes a typo in the man page that was causing formatting problems.
--
Francis Litterio
--- bash.1~ 2007-03-24 17:15:06.459699200 -0400
+++ bash.1 2007-03-30 15:17:56.564707200 -0400
@@ -2550,7 +2550,7 @@
pathname expansion.
\fIParameter\fP is expanded and the longest match of
Also, creating an "option" to decide which behaviour should be followed
(current one or the one I propose) would make everyone happy
It should be possible to code a value for PROMPT_COMMAND that sends
the cursor position report escape sequence (for xterm this is
"\033[6n"), learn the position of
Wouldn't a call to exit() flush any unwritten output buffers?
--
Fran
On 4/13/07, Mike Frysinger <[EMAIL PROTECTED]> wrote:
On Friday 13 April 2007, Chet Ramey wrote:
> West Stephen-QSW000 wrote:
> > Configuration Information [Automatically generated, do not change]:
> > Machine: powerpc
> > OS:
Ortwin wrote:
[[ "a b c" =~ "a (.) c" ]]
echo ${BASH_REMATCH[1]}
Recently, a change was made to cause quotes to suppress the special meaning
of regular expression characters in the right-hand side of =~. This is how
to do the above now:
[[ "a b c" =~ a\ (.)\ c ]]
I submitted a patch to t
