From: Pascal Bourguignon <spam@thalassa.informatimago.com>
Subject: Re: WARNING: terminal is not fully functional
Date: 29 May 2003 20:07:41 +0200 [thread overview]
Message-ID: <87znl5fwya.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: bb54hm$lcu$1@reader1.panix.com
Irving Kimura <irving_kimura@lycos.com> writes:
> I find it infuriating that M-x shell does not give me a fully
> functional bash (or rather, a fully functional terminal). For
> instance, I can't pipe things through less ("WARNING: terminal is
> not fully functional"). And /bin/ls --color results in gobbledygook.
> Etc.
>
> Of course, my main reason for using M-x shell is to be able to
> treat stdout as any other Emacs buffer. (In particular, I find it
> very useful to be able to easily copy selected chunks of stdout to
> another Emacs buffer.) Is this capability fundamentally antithetical
> to a "fully functional terminal" that would allow me to pipe outputs
> through less, run /bin/ls --color, run man, run top, etc? If not,
> is there any way to configure Emacs so that M-x shell operates
> under a "fully functional terminal"?
>
> Thanks!!!
>
> -Irv
(add-hook 'shell-mode-hook
'(lambda ()
(set-variable 'tab-width 8)
(ansi-color-for-comint-mode-on)
(process-send-string (get-buffer-process (current-buffer))
"alias less=cat ; alias more=cat")))
M-x term is no use for tops...
A good emacs exercise would be to add support for basic VT100 escape
sequences to shell or term, moving the cursor, and overwritting the
characters, etc. Should not be too difficult.
--
__Pascal_Bourguignon__ http://www.informatimago.com/
----------------------------------------------------------------------
Do not adjust your mind, there is a fault in reality.
next prev parent reply other threads:[~2003-05-29 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 14:13 WARNING: terminal is not fully functional Irving Kimura
2003-05-29 14:18 ` Phillip Lord
2003-05-29 14:26 ` lawrence mitchell
2003-05-31 9:28 ` Tim X
2003-05-29 14:29 ` Paolo Gianrossi
2003-05-29 14:39 ` Stefan Monnier
2003-05-29 18:52 ` Irving Kimura
2003-05-30 4:58 ` Kai Großjohann
2003-05-30 18:23 ` Irving Kimura
2003-05-30 18:26 ` Barry Margolin
2003-05-31 9:39 ` Tim X
2003-06-02 17:25 ` Kevin Rodgers
2003-05-29 16:02 ` Kevin Rodgers
2003-05-29 18:07 ` Pascal Bourguignon [this message]
[not found] ` <878ysp1kyk.fsf@kruhft.vc.shawcable.net>
2003-06-01 6:07 ` Pascal Bourguignon
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=87znl5fwya.fsf@thalassa.informatimago.com \
--to=spam@thalassa.informatimago.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.
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).