GNU bug report logs - #34943
27.0.50; Tramp explicte-shell-file-name not work and not safe local variable

Previous Next

Package: emacs;

Reported by: Shuguang Sun <shuguang79 <at> qq.com>

Date: Fri, 22 Mar 2019 06:35:01 UTC

Severity: normal

Tags: fixed

Found in version 27.0.50

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


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

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Shuguang Sun <shuguang79 <at> qq.com>
Cc: 34943 <at> debbugs.gnu.org
Subject: Re: bug#34943: 27.0.50;
 Tramp explicte-shell-file-name not work and not safe local variable
Date: Sat, 23 Mar 2019 09:59:42 +0100
Shuguang Sun <shuguang79 <at> qq.com> writes:

[Pls Cc 34943 <at> debbugs.gnu.org, and NOT bug-gnu-emacs <at> gnu.org]

Hi,

> The patch works. Thanks.

Thanks for checking.

>>> Another issue, the emacs treat explicit-shell-file-name and
>>> explicit-bash-args as non-safe local variables and ask how to deal
>>> it (Y/N/! ...).  In the previous version of tramp (about Feb), it
>>> takes these two variables as safe which I think is reasonable
>>> because user sets it in tramp-way explicitely and it is only used in
>>> tramp only.
>>
>> I'll check when the first problem is solved.
>
> FYI. explicit-shell-file-name and explicit-bash-args are still
> non-safe local variables now.

This shall be fixed now as well. Could you, pls, confirm?

Everything pushed to master.

Best regards, Michael.




This bug report was last modified 6 years and 62 days ago.

Previous Next


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