GNU bug report logs - #61926
29.0.60; [PATCH] Make tramp-remote-path behave like exec-path

Previous Next

Package: emacs;

Reported by: João Távora <joaotavora <at> gmail.com>

Date: Fri, 3 Mar 2023 00:19:01 UTC

Severity: normal

Found in version 29.0.60

Full log


Message #8 received at 61926 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: João Távora <joaotavora <at> gmail.com>
Cc: michael.albinus <at> gmx.de, 61926 <at> debbugs.gnu.org
Subject: Re: bug#61926: 29.0.60;
 [PATCH] Make tramp-remote-path behave like exec-path
Date: Fri, 03 Mar 2023 09:23:58 +0200
> Cc: michael.albinus <at> gmx.de
> From: João Távora <joaotavora <at> gmail.com>
> Date: Fri, 03 Mar 2023 00:19:50 +0000
> 
> Very few Emacs variables, if any, require a separate command (here M-x
> tramp-cleanup-all-connections) to be issued after the variables value is
> set.  This variable needn't belong to that group.  
> 
> There is a discussion about this caching somewhat deep in the Tramp
> manual.  But I think it would be much nicer if simple things like this
> worked out of the box, allowing users to experiment with value for
> `tramp-remote-path' via M-: (setq ... ) or some other variable-setting
> method, until they get it right.
> 
> Changing this variable's value doesn't alter the remote value of the
> PATH environment variable, much like changing exec-path locally doesn't
> change the local PATH environment variable.

We nowadays have variable-watching feature in Emacs, see
add-variable-watcher.  Could that facility be used in this case to
allow a more elegant solution?




This bug report was last modified 125 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.