From: Ingo Lohmar <i.lohmar@gmail.com>
To: Per Bothner <per@bothner.com>, 22785@debbugs.gnu.org
Subject: bug#22785: 24.5; comint/shell modes should be merged with term mode
Date: Tue, 23 Feb 2016 22:05:18 +0100 [thread overview]
Message-ID: <87si0ji1dd.fsf@acer.localhost.com> (raw)
In-Reply-To: <56CCC20A.4090804@bothner.com>
On Tue, Feb 23 2016 12:33 (-0800), Per Bothner wrote:
> The "line" submode of term mode duplicates much of the functionality
> of comint mode. When I wrote term mode, my hope was that it would
> subsume comint mode, or that comint mode would be built on top of
> term mode. That never happened - so far.
>
> 'shell mode' should basically be the same as 'term' mode, except
> that shell mode starts of in line-editing mode, while term mode
> starts up in character mode.
>
> There are obvious advantages to merging these modes. One is
> we have ansi escape sequence handling in a single place.
> Another is that you can run console applications from shell mode.
To me, that seems to be a bad idea. They are two different modes
precisely *because* they are quite different. If you want to run
console applications, why would you use shell-mode at all?
I dumped any use of term.el because I could not control its
complexities, no matter what overrides, patches and advices I used. I
have not looked back after using shell-mode where it's useful instead,
and not running console applications anymore.
Term is *significantly* more complex than shell (175k vs 54k), and does
a lot more things (for better or worse). Maybe factoring out the ANSI
sequence parsing is what you really want?
next prev parent reply other threads:[~2016-02-23 21:05 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 [this message]
2016-02-23 21:24 ` Per Bothner
2016-02-24 18:20 ` John Wiegley
2016-02-24 22:23 ` Per Bothner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87si0ji1dd.fsf@acer.localhost.com \
--to=i.lohmar@gmail.com \
--cc=22785@debbugs.gnu.org \
--cc=per@bothner.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.