bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#3343: marked as done (23.0.93; Setting grep-command etc has no effec


From: Emacs bug Tracking System
Subject: bug#3343: marked as done (23.0.93; Setting grep-command etc has no effect)
Date: Sat, 23 May 2009 00:25:07 +0000

Your message dated Fri, 22 May 2009 20:19:43 -0400
with message-id <87pre0ekm8.fsf@cyd.mit.edu>
and subject line 23.0.93; Setting grep-command etc has no effect
has caused the Emacs bug report #3343,
regarding 23.0.93; Setting grep-command etc has no effect
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3343: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3343
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
--- Begin Message --- Subject: 23.0.93; Setting grep-command etc has no effect Date: Thu, 21 May 2009 16:14:47 +0200 User-agent: Gnus/5.110009 (No Gnus v0.9) Emacs/23.0.90 (gnu/linux)
The problem is that grep-compute-defaults overwrites `grep-command',
`grep-find-command' et al.


emacs -Q
M-x set-variable RET grep-command RET "ls" RET
M-x grep RET RET
M-x set-variable RET grep-command RET "ll" RET
M-x grep RET   => The old command is still used.


This used to work in Emacs 22.



--- End Message ---
--- Begin Message --- Subject: 23.0.93; Setting grep-command etc has no effect Date: Fri, 22 May 2009 20:19:43 -0400
> emacs -Q
> M-x set-variable RET grep-command RET "ls" RET
> M-x grep RET RET
> M-x set-variable RET grep-command RET "ll" RET
> M-x grep RET   => The old command is still used.
>
> This used to work in Emacs 22.

This is due to the introduction of grep-compute-defaults and
grep-host-defaults-alist, which is supposed to offer "smarter" defaults
for these variables when you call grep on remote files.  Unfortunately,
this means that if you simply change these variables, those changes get
overwritten during the next interactive call to grep.

We should probably revisit the design of this code after the release.

In the meantime, I've made a change so that if you change these
variables via the Customize interface, the new values will take effect
correctly.

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]