From: Simon Streit <simon@netpanic.org>
To: Tomas Volf <~@wolfsden.cz>
Cc: 68850@debbugs.gnu.org
Subject: bug#68850: emacs: rgrep does not work over tramp
Date: Tue, 10 Dec 2024 21:02:35 +0100 [thread overview]
Message-ID: <yguseqv4884.fsf@netpanic.org> (raw)
In-Reply-To: <87bjxj7bzr.fsf@wolfsden.cz> (Tomas Volf's message of "Tue, 10 Dec 2024 17:12:56 +0100")
Thank you for your quick reply!
Tomas Volf <~@wolfsden.cz> writes:
> Customizing `find-program' to just "find" and restarting Emacs does the
> trick. So just sticking
>
> (setopt find-program "find")
>
> into `init.el' should work.
>
> I played with it around for a bit but did not figure out how to
> customize it in already running Emacs. I am sure it is possible, but I
> hit the self-imposed time limit before figuring it out.
Setting this variable fixes it and happily applied it locally.
I also get your point now too. The path has been hard-coded at build
time. Looking into the package declaration, it is not the only one
being modified. This modification may seem reasonable when working
within an environment of Guix. But it can become a disadvantage
when working on hosts that are sans Guix.
Also, how can this path to an application within the store work on a
remote system – that may also have a Guix store – when it does not
exist? My guess here is, that tramp will call the application on remote
host it is working on. Then it should also expect that path on the
remote store to exist too.
I can't deny that my Guix systems are not that much different to each
other. They usually tend to have similar states of stores. I can test
a scenario with an empty near clean store.
Kind regards
--
Simon
prev parent reply other threads:[~2024-12-10 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 13:08 bug#68850: emacs: rgrep does not work over tramp Tomas Volf
2024-12-10 15:05 ` Simon Streit
2024-12-10 16:12 ` Tomas Volf
2024-12-10 20:02 ` Simon Streit [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yguseqv4884.fsf@netpanic.org \
--to=simon@netpanic.org \
--cc=68850@debbugs.gnu.org \
--cc=~@wolfsden.cz \
/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/guix.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.