From: npostavs@users.sourceforge.net
To: Yegor Timoshenko <yegortimoshenko@gmail.com>
Cc: 27169@debbugs.gnu.org
Subject: bug#27169: eshell/sudo doesn't work with protected directories
Date: Wed, 07 Jun 2017 20:50:55 -0400 [thread overview]
Message-ID: <8760g7xpxs.fsf@users.sourceforge.net> (raw)
In-Reply-To: <92D4739F-7FCF-4658-B0C0-D20CEB863150@gmail.com> (Yegor Timoshenko's message of "Wed, 7 Jun 2017 21:43:18 +0300")
Yegor Timoshenko <yegortimoshenko@gmail.com> writes:
>> Works for me, can you reproduce this from 'emacs -Q'? What Emacs
>> version are you using?
>
> 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
>
> Yes, it's reproducible with -Q flag, provided that you execute (require 'em-tramp) in *scratch* buffer.
Don't you also need (push 'eshell-tramp eshell-modules-list)?
Once I do that, I'm able to reproduce #27167, but not this bug:
~/src $ sudo /bin/cat foo
/sudo:root@localhost:/home/npostavs/src/bin/cat: command not found
~/src $ cd /tmp
/tmp $ sudo ls a/b
a/b
> I believe it can be a platform-specific bug (I use macOS).
Possible. Does this work from M-x shell? Does C-x C-f /sudo::/tmp/a/
work? Does it make a difference if you run from the terminal vs running
graphically (there's at least one macOS bug where this makes a
difference, #21573).
next prev parent reply other threads:[~2017-06-08 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 16:47 bug#27169: eshell/sudo doesn't work with protected directories Yegor Timoshenko
2017-06-07 12:59 ` npostavs
[not found] ` <9B3DCDF4-DA3C-40CB-B5E6-61FD2BB6DEC8@gmail.com>
2017-06-07 18:43 ` Yegor Timoshenko
2017-06-08 0:20 ` npostavs
2017-06-08 0:50 ` npostavs [this message]
2017-06-08 22:21 ` Yegor Timoshenko
2017-06-09 0:49 ` npostavs
2020-09-04 6:04 ` bug#27168: " Lars Ingebrigtsen
2020-10-07 3:29 ` Lars Ingebrigtsen
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=8760g7xpxs.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27169@debbugs.gnu.org \
--cc=yegortimoshenko@gmail.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.