From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Antoine Levitt <antoine.levitt@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Character mode for comint?
Date: Sun, 30 Oct 2011 09:43:18 +0900 [thread overview]
Message-ID: <877h3npavt.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87lis3a5ye.fsf@gmail.com>
Antoine Levitt writes:
> I think the whole shell situation on emacs is a can of worms. There's
> term, ansi-term, nterm, multi-term, shell, comint, each with specific
> caveats and gotchas.
No, there's just comint, (most of?) the rest are layered on top of it.
The plan is pretty obvious: move features from the various
higher-level (user-level) interfaces into comint. This can probably
done ad hoc as you need features (but you need to test with everything
that matches `grep -E "(require 'comint)"' before pushing).
In python-mode, though, Emacs provides a powerful history mechanism
for comint. While it's true that Python users will be familiar with
the readline interface, Emacs users shouldn't have too much trouble
with switching to the Emacs bindings (and if they don't like that,
they may as well remap Emacs bindings since it's fundamentally more
powerful).
next prev parent reply other threads:[~2011-10-30 0:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 9:23 Character mode for comint? Antoine Levitt
2011-10-29 9:29 ` Andreas Schwab
2011-10-29 9:32 ` Antoine Levitt
2011-10-29 10:37 ` Andreas Schwab
2011-10-29 11:37 ` Antoine Levitt
2011-10-29 11:50 ` Andreas Schwab
2011-10-29 12:02 ` Antoine Levitt
2011-10-29 12:17 ` Andreas Schwab
2011-10-29 14:32 ` Antoine Levitt
2011-10-29 15:15 ` Andreas Schwab
2011-10-29 15:33 ` Antoine Levitt
2011-10-29 16:17 ` Andreas Schwab
2011-10-29 18:36 ` Antoine Levitt
2011-10-29 16:35 ` Stephen J. Turnbull
2011-10-29 18:36 ` Antoine Levitt
2011-10-29 19:48 ` Stefan Monnier
2011-10-29 16:36 ` Stefan Monnier
2011-10-29 20:38 ` Antoine Levitt
2011-10-30 0:43 ` Stephen J. Turnbull [this message]
2011-10-30 1:13 ` Stephen J. Turnbull
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=877h3npavt.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=antoine.levitt@gmail.com \
--cc=emacs-devel@gnu.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).