From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Cray Elliott <mp2e@archlinux.us>, 11194@debbugs.gnu.org
Subject: bug#11194: 24.0.95; sudo rm doesn't work with absolute directory paths on the file system
Date: Sun, 22 Apr 2012 19:47:47 +0200 [thread overview]
Message-ID: <87k417sloc.fsf@gmx.de> (raw)
In-Reply-To: <jwv7gx9vo4v.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 20 Apr 2012 22:03:03 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> I'd be happy to hear of arguments in favor of the current behavior of
>>> eshell/sudo w.r.t builtins.
>> I've checked the implementation of eshell/sudo: It simply let-binds
>> default-directory to "/sudo:user@host:dir", and let the command like rm
>> run. That's why the built-in version of rm is in place.
>> Another implementation of sudo would not be in the spirit of eshell, I
>> think.
>
> Spirit or not, the resulting behavior for `sudo' makes no sense and
> should be fixed,
Last attempt to convince you: The eshell manual gives as example
~ $ cd /ssh:otherhost:/etc
/ssh:user@otherhost:/etc $ sudo find-file shadow
If you disable built-in commands inside sudo, you would disable all
other Lisp functions as well. Do we want this?
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2012-04-22 17:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 10:45 bug#11194: 24.0.95; sudo rm doesn't work with absolute directory paths on the file system Cray Elliott
2012-04-08 11:00 ` Michael Albinus
2012-04-09 2:20 ` Stefan Monnier
2012-04-09 18:08 ` Michael Albinus
2012-04-10 1:58 ` Stefan Monnier
2012-04-10 7:07 ` Michael Albinus
2012-04-10 13:01 ` Stefan Monnier
2012-04-10 14:00 ` Michael Albinus
2012-04-10 14:55 ` Stefan Monnier
2012-04-10 15:14 ` Michael Albinus
2012-04-10 16:23 ` Stefan Monnier
2012-04-10 16:41 ` Thierry Volpiatto
2012-04-10 17:07 ` Thierry Volpiatto
2012-04-10 18:00 ` Stefan Monnier
2012-04-20 13:35 ` Michael Albinus
2012-04-21 2:03 ` Stefan Monnier
2012-04-22 17:47 ` Michael Albinus [this message]
2012-04-24 1:52 ` Stefan Monnier
2012-04-25 9:32 ` Michael Albinus
2012-04-10 16:35 ` Thierry Volpiatto
2012-04-10 16:57 ` Thierry Volpiatto
2012-04-20 13:38 ` Michael Albinus
2012-04-20 20:58 ` Thierry Volpiatto
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=87k417sloc.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=11194@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=mp2e@archlinux.us \
/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).