unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Will Parsons <oudeis@nodomain.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: Reasons for Switching to Eshell
Date: 30 Mar 2008 01:25:32 GMT	[thread overview]
Message-ID: <slrnfutr0c.p36.oudeis@isis.thalatta.eme> (raw)
In-Reply-To: mailman.9571.1206798351.18990.help-gnu-emacs@gnu.org

Lorenzo Isella wrote:
> Dear All,
> I am slowly discovering new features in emacs and I found out it has its 
> own shell (eshell).
> Now, I wonder if it is a good investment to learn how to use it. I found 
> tons of tutorials online (BTW: any recommendation to start me out?), but 
> I am missing the big picture.
> I suppose that eshell must be perfectly integrated with emacs, but other 
> than that are there reasons to give it preference with respect to .e.g BASH?
> Many thanks

I'm generally quite happy using the "native" shell (whether bash or tcsh)
under Unix-type systems, but I find eshell far superior to the native
command shell under Windows.  If you work (as I do) in various
environments, I can see where one might prefer to use the same shell
everywhere, and eshell provides that ability.  (The ability to use the same
[powerful] editor under many different OS's is a prime reason why I'm an
Emacs user in the first place.)

-- 
Will


       reply	other threads:[~2008-03-30  1:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.9571.1206798351.18990.help-gnu-emacs@gnu.org>
2008-03-30  1:25 ` Will Parsons [this message]
2008-03-30  7:41 ` Reasons for Switching to Eshell Tim X
2008-03-30  8:54   ` Richard G Riley
2008-03-30 23:13   ` William Xu
2008-03-30 12:15 ` Mathias Dahl
2008-03-30 13:00   ` Michael Albinus
     [not found]   ` <mailman.9637.1206881927.18990.help-gnu-emacs@gnu.org>
2008-03-30 19:43     ` Mathias Dahl
2008-03-30 20:24       ` Thierry Volpiatto
2008-03-30 22:29         ` Mathias Dahl
2008-03-31  8:13           ` Michael Albinus
2008-03-31 13:30       ` Christian Herenz
2008-03-31 14:56         ` Michael Albinus
2008-03-30 12:51 ` poppyer
2008-03-31  7:34   ` Tim X
2008-03-30  9:40 Pavol Murin
  -- strict thread matches above, loose matches on Subject: below --
2008-03-29 13:45 Lorenzo Isella

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=slrnfutr0c.p36.oudeis@isis.thalatta.eme \
    --to=oudeis@nodomain.invalid \
    --cc=ellenophilos@yahoo.com \
    --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).