From: Ken Hori <fplemma@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 6226@debbugs.gnu.org
Subject: bug#6226: Please add a customizable option to NOT call tramp for every sudo command
Date: Fri, 21 May 2010 20:50:12 -0700 [thread overview]
Message-ID: <AANLkTinM_5MPBO3ap7i2gP9xS7h-r8MB_K1xZkAISWNk@mail.gmail.com> (raw)
In-Reply-To: <87zkzv3wg4.fsf@gmx.de>
Yes, I am aware of that. Thank you. And I'm also aware
I can just remove eshell-unix from eshell-modules-list.
Inside em-unix.el are
eshell/agrep
eshell/cat
eshell/cp
eshell/diff
eshell/du
eshell/egrep
eshell/fgrep
eshell/glimpse
eshell/grep
eshell/info
eshell/ln
eshell/locate
eshell/make
eshell/man
eshell/mkdir
eshell/mv
eshell/occur
eshell/rm
eshell/rmdir
eshell/su
eshell/sudo
eshell/time
eshell/whoami
Some are beneficial, but many command wrappers are not -- at
least to me.
I think it's a good idea to give the users freedom
of choosing which eshell commands to opt-in or out.
On Wed, May 19, 2010 at 11:43 PM, Michael Albinus
<michael.albinus@gmx.de> wrote:
> Ken Hori <fplemma@gmail.com> writes:
>
>> I've recently noticed Eshell is now calling tramp for every sudo
>> command. Tramp is very slow, and I believe for most cases tramp
>> intermediation is unnecessary.
>>
>> Could we please add a customizable switch to enable/disable
>> eshell/sudo? Disabling eshell/sudo by default would be even better.
>
> All built-in commands of eshell can be disabled by prepending "*". See
>
> (info "(eshell)Built-ins")
>
> That means, you shall call
>
> ~ $ *sudo command
>
> Best regards, Michael.
>
next prev parent reply other threads:[~2010-05-22 3:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 4:42 bug#6226: Please add a customizable option to NOT call tramp for every sudo command Ken Hori
2010-05-20 6:43 ` Michael Albinus
2010-05-22 3:50 ` Ken Hori [this message]
2010-05-22 22:03 ` Michael Albinus
2010-05-23 13:22 ` Stefan Monnier
2010-05-23 17:15 ` Michael Albinus
2010-05-23 18:54 ` Juanma Barranquero
2010-05-24 8:16 ` Ken Hori
2010-05-24 14:05 ` Stefan Monnier
2010-05-26 3:26 ` Michael Albinus
2010-05-26 5:55 ` Thierry Volpiatto
2010-05-26 10:16 ` Michael Albinus
2010-05-26 13:30 ` Stefan Monnier
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=AANLkTinM_5MPBO3ap7i2gP9xS7h-r8MB_K1xZkAISWNk@mail.gmail.com \
--to=fplemma@gmail.com \
--cc=6226@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).