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: Mon, 18 Feb 2013 06:07:51 +0100 [thread overview]
Message-ID: <87ppzyxl94.fsf@gmx.de> (raw)
In-Reply-To: <8738wur054.fsf@dimension8.tehua.net> (Aidan Gauland's message of "Mon, 18 Feb 2013 12:28:07 +1300")
Aidan Gauland <aidalgol@no8wireless.co.nz> writes:
Hi Aidan,
> OK, then I'd say go ahead and commit the changes.
I will, for sure. The question is rather whether to commit in the
emacs-24 branch, or in trunk. I prefer the emacs-24 branch, because the
changes are such simple. Glenn? Stefan?
> I hope this clears up the recursive load problem. Any idea why this
> appears erratically (for some people and not others)? Have you been
> able to reproduce it consistently?
Maybe there is a misunderstanding. The recursive load problem happens
consistently with the recipe given by Ian. This is fixed by the (require
'tramp) forms in the patch.
I was rather surprised to see that a "sudo id" sometimes refused to
run. But this is covered by my second patch, which handles the defense
mechanism of Tramp.
> Regards,
> Aidan Gauland
Best regards, Michael.
next prev parent reply other threads:[~2013-02-18 5:07 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppzyxl94.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 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.