bash completion escaping bug

2015-08-24 Thread Neven Sajko
Hi, I use bash 4.3.039 and there is a bug (not necessarily a recent regression) with its file name completion feature. for example I have this in shell input: db.rc $home/Downloads/games/DOS/Captai and after I press Tab I have this: db.rc \$home/Downloads/games/DOS/Captain\ Bible\ in\ the\ Dom

Re: Multi-line bash strings that end in ! improperly treated as event designator

2015-08-24 Thread Lane Schwartz
On Mon, Aug 24, 2015 at 8:19 AM, Chet Ramey wrote: > On 8/21/15 5:17 PM, Lane Schwartz wrote: > > > Bash Version: 4.3 > > Patch Level: 11 > > Release Status: release > > > > Description: > > Per the Bash Reference Manual, section 9.3.1 "Event > Designators", a > > bare exclamation point s

Re: Multi-line bash strings that end in ! improperly treated as event designator

2015-08-24 Thread Chet Ramey
On 8/24/15 10:16 AM, Lane Schwartz wrote: > In light of your comments, might I suggest two additions to the manual? > > * History expansion takes place before quote removal. (This could be added > to the bullet list in Section 3.5) I would think that the following sentence from the HISTORY EXPAN

Re: Multi-line bash strings that end in ! improperly treated as event designator

2015-08-24 Thread Chet Ramey
On 8/21/15 5:17 PM, Lane Schwartz wrote: > Bash Version: 4.3 > Patch Level: 11 > Release Status: release > > Description: > Per the Bash Reference Manual, section 9.3.1 "Event Designators", a > bare exclamation point should be treated as "Start[ing] a history > substitution, except when f

Re: coredump with wait -n

2015-08-24 Thread Chet Ramey
On 8/22/15 4:39 AM, isabella parakiss wrote: > Hi, after running wait -n there's something wrong, ^C doesn't work > properly anymore: it displays ^C in the readline buffer, but the current > line stays there until I press enter. Running any command "fixes" it. > > > It can also dump core if you