From: Andrey Lisin <andrey.lisin@gmail.com>
To: info-gnus-english@gnu.org
Subject: Why do we need a number of different terminal modes in Emacs?
Date: Sun, 01 Feb 2015 12:38:50 +0600 [thread overview]
Message-ID: <m2egqa6sqt.fsf@gmail.com> (raw)
Hi everyone,
could anyone explain me why do we need several of terminal
implementations inside Emacs? Shell, eshell, term, ansi-term... And as
far as I noticed they all suck one way or another. For example, shell
cannot complete commands when you ssh to remote server inside it. Eshell
tragically cannot do a very simple thing - source a bash script. Really,
try to run `. some_script.sh' or `source some_script.sh' inside eshell.
So, am I right and we need them all just because one solves restrictions
of the others and others do the same thing for the one? Why then not
just to write some standard terminal implementation, that will just
works? Does it have something with cross-platform nature of Emacs? Or,
maybe I'm doing something wrong and all this stuff makes sense? Thank
you.
next reply other threads:[~2015-02-01 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 6:38 Andrey Lisin [this message]
2015-02-01 7:06 ` Andrey Lisin
[not found] <mailman.19085.1422772746.1147.info-gnus-english@gnu.org>
2015-02-01 13:43 ` Hikaru Ichijyo
2015-02-03 19:05 ` Emanuel Berg
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=m2egqa6sqt.fsf@gmail.com \
--to=andrey.lisin@gmail.com \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).