GNU bug report logs -
#33781
tramp trouble when PATH is very long
Previous Next
Reported by: Glenn Morris <rgm <at> gnu.org>
Date: Mon, 17 Dec 2018 19:17:02 UTC
Severity: minor
Tags: fixed
Found in version 27.0.50
Fixed in version 27.1
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #33 received at 33781 <at> debbugs.gnu.org (full text, mbox):
Glenn Morris <rgm <at> gnu.org> writes:
> Michael Albinus wrote:
>
>> The first problem was, that `tramp-remote-path' has lost its autoload
>> cookie. Requiring tramp-sh is a valid workaround, but the better
>> solution is to bring the autoload cookie back into place. Which I did.
>
> That's a shame, I always like to see variables get un-autoloaded.
Same here. Well, the variables go to tramp-loaddefs.el, which is less
annoying than loaddefs.el, isn't it?
The problem is setting a user option. If you want to set just a value,
it works fine:
--8<---------------cut here---------------start------------->8---
# emacs -Q --eval '(customize-set-variable (quote tramp-verbose) 6)'
--8<---------------cut here---------------end--------------->8---
This doesn't work, if you need the initial value of the user option in
order to compute a new value:
--8<---------------cut here---------------start------------->8---
# emacs -Q --eval '(customize-set-variable (quote tramp-remote-path) (add-to-list (quote tramp-remote-path) (quote tramp-own-remote-path)))'
=> customize-set-variable: Symbol’s value as variable is void: tramp-remote-path
--8<---------------cut here---------------end--------------->8---
If I would know a trick how to apply the latter one, I could get rid of
the respective autoloads.
Best regards, Michael.
This bug report was last modified 6 years and 154 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.