From: Yegor Timoshenko <yegortimoshenko@gmail.com>
To: npostavs@users.sourceforge.net
Cc: 27167@debbugs.gnu.org
Subject: bug#27167: eshell/sudo doesn't handle absolute command names correctly
Date: Wed, 7 Jun 2017 21:42:37 +0300 [thread overview]
Message-ID: <3F441A99-6FD7-45C9-83B5-8922EDEB9DB7@gmail.com> (raw)
In-Reply-To: <87efuwx8kx.fsf@users.sourceforge.net>
Still reproducible, even with -Q flag. Affected versions:
GNU Emacs 25.2.1 (x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version 10.9.5 (Build 13F1911)) of 2017-04-21
GNU Emacs 25.2.1 (x86_64-apple-darwin16, NS appkit-1504.83 Version 10.12.5 (Build 16F73)) of 2017-06-07
next prev parent reply other threads:[~2017-06-07 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 16:35 bug#27167: eshell/sudo doesn't handle absolute command names correctly Yegor Timoshenko
2017-06-07 12:53 ` npostavs
2017-06-07 18:42 ` Yegor Timoshenko [this message]
2017-06-11 12:48 ` npostavs
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=3F441A99-6FD7-45C9-83B5-8922EDEB9DB7@gmail.com \
--to=yegortimoshenko@gmail.com \
--cc=27167@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).