quote nesting bug

2010-11-19 Thread Matt Zyzik
g output in all 3 shells (ignore leading whitespace): ''good morning Can I request comment? Thank you. --Matt Zyzik

Re: globstar broken again

2009-05-24 Thread Matt Zyzik
On Fri, May 22, 2009 at 04:10:21PM -0400, Chet Ramey wrote: > OK. I finally had some time to look at this. > > The issue is that you can't always add a null placeholder for the current > directory (the original bash-4.0 code) or never add one (patch 24). You > have to add one in certain circumst

Re: globstar broken again

2009-05-18 Thread Matt Zyzik
On Mon, May 18, 2009 at 10:04:06PM -0400, Mike Frysinger wrote: > On Monday 18 May 2009 21:14:18 Matt Zyzik wrote: > > Previously, the behavior of globstar mimicked that of ksh/zsh for such a > > command: "ls -adl **/*.cs". > > > > Now I've upgraded to Bas

globstar broken again

2009-05-18 Thread Matt Zyzik
All, Previously, the behavior of globstar mimicked that of ksh/zsh for such a command: "ls -adl **/*.cs". Now I've upgraded to Bash 4.0.24 from Bash 4.0.17 and the behavior is different (seemingly incorrect). Previously, the above-mentioned command would list all *.cs files in the current directo

Re: dir*/** behavior

2009-04-26 Thread Matt Zyzik
The above-mentioned "ls -adl exampl*/**" command should work the >> same as "ls >> -adl examples/**"; however, as shown above, the behavior of the former >> command is wrong. The >> commands work properly in both KornShell and Z shell. >> >&

Re: backward-kill-word is not refreshing correctly

2009-04-14 Thread Matt Zyzik
On Tue, Apr 14, 2009 at 02:07:32PM -0400, Chet Ramey wrote: > Chet Ramey wrote: > > > OK, I figured out why I couldn't reproduce it. My locale is always set > > to en_US.UTF-8 (multibyte), and the problem only manifests itself when > > in non-multibyte mode. This is why I originally asked for yo

Re: backward-kill-word is not refreshing correctly

2009-04-13 Thread Matt Zyzik
On Mon, Apr 13, 2009 at 05:50:52PM -0400, Chet Ramey wrote: > > > > My PS1, which causes the issue, is: > > > > PS1='[\[\033[01;32m\]\u \[\033[01;31m\]- \[\033[01;34m\]\w\[\033[00m\]]$ ' > > Sorry, I still can't reproduce it. Can you send a series of steps that > you use to reproduce the proble

Re: backward-kill-word is not refreshing correctly

2009-04-12 Thread Matt Zyzik
> If, as seems likely, this is a problem with the calculation of the physical > cursor position, a good place to start would be your PS1 and PROMPT_COMMAND > (if any). The locale you're using would be good, too. > > Chet My PS1, which causes the issue, is: PS1='[\[\033[01;32m\]\u \[\033[01;31m\]

some variable level issues

2008-06-29 Thread Matt Zyzik
bug-bash, I have a few issues to address, that I arrived at recently. None of them are necessarily bugs. 1. I noticed bash variables don't support null characters (0x00). This is unlike perl and other languages. Will this ever change? Have people requested or wanted this feature? 2. $(