unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Philip Kaludercic <philipk@posteo.net>, 53644@debbugs.gnu.org
Subject: bug#53644: 29.0.50; xref-search-program breaks if programm not installed on a remote host
Date: Fri, 4 Feb 2022 21:45:39 +0200	[thread overview]
Message-ID: <3b4cfff4-4d95-9f8e-d5ec-db6cc492a9b8@yandex.ru> (raw)
In-Reply-To: <87iltvnj3g.fsf@gmx.de>

Hi Michael,

On 04.02.2022 10:15, Michael Albinus wrote:

>>> When invoking a command that respects xref-search-program via TRAMP,
>>> e.g. on a remote system that doesn't have (in my case ripgrep)
>>> installed, an error is signalled indicating that the search query
>>> couldn't be executed.
>>
>> One way to work around this will probably involve an addition to
>> find-file-hook and some code which checks (file-remote-p
>> buffer-file-name) and sets xref-search-program to a particular value
>> buffer-locally depending on the result.
>>
>> Or an around-advice for xref-matches-in-files.
> 
> There are connection-local variables exactly for this use case.

Is there a documented way on how to make the variable's value on remote 
hosts customizable for the user too?

Or maybe it's not exactly necessary for this custom var.

>> A proper solution would probably look more similar to
>> grep-host-defaults-alist and grep-compute-defaults.
> 
> On my wishlist, there is moving grep-*-defaults to connection-local
> variables. But I fear it will break too many existing configurations.
> 
> Best regards, Michael.

Cheers,
Dmitry.





  reply	other threads:[~2022-02-04 19:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30 23:38 bug#53644: 29.0.50; xref-search-program breaks if programm not installed on a remote host Philip Kaludercic
2022-02-04  2:00 ` Dmitry Gutov
2022-02-04  8:15   ` Michael Albinus
2022-02-04 19:45     ` Dmitry Gutov [this message]
2022-02-05 14:38       ` Michael Albinus
2022-02-07  2:57         ` Dmitry Gutov
2022-02-07  9:18           ` Michael Albinus
2022-02-07 18:34             ` Michael Albinus
2022-02-08 11:15           ` Philip Kaludercic
2022-02-08 14:59             ` Michael Albinus
2022-02-08 17:12               ` Philip Kaludercic
2022-02-08 18:30                 ` Michael Albinus
2022-02-08 21:16                   ` Philip Kaludercic
2022-02-09  7:55                     ` Michael Albinus
2022-02-09  9:17                       ` Philip Kaludercic
2022-02-12  1:04                         ` Dmitry Gutov
2022-02-14 13:57                           ` Philip Kaludercic
2022-02-14 14:40                             ` Dmitry Gutov
2022-02-14 17:32                               ` Philip Kaludercic
2022-02-15  1:27                                 ` Dmitry Gutov
2022-02-15 16:32                                   ` Philip Kaludercic
2022-02-15 16:33                                     ` Dmitry Gutov
2022-02-15 16:37                                     ` Dmitry Gutov

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=3b4cfff4-4d95-9f8e-d5ec-db6cc492a9b8@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=53644@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=philipk@posteo.net \
    /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).