From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Keith David Bershatsky <esq@lawlist.com>, 25270@debbugs.gnu.org
Subject: bug#25270: eshell -- programmatically send input -- feature request
Date: Mon, 16 May 2022 14:13:11 +0200 [thread overview]
Message-ID: <87o7zxfzfs.fsf@gnus.org> (raw)
In-Reply-To: <9f52fe73-30ef-edf9-1d5b-2bf134e69dac@gmail.com> (Jim Porter's message of "Sun, 15 May 2022 22:46:47 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
> Also, for the code posted in the original message, I'm not sure the
> changes to `eshell-parse-command' are needed. It should already let
> you pass a command string to it. Maybe this is because there's an
> issue with how `eshell-parse-command' temporarily inserts COMMAND into
> the buffer (see the FIXME comment in the code in the original
> message)? If there is, we'd probably have to think quite a bit more
> about how to resolve it.
Yes, if I understood correctly, that was the main problem -- inserting
things into the buffer to eval it sometimes leaves artefacts (or doesn't
work), so it'd be better to talk directly to the underlying shell to get
things evalled.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-16 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 19:00 bug#25270: eshell -- programmatically send input -- feature request Keith David Bershatsky
2022-05-13 14:02 ` Lars Ingebrigtsen
2022-05-16 5:46 ` Jim Porter
2022-05-16 12:13 ` Lars Ingebrigtsen [this message]
2022-05-16 17:33 ` Jim Porter
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=87o7zxfzfs.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=25270@debbugs.gnu.org \
--cc=esq@lawlist.com \
--cc=jporterbugs@gmail.com \
/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.