From: Mark Plaksin <happy@usg.edu>
Subject: Emacs 21 and M-x term
Date: 01 Sep 2003 12:32:14 -0400 [thread overview]
Message-ID: <m3n0dojwq9.fsf@usg.edu> (raw)
Is there a version of Emacs 21 in which M-x term does the right thing most of
the time?
I've tried many versions including 21.3.50.2 from CVS and they all have
wacky problems. For example, in 21.3.50.2 it won't use more than half of
the window and ls output is not properly aligned. It behaves this way
with TERM set to both eterm and vt100. I've tried starting emacs with -q
and removing my shell's dot files just to make sure I'm not causing the
problem.
Is M-x term in Emacs 21 working well for folks? If so, what is your
emacs-version and OS?
Currently I use Emacs 20 and M-x term to log into lots of remote machines
via ssh. I often need to run terminal-based programs like less and vi on
the remote machine. I'm used to minor terminal emulation problems but most
of them can be fixed by hitting C-l or with small changes to term.el. The
M-x term problems with Emacs 21 are much worse. Am I just missing
something?
I've looked at M-x shell and M-x eshell but neither does what I want--I
really love M-x term :)
A side note: The remote machines I connect to run several different OSes.
Almost every time there is a new version of an OS (e.g., HP-UX 11.11 comes
out) there are new terminal emulation problems with M-x term in Emacs 20.
The problems can usually be demonstrated by hitting paging down with C-d
inside of vi. After that some lines of the file are on the wrong line of
the terminal. C-l usually gets things displayed correctly.
Is there a good reason for these problems? I don't fully understand
terminal emulation but I'd have guessed that once vt100 worked it should
work forever. term.el can be changed to resolve the problems, of course,
but it seems like that shoudn't be required.
Thanks for any help!
next reply other threads:[~2003-09-01 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 16:32 Mark Plaksin [this message]
[not found] <mailman.1385.1062441899.29551.help-gnu-emacs@gnu.org>
2003-09-01 19:10 ` Emacs 21 and M-x term Lute Kamstra
2003-09-04 13:39 ` Mark Plaksin
[not found] ` <mailman.135.1062682802.18171.help-gnu-emacs@gnu.org>
2003-09-04 16:39 ` Lute Kamstra
2003-09-09 0:17 ` Mark Plaksin
[not found] ` <mailman.36.1063066672.21628.help-gnu-emacs@gnu.org>
2003-09-09 10:18 ` Lute Kamstra
2003-09-10 1:39 ` Mark Plaksin
[not found] ` <mailman.101.1063158543.21628.help-gnu-emacs@gnu.org>
2003-09-10 8:44 ` Lute Kamstra
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=m3n0dojwq9.fsf@usg.edu \
--to=happy@usg.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).