From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: shuguang79@qq.com, 35241@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#35241: 27.0.50; Tramp can't decrypt .authinfo.gpg in Win 10
Date: Tue, 16 Apr 2019 17:47:42 +0300 [thread overview]
Message-ID: <83k1fugg6p.fsf@gnu.org> (raw)
In-Reply-To: <87pnpm3yhr.fsf@gmx.de> (message from Michael Albinus on Tue, 16 Apr 2019 14:50:40 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Tue, 16 Apr 2019 14:50:40 +0200
> Cc: 35241@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
>
> Relative file names are not forbidden as part of exec-path. Shall we ban
> them (with an error message)? Or shall we ignore them, silently? Don't know.
>
> I'd vote for the latter (including proper documentation).
Maybe executable-find should ignore them if default-directory is
remote?
next prev parent reply other threads:[~2019-04-16 14:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vk5yimvkeyca.fsf@qq.com>
2019-04-16 1:20 ` bug#35241: 27.0.50; Tramp can't decrypt .authinfo.gpg in Win 10 Noam Postavsky
2019-04-16 4:54 ` Shuguang Sun
2019-04-16 7:18 ` Michael Albinus
2019-04-16 9:34 ` Shuguang Sun
2019-04-16 9:42 ` Shuguang Sun
[not found] ` <vk5y5zrei997.fsf@qq.com>
2019-04-16 12:50 ` Michael Albinus
2019-04-16 14:47 ` Eli Zaretskii [this message]
2019-04-16 16:20 ` Michael Albinus
2019-04-16 16:42 ` Eli Zaretskii
2019-04-16 19:42 ` Michael Albinus
2019-04-17 7:35 ` Michael Albinus
2019-04-17 12:08 ` Michael Albinus
2019-04-17 14:29 ` Noam Postavsky
2019-04-17 19:09 ` Michael Albinus
2019-04-17 17:07 ` Eli Zaretskii
2019-04-16 15:20 ` Noam Postavsky
2019-04-16 16:03 ` Eli Zaretskii
2019-04-16 16:12 ` Michael Albinus
2019-04-17 2:02 ` Shuguang Sun
[not found] ` <vk5ywojt2xu2.fsf@qq.com>
2019-04-17 7:24 ` Michael Albinus
2019-04-12 2:44 Shuguang Sun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k1fugg6p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35241@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=npostavs@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.