On 2010-08-15 01:08 +0400, Dmitry Groshev wrote:
> If an escape's parameter makes no sense, escape sequence should be
> left untranslated - just the way "\x" handles things like "\xZZ". Make
> "\c" check that its parameter is an ASCII char, and the problem will
> be fixed.
> Unless for some reason
> How do you force a reload of ~/.inputrc from a Bash function ?
There's no good way to do this. The bindable readline functions are
not designed to be called in this fashion, and there's nothing written
to act as a bridge.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
On 15/08/2010, Chet Ramey wrote:
> I'm not sure why you think this is a bug.
Because the documentation says "backslash-escaped _characters_", and
not "bytes"? ;-)
> The \c escape is described
> as converting to a control character; control characters are always a
> single byte; the conversion to
On 8/14/10 3:01 PM, Dmitry Groshev wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
> -DCONF_VEN
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale'
-DPACKAGE
Thanks, Chet. I'll try the patch out as soon as I can get to it.
Meanwhile, I've also tried to add in some of the examples/loadables
(beyond the "tty" one), and it makes bash unstable. I will also try
to put together a patch that will run through the examples directory
on "make check". I am pret
