From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 5303@debbugs.gnu.org, cyd@stupidchicken.com
Subject: bug#5303: 23.1.91; Cannot load .emacs-history from savehist.el
Date: Wed, 20 Jan 2010 20:18:24 +0200 [thread overview]
Message-ID: <83bpgo7i8f.fsf@gnu.org> (raw)
In-Reply-To: <nq1vhksrzw.fsf@alcatel-lucent.com>
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: "'Lennart Borgman'" <lennart.borgman@gmail.com>,
> "'Eli Zaretskii'" <eliz@gnu.org>,
> "'Chong Yidong'" <cyd@stupidchicken.com>,
> "5303\@debbugs.gnu.org" <5303@debbugs.gnu.org>
> Date: Wed, 20 Jan 2010 16:41:55 +0100
>
> > Obviously, speaking generally, this needs to be fixed before the 23.2 release,
> > since it is a _regression_. The problem never manifested itself previously
> > (Emacs 20 through 23.1 release), even if, as some have suggested, 23.1 perhaps
> > dodged a bullet.
>
> On my colleague's PC, I could reproduce the problem with
>
> GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
> of 2009-01-15 on LENNART-69DE564
>
> It doesn't seem to be a regression wrt Emacs 23.1, at least.
It doesn't happen for me with stock Emacs 23.1, so it _is_ a
regression.
next prev parent reply other threads:[~2010-01-20 18:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8F73D1539CE042B8A9B48F767127C43B@us.oracle.com>
2010-01-16 19:33 ` bug#5303: 23.1.91; Cannot load .emacs-history from savehist.el Chong Yidong
2010-01-16 20:03 ` Lennart Borgman
2010-01-16 21:11 ` Kevin Rodgers
2010-01-17 16:54 ` Michael Albinus
2010-01-17 16:58 ` Lennart Borgman
2010-01-17 17:18 ` Michael Albinus
2010-01-17 19:46 ` Lennart Borgman
2010-01-19 13:40 ` Michael Albinus
2010-01-19 17:39 ` Drew Adams
2010-01-19 19:28 ` Eli Zaretskii
2010-01-19 19:30 ` Chong Yidong
2010-01-19 19:36 ` Michael Albinus
2010-01-19 21:24 ` Eli Zaretskii
2010-01-19 22:13 ` Eli Zaretskii
2010-01-20 1:25 ` Lennart Borgman
2010-01-20 8:44 ` Michael Albinus
2010-01-20 8:46 ` Lennart Borgman
2010-01-20 8:56 ` Michael Albinus
2010-01-20 9:02 ` Lennart Borgman
2010-01-20 9:45 ` Michael Albinus
2010-01-20 10:39 ` Eli Zaretskii
2010-01-20 10:50 ` Michael Albinus
2010-01-19 19:37 ` Drew Adams
2010-01-19 19:44 ` Eli Zaretskii
2010-01-19 19:52 ` Drew Adams
2010-01-19 21:31 ` Eli Zaretskii
2010-01-19 20:01 ` Lennart Borgman
2010-01-20 9:00 ` Michael Albinus
2010-01-20 9:04 ` Lennart Borgman
2010-01-20 10:13 ` Michael Albinus
2010-01-20 10:38 ` Lennart Borgman
2010-01-20 12:01 ` Michael Albinus
2010-01-20 12:03 ` Lennart Borgman
2010-01-20 12:15 ` Michael Albinus
2010-01-20 12:21 ` Lennart Borgman
2010-01-20 15:32 ` Drew Adams
2010-01-20 15:41 ` Michael Albinus
2010-01-20 17:33 ` Drew Adams
2010-01-20 18:18 ` Eli Zaretskii [this message]
2010-01-21 1:02 ` Lennart Borgman
2010-01-21 18:24 ` Eli Zaretskii
2010-01-21 18:42 ` Chong Yidong
2010-01-21 20:41 ` Chong Yidong
2010-01-20 18:17 ` Eli Zaretskii
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=83bpgo7i8f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5303@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--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).