From: Jim Porter <jporterbugs@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 61954@debbugs.gnu.org
Subject: bug#61954: 30.0.50; [PATCH] Simplify structured commands in Eshell
Date: Sun, 5 Mar 2023 18:11:44 -0800 [thread overview]
Message-ID: <4b2704ab-d615-f6aa-90df-990444849ef0@gmail.com> (raw)
In-Reply-To: <87y1oar86t.fsf@melete.silentflame.com>
On 3/5/2023 5:15 PM, Sean Whitton wrote:
> I think you have typo'd the bug number?
Sorry, bug#57635.
> I would like to read about what the advantages of moving to CPS in
> particular will be. My understanding was that CPS is only rarely a good
> idea.
Well, that's what 'eshell-do-eval' is already; it's just incomplete
(doesn't understand all of Elisp) and has a number of bugs. Migrating to
generator.el's CPS machinery would mean we get the benefits of a
more-complete implementation, with (hopefully) fewer bugs.
Whether CPS is a good idea in general is above my pay grade, but short
of some major improvements to threads in Emacs, I don't see an
alternative. Eshell needs *some* mechanism for deferring execution of
its command forms. (As I recall, threads have issues around prompting
the user, which is why Tramp doesn't yet use threads, and Eshell would
have the same issues. Not only that, but if Eshell used threads, it
would cause problems when Eshell code calls Tramp code.)
next prev parent reply other threads:[~2023-03-06 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 7:28 bug#61954: 30.0.50; [PATCH] Simplify structured commands in Eshell Jim Porter
2023-03-06 1:15 ` Sean Whitton
2023-03-06 2:11 ` Jim Porter [this message]
2023-03-17 5: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
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=4b2704ab-d615-f6aa-90df-990444849ef0@gmail.com \
--to=jporterbugs@gmail.com \
--cc=61954@debbugs.gnu.org \
--cc=spwhitton@spwhitton.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).