unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Shuguang Sun <shuguang79@qq.com>
Cc: 34943@debbugs.gnu.org
Subject: 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	[thread overview]
Message-ID: <87tvfu3r0h.fsf@gmx.de> (raw)
In-Reply-To: <vk5ybm229qin.fsf@qq.com>+84B887AED736CBAA (Shuguang Sun's message of "Sat, 23 Mar 2019 12:13:52 +0800")

Shuguang Sun <shuguang79@qq.com> writes:

[Pls Cc 34943@debbugs.gnu.org, and NOT bug-gnu-emacs@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.





  parent reply	other threads:[~2019-03-23  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  6:17 bug#34943: 27.0.50; Tramp explicte-shell-file-name not work and not safe local variable Shuguang Sun
2019-03-22  7:16 ` Shuguang Sun
2019-03-22  7:56   ` Shuguang Sun
2019-03-22 14:14   ` Michael Albinus
2019-03-22 14:13 ` Michael Albinus
2019-03-23  4:13   ` Shuguang Sun
     [not found]   ` <vk5ybm229qin.fsf@qq.com>
2019-03-23  8:59     ` Michael Albinus [this message]
2019-03-23 15:41       ` Shuguang Sun
2019-03-24 12:42         ` Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tvfu3r0h.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=34943@debbugs.gnu.org \
    --cc=shuguang79@qq.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).