unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: 60948@debbugs.gnu.org
Subject: bug#60948: 28.1; cannot find executable-find command
Date: Thu, 19 Jan 2023 18:58:53 +0200	[thread overview]
Message-ID: <83wn5io3zm.fsf@gnu.org> (raw)
In-Reply-To: <87o7qu1q8s.fsf@web.de> (arne_bab@web.de)

> From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
> Date: Thu, 19 Jan 2023 16:41:12 +0100
> 
> Emacs has broken badly: Opening files via tramp/ido leads to the message
> symbol's value as variable is void - executable-find:
> https://www.reddit.com/r/emacs/comments/107pc9m/emacs_can_find_the_executablefind_command/
> 
> 
> I solved it via
> rm -r ~/.emacs.d/eln-cache ~/.emacs.d/elpa/{compat,magit}-*
> 
> But this is actually just a workaround for a backwards compatibility
> problem which leaves Emacs in a broken state after updating.

Neither the Reddit discussion nor this report provided a recipe for
reproducing the problem.  In particular, what do you mean by "Opening
files via tramp/ido"?

Also, executable-find is a function, not a variable, and it is defined
on files.el which is preloaded into Emacs.  So it is unclear to me how
Emacs 28 could show such a message.  Which is why a recipe to
reproduce the problem is necessary if we are to do anything about this
issue.

Thanks.





  reply	other threads:[~2023-01-19 16:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 15:41 bug#60948: 28.1; cannot find executable-find command Dr. Arne Babenhauserheide
2023-01-19 16:58 ` Eli Zaretskii [this message]
2023-01-19 17:32   ` Dr. Arne Babenhauserheide
2023-01-19 17:57     ` Eli Zaretskii
2023-01-19 20:28       ` Dr. Arne Babenhauserheide
2023-01-20  6:39         ` 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=83wn5io3zm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60948@debbugs.gnu.org \
    --cc=arne_bab@web.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).