Re: Verbatim pasting

2010-08-10 Thread Andre Majorel
On 2010-08-10 16:05 -0400, Mike Frysinger wrote: > On Tue, Aug 10, 2010 at 2:08 PM, Andre Majorel wrote: > > Binding printable ASCII characters to readline functions is > > convenient but it can bite you when you paste text into a shell. > > > > Is there a way to bypass readline while pasting ? Som

Re: Verbatim pasting

2010-08-10 Thread Ben Pfaff
Andre Majorel writes: > Binding printable ASCII characters to readline functions is > convenient but it can bite you when you paste text into a shell. This also bites me from time to time when I cut-and-paste a command from an editor window into a bash terminal window. If the line that I cut-an

Re: Verbatim pasting

2010-08-10 Thread Mike Frysinger
On Tue, Aug 10, 2010 at 2:08 PM, Andre Majorel wrote: > Binding printable ASCII characters to readline functions is > convenient but it can bite you when you paste text into a shell. > > Is there a way to bypass readline while pasting ? Something like > a ^V toggle or a ^V that lasts until the next

Re: Verbatim pasting

2010-08-10 Thread Chet Ramey
On 8/10/10 2:08 PM, Andre Majorel wrote: > Binding printable ASCII characters to readline functions is > convenient but it can bite you when you paste text into a shell. > > Is there a way to bypass readline while pasting ? Something like > a ^V toggle or a ^V that lasts until the next newline or

Verbatim pasting

2010-08-10 Thread Andre Majorel
Binding printable ASCII characters to readline functions is convenient but it can bite you when you paste text into a shell. Is there a way to bypass readline while pasting ? Something like a ^V toggle or a ^V that lasts until the next newline or next pause between two characters longer than 250 m

Re: documentation for ${!prefix*} is misleading

2010-08-10 Thread Greg Wooledge
On Tue, Aug 10, 2010 at 04:50:48PM +0200, Andreas Schwab wrote: > There is no special behaviour of the * version. > > The quotes only make the difference of whether word > splitting can be applied on the expansion (if word splitting is > considered in the first place, which isn't in the case of a

Issuing re-read-init-file from a Bash function

2010-08-10 Thread Andre Majorel
How do you force a reload of ~/.inputrc from a Bash function ? All "bind re-read-init-file" seems to do is make the [f] key go away. Thanks in advance. -- André Majorel http://www.teaser.fr/~amajorel/

Re: documentation for ${!prefix*} is misleading

2010-08-10 Thread Andreas Schwab
Greg Wooledge writes: > On Tue, Aug 10, 2010 at 04:15:30PM +0200, Andreas Schwab wrote: >> Greg Wooledge writes: >> >> > The 4.1 man page says: >> > >> > ${!prefix*} >> > ${!pre...@} >> >Names matching prefix. Expands to the names of variables whose >> >name

Re: documentation for ${!prefix*} is misleading

2010-08-10 Thread Greg Wooledge
On Tue, Aug 10, 2010 at 04:15:30PM +0200, Andreas Schwab wrote: > Greg Wooledge writes: > > > The 4.1 man page says: > > > > ${!prefix*} > > ${!pre...@} > >Names matching prefix. Expands to the names of variables whose > >names begin with prefix, separated by

Re: documentation for ${!prefix*} is misleading

2010-08-10 Thread Andreas Schwab
Greg Wooledge writes: > The 4.1 man page says: > > ${!prefix*} > ${!pre...@} >Names matching prefix. Expands to the names of variables whose >names begin with prefix, separated by the first character of the >IFS special variable. When @ is used an

documentation for ${!prefix*} is misleading

2010-08-10 Thread Greg Wooledge
The 4.1 man page says: ${!prefix*} ${!pre...@} Names matching prefix. Expands to the names of variables whose names begin with prefix, separated by the first character of the IFS special variable. When @ is used and the expansion appears wi