From: Michael Albinus <michael.albinus@gmx.de>
To: "Aleš Bizjak" <ales.bizjak0@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Strange behaviour of sudo and eshell
Date: Mon, 25 Feb 2013 09:37:32 +0100 [thread overview]
Message-ID: <8738wkzt4j.fsf@gmx.de> (raw)
In-Reply-To: <CAKVLaw4aM9ptv=L5s6TpJMW-PuAK_ST-kdmbdh8bcZ-sjk21Cg@mail.gmail.com> ("Aleš Bizjak"'s message of "Sun, 24 Feb 2013 22:45:16 +0100")
Aleš Bizjak <ales.bizjak0@gmail.com> writes:
Hi Aleš,
> Which bzr version have you used? There was a fix recently, in bzr
> #111277.
>
> I used the latest one from the gnu ftp server.
>
> ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-24.2.93.tar.xz
>
> I don't know which bzr version that is, sorry.
That prerelease is from Feb 7th. The fix I have mentioned was committed
on Feb 18th.
So you might check with the next prerelease version, which is expected
later this week.
Best regards, Michael.
prev parent reply other threads:[~2013-02-25 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 17:14 Strange behaviour of sudo and eshell Aleš Bizjak
2013-02-24 20:45 ` Michael Albinus
2013-02-24 21:45 ` Aleš Bizjak
2013-02-25 8:37 ` Michael Albinus [this message]
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=8738wkzt4j.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=ales.bizjak0@gmail.com \
--cc=help-gnu-emacs@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.
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).