all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Thu, 08 Jun 2017 20:49:01 -0400	[thread overview]
Message-ID: <87poeevvcy.fsf@users.sourceforge.net> (raw)
In-Reply-To: <565849C0-5191-4FD9-A012-0FA9237B89CA@gmail.com> (Yegor Timoshenko's message of "Fri, 9 Jun 2017 01:21:05 +0300")

Yegor Timoshenko <yegortimoshenko@gmail.com> writes:

>> Don't you also need (push 'eshell-tramp eshell-modules-list)?
>
> I never did that and it seemed to work fine (I had to manually alias
> sudo to eshell/sudo, though).

Aha, that explains it.

>> Does this work from M-x shell?
>
> No, this one is specific to eshell (actually, to em-tramp
> eshell/sudo).

So by "No" you mean "Yes" (it works)? ;)

>> Does C-x C-f /sudo::/tmp/a/ work?
>
> It works.
>
>> 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).
>
> It is reproducible both in graphical and terminal environments.

Hmm, if you step through eshell-plain-command does it call
eshell-lisp-command or eshell-external-command to run "ls"?  (for me it
goes through eshell-lisp-command)





  reply	other threads:[~2017-06-09  0:49 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
2017-06-08 22:21         ` Yegor Timoshenko
2017-06-09  0:49           ` npostavs [this message]
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=87poeevvcy.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.