Re: TAB is something you don't want to send thru *shell*

[Andreas Schwab]

Miles Bader <miles@gnu.org> writes:

|> jidanni@dman.ddts.net (Dan Jacobson) writes:
|> > What is the big problem with TAB in *shell* now (21.2)?
|> > No matter how you get a TAB into the command line, ^Q^I or paste, you
|> > are going to get the 329 etc. possibilities treatment:
|> 
|> I think this is because the pty emacs uses to communciate with the
|> shell process is kept in cooked mode, and so it's interpreting any
|> terminal control characters it gets in the input.

TAB is not a terminal control character.  It is interpreted by readline,
because bash does not know that there is already an editing interface
running on top of it.

|> It's a bug, though I'm not sure the right place to fix it offhand.

There should be a way to tell bash not to use its readline interface when
running in a shell buffer.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."