unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Per Bothner <per@bothner.com>
To: John Wiegley <johnw@gnu.org>
Cc: 22785@debbugs.gnu.org, Ingo Lohmar <i.lohmar@gmail.com>
Subject: bug#22785: 24.5; comint/shell modes should be merged with term mode
Date: Wed, 24 Feb 2016 14:23:42 -0800	[thread overview]
Message-ID: <56CE2D6E.2030800@bothner.com> (raw)
In-Reply-To: <m2k2luq8b5.fsf@newartisans.com>



On 02/24/2016 10:20 AM, John Wiegley wrote:
>>>>>> Per Bothner <per@bothner.com> writes:
>
>> To clarify: The goal is to essentially merge term.el and comint.el.
>> Comint.el might still exist, but only as a think veneer on term.el. shell
>> might or might not existing as a separate mode, but it would at most be a
>> thin veneer on top of term mode.
>
> I'm not sure what to think about this. Term is a bit of a complex beast, it is
> true, and it has far fewer users than comint. What is the motivation exactly?
> Would any mode other than shell interaction benefit from this merge?

While term is a bit of a complex beast, so is shell+comint mode.
Throw in ansi-color and it's more complex than term.

The existence of ansi-color shows there is a demand for at least handling
ansi escape sequences for colors and highlighting.  And if you're going to
handle those you might as well also support cursor movement and finish
the job.

Some inferior-process modes might prefer to make use of the inferior's readline,
at least as an option.

Sometimes a repl may want to do more than read/write times.  It may
want to switch colors, "print" pictures (as supported by Racket/Geiser),
ask for a password or a single-letter key.  Of course all of this can be done
with comint, but it's easier if one can use the same logic and protocols
whether in a comint mode, in term mode, or in a non-emacs terminal emulator.

Right now there is a lot of code duplication in Emacs.  term.el duplicates much
of comint.el.  ansi-color.el duplicates term.el. Etc.  It would be better to
clean this up.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/





      reply	other threads:[~2016-02-24 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 20:33 bug#22785: 24.5; comint/shell modes should be merged with term mode Per Bothner
2016-02-23 21:05 ` Ingo Lohmar
2016-02-23 21:24   ` Per Bothner
2016-02-24 18:20     ` John Wiegley
2016-02-24 22:23       ` Per Bothner [this message]

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=56CE2D6E.2030800@bothner.com \
    --to=per@bothner.com \
    --cc=22785@debbugs.gnu.org \
    --cc=i.lohmar@gmail.com \
    --cc=johnw@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).