From: Jim Porter <jporterbugs@gmail.com>
To: Alfonso Sanchez-Beato <alfonsosanchezbeato@yahoo.es>,
Stefan Kangas <stefankangas@gmail.com>
Cc: 68074-done@debbugs.gnu.org
Subject: bug#68074: eshell sudo/doas does not work for aliases
Date: Sat, 27 Jan 2024 12:24:46 -0800 [thread overview]
Message-ID: <e8c9cdd3-ba88-4334-869f-5f2b79fd1ca2@gmail.com> (raw)
In-Reply-To: <2135837382.2409214.1706345170815@mail.yahoo.com>
On 1/27/2024 12:46 AM, Alfonso Sanchez-Beato via Bug reports for GNU
Emacs, the Swiss army knife of text editors wrote:
>
> En sábado, 27 de enero de 2024, 01:19:32 GMT, Jim Porter <jporterbugs@gmail.com> escribió:
>> ... actually, this is a more-complete patch. I'm not 100% sure about
>> this part though:
>>
>> ',(car args)
>>
>> That (usually) creates something like (quote "command"), but it's safer
I thought about this some more and the extraneous quoting is fine in my
opinion. Eshell already does that quite a bit in 'eshell-do-eval', so
what's one more case?
> This last patch works nicely, thanks a lot! It works also in cases where my patch was not, like:
>
> $ eshell/sudo VAR=val <alias> ...
Wait, that works?! (After trying it out locally, so it does!)
Looking at the code, I see why now: 'eshell-named-command' calls
'eshell-prepare-command-hook', and that hook is where we handle local
variables. However, I truly didn't expect that; I thought the local
variable handling occurred in an earlier phase. The more you know...
Anyway, since this works even better than I'd expected, I've now merged
my patch to the master branch as 3c680968e49. Closing this bug now.
prev parent reply other threads:[~2024-01-27 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31356544.8861481.1703711546895.ref@mail.yahoo.com>
2023-12-27 21:12 ` bug#68074: eshell sudo/doas does not work for aliases Alfonso Sanchez-Beato via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 21:00 ` Stefan Kangas
2024-01-11 21:15 ` Jim Porter
2024-01-25 2:43 ` Jim Porter
2024-01-26 23:53 ` Alfonso Sanchez-Beato via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-27 0:27 ` Jim Porter
2024-01-27 1:19 ` Jim Porter
2024-01-27 8:46 ` Alfonso Sanchez-Beato via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-27 20:24 ` Jim Porter [this message]
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=e8c9cdd3-ba88-4334-869f-5f2b79fd1ca2@gmail.com \
--to=jporterbugs@gmail.com \
--cc=68074-done@debbugs.gnu.org \
--cc=alfonsosanchezbeato@yahoo.es \
--cc=stefankangas@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 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).