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

[Dale Hagglund <rdh@yottayotta.com>]

schwab@suse.de (Andreas Schwab) writes:

> 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.

I believe that readline interprets ^V as its literal-next-char
escape.  So try the sequence

        C-q C-v C-q TAB

from inside the shell buffer and see if that helps.

Dale Hagglund.