From: Michael Albinus <michael.albinus@gmx.de>
To: Aidan Gauland <aidalgol@no8wireless.co.nz>
Cc: emacs-devel@gnu.org
Subject: Re: Eshell and Sudo
Date: Sun, 17 Feb 2013 19:00:50 +0100 [thread overview]
Message-ID: <87obfiu8fh.fsf@gmx.de> (raw)
In-Reply-To: <87wqu7xq77.fsf@dimension8.tehua.net> (Aidan Gauland's message of "Sun, 17 Feb 2013 22:08:44 +1300")
Aidan Gauland <aidalgol@no8wireless.co.nz> writes:
> "John Wiegley" <johnw@newartisans.com> writes:
>> As a note, I do not think tramp should be involved by default in eshell/sudo.
>> This should be an optional module, em-tramp, which one can enable to bring in
>> such behavior. It makes using sudo on localhost many, many times slower, with
>> no functional benefit.
>
> I fully agree; it's confusing just about every new user.
This was discussed already. In short
* There is still "*sudo", which calls the external command. Like for all
other built-ins.
* If we remove eshell/sudo, some functionality might be lost, like
running eshell internal commands as arguments of sudo, and like
Tramp's password caching.
I understand that it might cause confusion the way it runs now. But I
wanted to recall the reasons I have added eshell/sudo 3 years ago.
> Thanks,
> Aidan Gauland
Best regards, Michael.
next prev parent reply other threads:[~2013-02-17 18:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 16:06 Eshell and Sudo Ian D
2013-02-16 19:07 ` Michael Albinus
2013-02-16 19:44 ` Aidan Gauland
2013-02-16 22:25 ` Aidan Gauland
2013-02-17 8:22 ` John Wiegley
2013-02-17 9:08 ` Aidan Gauland
2013-02-17 18:00 ` Michael Albinus [this message]
2013-02-17 17:47 ` Michael Albinus
2013-02-17 18:47 ` Aidan Gauland
2013-02-17 19:29 ` Michael Albinus
2013-02-17 23:28 ` Aidan Gauland
2013-02-18 5:07 ` Michael Albinus
2013-02-18 13:48 ` Stefan Monnier
2013-02-18 14:01 ` Michael Albinus
2013-02-18 16:24 ` Stefan Monnier
2013-02-18 19:20 ` 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=87obfiu8fh.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=aidalgol@no8wireless.co.nz \
--cc=emacs-devel@gnu.org \
/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).