From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
71655@debbugs.gnu.org, james@literate-devops.io
Subject: bug#71655: Eshell external commands do not work under GNU Emacs for Windows
Date: Mon, 24 Jun 2024 07:56:16 +0200 [thread overview]
Message-ID: <875xtyyjcv.fsf@gmx.de> (raw)
In-Reply-To: <ba25197b-be37-2b6d-b66a-ecf4e1785806@gmail.com> (Jim Porter's message of "Sun, 23 Jun 2024 18:40:37 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
Hi Jim,
> That could work, though thinking about this some more, I think there's
> a benefit to being careful about how we add checks here. For Tramp
> files, we should probably try to keep the number of calls that need to
> touch the remote filesystem to a minimum.
>
> I'll think about this some more and see if we can get all the checks
> we want without making the code slower over Tramp. (Maybe Tramp caches
> enough that this isn't a problem, but I'm not certain yet.)
If Eshell calls `process-file', it shall bind `process-file-side-effects'
to nil if appropriate for the given command.
Furthermore, Eshell might bind `remote-file-name-inhibit-cache' to
something which helps. The default value (10) seems to be very conservative.
In case Eshell needs to clear the cache for a given directory, there is
`dired-uncache'. Contrary to its name, it is not restricted to dired,
but of general purpose.
Best regards, Michael.
next prev parent reply other threads:[~2024-06-24 5:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:53 bug#71655: Eshell external commands do not work under GNU Emacs for Windows James Hilling via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 19:12 ` Eli Zaretskii
2024-06-19 19:22 ` Eli Zaretskii
2024-06-19 19:40 ` Jim Porter
2024-06-20 4:53 ` Eli Zaretskii
2024-06-20 5:34 ` Jim Porter
2024-06-20 7:45 ` Eli Zaretskii
2024-06-22 19:55 ` Jim Porter
2024-06-23 4:36 ` Eli Zaretskii
2024-06-24 1:40 ` Jim Porter
2024-06-24 5:56 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-08 3:26 ` Jim Porter
2024-07-08 11:09 ` Eli Zaretskii
2024-06-19 19:30 ` Eli Zaretskii
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=875xtyyjcv.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=71655@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=james@literate-devops.io \
--cc=jporterbugs@gmail.com \
--cc=michael.albinus@gmx.de \
/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).