From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Subject: Re: Why have "shell" when there's "term"
Date: Fri, 06 Jun 2003 17:13:57 +0200 [thread overview]
Message-ID: <sgdvfvj2q8a.fsf@occarina.pna.cwi.nl> (raw)
In-Reply-To: <sgdvfvjcmzi.fsf@occarina.pna.cwi.nl> (Lute Kamstra's message of "Fri, 06 Jun 2003 16:13:53 +0200")
Lute Kamstra <Lute.Kamstra@cwi.nl> writes:
[...]
> I just tried `term' for the first time in Emacs 21 and it seemed
> broken as a simple ls in bash spat out badly aligned text columns.
Oops, this just happens in CVS Emacs 21.3.50. I got lost in my
home-grown version jungle.
Lute.
--
(spook) => "Project Monarch arrangements David John Oates"
(insert-file-contents "~/.signature") => (error "`~/.signature' too rude")
next prev parent reply other threads:[~2003-06-06 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 12:57 Why have "shell" when there's "term" J Krugman
2003-06-06 14:13 ` Lute Kamstra
2003-06-06 15:13 ` Lute Kamstra [this message]
2003-06-06 14:32 ` Hallvard B Furuseth
2003-06-07 11:41 ` Lute Kamstra
2003-06-06 16:50 ` Eric Hanchrow
2003-06-06 22:11 ` J Krugman
2003-06-06 23:10 ` Barry Margolin
2003-06-09 19:12 ` Subhankar Chatterjee
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=sgdvfvj2q8a.fsf@occarina.pna.cwi.nl \
--to=lute.kamstra@cwi.nl \
/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).