From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Michael Albinus <michael.albinus@gmx.de>
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: Tue, 10 Apr 2012 12:23:08 -0400 [thread overview]
Message-ID: <jwvty0rv9ri.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r4vvsjor.fsf@gmx.de> (Michael Albinus's message of "Tue, 10 Apr 2012 17:14:28 +0200")
>> "sudo . .eshell/history" means "execute the commands in .eshell/history
>> as user `root'". I.e. it's very different from
>> ". /sudo::.eshell/history" which runs those command as the current user.
> I haven't said there's only one way to do it :-) I mean we should
> think about, before we disable builtins in sudo. I'm still not
> convinced it is a bug.
> In eshell, one must understand how file names are handled.
I'd be happy to hear of arguments in favor of the current behavior of
eshell/sudo w.r.t builtins.
Stefan
next prev parent reply other threads:[~2012-04-10 16:23 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 [this message]
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
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=jwvty0rv9ri.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11194@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--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).