Re: tramp (2.2.13.25.1); grep-compute-defaults locks in wrong values when first grep is remote

[Michael Albinus]

Dave Abrahams <address@hidden> writes:

> Hi Michael,

Hi Dave,

> When my first `M-x grep' starts in a tramp remote directory, it
> grep-compute-defaults *sometimes* decides that it can't use -H and
> instead must append /dev/null to the command, even when that's not the
> case... and that breaks `M-x grep' when I go to replace the grep command
> with `git grep'.  I have at least one machine where I can reproduce it,
> and also some machines where I can't.  Further, the remote defaults seem
> to be locked in for all subsequent greps and are not separately computed
> for any other host (including localhost).  Here's my
> grep-host-defaults-alist:
>
> ((/scp:shiny-11:
>   (grep-command "grep  -n -e ")
>   (grep-template "grep <X> <C> -n -e <R> <F>")
>   (grep-use-null-device t)
>   (grep-find-command
>    ("find . -type f -exec grep  -n -e  /dev/null {} +" . 34))
>   (grep-find-template "find <D> <X> -type f <F> -exec grep <C> -n -e <R> 
> /dev/null {} +")
>   (grep-find-use-xargs exec-plus)
>   (grep-highlight-matches nil))
>  (nil
>   (grep-command nil)
>   (grep-template nil)
>   (grep-use-null-device auto-detect)
>   (grep-find-command nil)
>   (grep-find-template nil)
>   (grep-find-use-xargs nil)
>   (grep-highlight-matches auto-detect)))

Honestly, it is related to grep.el. I've studied the code for a while in
order to understand how the defaults are set, but I'm too unfamiliar
with that code. Best would be you write an Emacs bug report.

I'm sorry I cannot help.

Best regards, Michael.