On 10/12/11 7:26 PM, John E. Malmberg wrote:
> I posted this to the gmane.comp.shells.bash.bugs newsgroup two days ago,
> but have not seen any response.
It's self-evidently a good fix, and will be in the next bash release.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
On 10/12/11 4:07 PM, Greg Wooledge wrote:
> Personally I wish all the csh compatibility features would go away forever,
> but I appreciate that it's too late to remove them at this point. But
> I think the manual should be updated to indicate that the >&word form
> just plain fails for certain wo
On 10/13/11 10:37 AM, lolilolicon wrote:
> Inside an empty directory:
>
> touch 1 1\'1
> complete -r ls
> ls 1\' # ls 1\'1
> complete -f ls
> ls 1\' # ls 1
> ls 1\\\' # ls 1\'1
>
> (Note: the comment on the right is the result after pressing )
>
> Is this broken behav
Great stuff, amazingly fast - I'm really surprised!
Thanks for that.
Dave
-Original Message-
From: bug-bash-bounces+davidparks21=yahoo@gnu.org
[mailto:bug-bash-bounces+davidparks21=yahoo@gnu.org] On Behalf Of Chet
Ramey
Sent: Tuesday, October 04, 2011 5:29 PM
To: David Parks
Cc: b
(Sorry, forgot to CC the ML.)
On Sat, Oct 15, 2011 at 1:30 AM, Chet Ramey wrote:
> Thanks for the report. This looks like a problem, or an omission, with
> the effects of the `-f' option to complete, since it works as expected
> without using programmable completion or when using `-o default'.
