unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Dan Espen <despen@verizon.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Why do we need a number of different terminal modes in Emacs?
Date: Sun, 01 Feb 2015 22:16:40 +0000	[thread overview]
Message-ID: <87386ps2ev.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <malfhp$7oo$1@dont-email.me> (message from Dan Espen on Sun, 01 Feb 2015 10:09:15 -0500)

Dan Espen <despen@verizon.net> writes:
...
> ls -> dired
> make -> M-x compile
> grep -> M-x grep
>
> these commands offer advantages over a shell buffer.
> Years ago I used to use M-x shell, but I no longer find use for any of
> these  shell interfaces.

Yes.  I only use Emac's shell modes for programs that can't be dealt
with by a specific mode.  For 90% of cases I get away without using them
at all, when I need them I use M-x term.

BR,
Robert Thorpe



  reply	other threads:[~2015-02-01 22:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.19088.1422774606.1147.help-gnu-emacs@gnu.org>
2015-02-01 10:37 ` Why do we need a number of different terminal modes in Emacs? Pascal J. Bourguignon
2015-02-01 11:10   ` Andrey Lisin
2015-02-01 11:24     ` Andrey Lisin
     [not found]     ` <mailman.19095.1422789865.1147.help-gnu-emacs@gnu.org>
2015-02-01 15:09       ` Dan Espen
2015-02-01 22:16         ` Robert Thorpe [this message]
2015-02-01  7:09 Andrey Lisin
2015-02-01 13:37 ` Robert Thorpe
2015-02-01 14:10   ` Andrey Lisin
2015-02-01 15:00 ` Marcin Borkowski

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=87386ps2ev.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=despen@verizon.net \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).