unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
Cc: gnu-emacs-bug@moderators.isc.org
Subject: Re: TAB is something you don't want to send thru *shell*
Date: Wed, 26 Jun 2002 13:36:58 +0200	[thread overview]
Message-ID: <jefzza8e5h.fsf@sykes.suse.de> (raw)
In-Reply-To: <873cvbz89w.fsf@tc-1-100.kawasaki.gol.ne.jp> (Miles Bader's message of "Tue, 25 Jun 2002 15:29:32 GMT")

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

  reply	other threads:[~2002-06-26 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25  3:41 TAB is something you don't want to send thru *shell* Dan Jacobson
2002-06-25 15:29 ` Miles Bader
2002-06-26 11:36   ` Andreas Schwab [this message]
2002-06-26 12:39     ` Miles Bader
2002-06-26 13:12       ` Andreas Schwab
2002-07-21  2:16     ` Dale Hagglund

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jefzza8e5h.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gnu-emacs-bug@moderators.isc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).