From: James Thomas <jimjoe@gmx.net>
To: "Help-gnu-emacs@gnu.org" <Help-gnu-emacs@gnu.org>
Subject: Re: How to get eshell to do what I used to do with shell
Date: Sun, 11 Aug 2024 02:31:13 +0530 [thread overview]
Message-ID: <86cymgytwm.fsf@gmx.net> (raw)
In-Reply-To: <DM3PR02MB10256ACA438DB5E085EE65D3C9DBB2@DM3PR02MB10256.namprd02.prod.outlook.com> (DAVID KARR's message of "Sat, 10 Aug 2024 17:00:44 +0000")
KARR, DAVID wrote:
> My old wrapper had these features:
> * In a non-shell buffer, execing the main func would either create the
> first shell buffer, or go to the first one in the chain, perhaps
> called the 0th.
> * In a shell buffer, execing the main func would create a new shell in
> the chain, using the current directory
> * In a shell buffer, execing the "goto-next-shell" func would move to
> the next buffer in the chain, or back to 0 if at the end
> * In a shell buffer, execing the "find-shell-with-dir" func would take
> a string argument and find the next buffer in the chain where the pwd
> has that string as a substring
>
> I think all of these are doable
They should be, but lemme just say that I think a better way to use
eshell is to have a single buffer: the ability to transparently 'cd' to
different remotes and selectively open async output buffers (at least
for me) makes keeping multiple buffers redundant and is more convenient:
if the user is a single person, all the commands are in a particular
sequence, after all.
Regards,
James
next prev parent reply other threads:[~2024-08-10 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 17:00 How to get eshell to do what I used to do with shell KARR, DAVID
2024-08-10 19:10 ` tpeplt
2024-08-10 19:52 ` KARR, DAVID
2024-08-10 22:32 ` tpeplt
2024-08-11 11:27 ` Joel Reicher
2024-08-10 21:01 ` James Thomas [this message]
2024-08-10 21:06 ` KARR, DAVID
2024-08-11 9:49 ` James Thomas
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=86cymgytwm.fsf@gmx.net \
--to=jimjoe@gmx.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).