Paul Jarc spake thusly on 07/11/2007 12:10 PM:
Scott Carpenter <[EMAIL PROTECTED]> wrote:
V="one/two"
[[ ! $V =~ ^\.*/ ]] && echo not
3.1 will remove the backslash as part of basic string parsing, just as
if this were not part of a [[ command, while 3.2 handles the arguments
for [[ specially,
Scott Carpenter wrote:
> Hi, all. I hope this report is of some use -- I'm pretty inexperienced
> at GNU/Linux and Bash so I'm afraid this is going to sound horribly
> amateurish. But I think I've found something for you. (Or I'm simply
> about to demonstrate my crude understanding of regular ex
Scott Carpenter <[EMAIL PROTECTED]> wrote:
> V="one/two"
> [[ ! $V =~ ^\.*/ ]] && echo not
3.1 will remove the backslash as part of basic string parsing, just as
if this were not part of a [[ command, while 3.2 handles the arguments
for [[ specially, and will keep the backslash as part of the rege
On Tue, Jul 10, 2007 at 09:35:56PM -0400, Chet Ramey wrote:
> Poor Yorick wrote:
> > (on my debian system, bashbug reports for bash 2.05)
> >
> > printf status is 0 but /usr/bin/printf is 1. Is this the expected behavior?
> >
> > [EMAIL PROTECTED]:~$ bash3
> > [EMAIL PROTECTED]:~$ bash3 --versio
Benno Schulenberg wrote:
> Then look at a new typescript, and see if that strange 1034h is
> still there. If yes, a simple 'set | grep 1034' might find the
> variable that contains it.
Nothing found doing this grep... As for doing a script, the "1034h" is
indeed missing in the plain shell you
Hmm, interesting. I thought that using "env | grep PROM" would show
PROMPT_COMMAND's value, but I guess not. Yes, I do have PROMPT_COMMAND
set, it appears. However, if I unset it (and even also 'export PS1="foo
"' to set PS1 to a simple string), the problem remains.
How best to debug this? tcs
Hi, all. I hope this report is of some use -- I'm pretty inexperienced
at GNU/Linux and Bash so I'm afraid this is going to sound horribly
amateurish. But I think I've found something for you. (Or I'm simply
about to demonstrate my crude understanding of regular expressions.)
I realize that
Hi Benno,
Here is the output from "locale":
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_ALL=en_US.UTF-8
The following prompt is set in my .bashrc (but the same behavior happ
Chet Ramey wrote:
>
>
>>You might want to look at examples/rlfe in the readline distribution. It
>>does the same sort of front-end pty manipulation you;re interested in.
>
> Great tip, in there I found they do a setsid() and ioctl(...) and that
> fixed the nojob control warning message AND l
