From: Ted Zlatanov <tzz@lifelogs.com>
To: help-gnu-emacs@gnu.org
Subject: Re: leaving comint.el for a better emacs shell
Date: Fri, 13 May 2011 17:34:34 -0500 [thread overview]
Message-ID: <87liyap6v9.fsf@lifelogs.com> (raw)
In-Reply-To: ab79de0d-6ac7-4d18-883c-fe9d94790191@u15g2000vby.googlegroups.com
On Fri, 13 May 2011 14:46:41 -0700 (PDT) Terrence Brannon <thequietcenter@gmail.com> wrote:
TB> I would like to have a shell which
TB> 1. allows me to have multiple shells, with descriptive names, based
TB> on the current working directory of the buffer I am in
TB> 2. opens shells on remote machines, should the current working
TB> directory be on a machine I have accessed via tramp
eshell does 1 and 2.
TB> Eshell sounds neat, but I dont think it sources .bashrc files, does
TB> it?
Why do you need to source bashrc files? Do you need aliases, functions, prompts?
Ted
next prev parent reply other threads:[~2011-05-13 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 21:46 leaving comint.el for a better emacs shell Terrence Brannon
2011-05-13 22:34 ` Ted Zlatanov [this message]
2011-05-15 1:48 ` Tim X
2011-05-16 15:38 ` Terrence Brannon
2011-05-16 15:36 ` Terrence Brannon
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=87liyap6v9.fsf@lifelogs.com \
--to=tzz@lifelogs.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).