all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xavier Maillard <xma@gnu.org>
To: jadamson@partners.org (Joel J. Adamson)
Cc: dkcombs@panix.com, help-gnu-emacs@gnu.org
Subject: Re: what's much better in eshell than eg tcsh?
Date: Sun, 6 Apr 2008 02:00:02 +0200	[thread overview]
Message-ID: <200804060000.m36002sp007651@localhost.localdomain> (raw)
In-Reply-To: <878wztu0pc.fsf@W0053328.mgh.harvard.edu> (jadamson@partners.org)


   Although this sounds like bait, I'll try to help you.

   dkcombs@panix.com (David Combs) writes:

   > I tried it once, a few years ago, and found it difficult,
   > maybe even unpleasant, to use.  Also never learned how
   > to do things I was used to do with tcsh.

   Eshell is for interactive use in Emacs.  It's more portable than say
   bash, if you don't want to install Cygwin.

   > And why better (for programming) than bourne?

   It's not.  Scripting in Eshell doesn't make any sense.  For that you'd
   simply use Lisp.

   Eshell, IMO, is nice because you can use familiar Emacs commands as
   shell commands, however, I get a lot more mileage out of just using
   dired and Emacs in command mode (as an editor) than in Eshell.  Eshell
   also mixes up parentheses and brackets, which I find slightly confusing.

I also tried several times to use eshell but I really prefer
eev-mode + M-x shell.

I highly recommend anybody to try eev-mode to see what it can do.

	Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org




  reply	other threads:[~2008-04-06  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04  1:44 what's much better in eshell than eg tcsh? David Combs
2008-04-04 13:13 ` Chris McMahan
2008-04-04 14:57 ` Joel J. Adamson
2008-04-06  0:00   ` Xavier Maillard [this message]
2008-04-04 15:36 ` Ted Zlatanov
2008-04-05  3:21 ` Tim X

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200804060000.m36002sp007651@localhost.localdomain \
    --to=xma@gnu.org \
    --cc=dkcombs@panix.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jadamson@partners.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.