From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: Re: Emacs 25 & the registry
Date: Wed, 28 Sep 2016 16:14:04 +0200 [thread overview]
Message-ID: <87shskm7rn.fsf@nwalsh.com> (raw)
In-Reply-To: <87lgyg2ibw.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 25 Sep 2016 21:57:07 +0800")
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> I decided to give Emacs 25.1.3 a try. Curiously, when I start gnus
>> (v5.13), it pauses part way through and asks me to confirm that I want
>> to rename ~/.gnus.registry.eioio to ~/.gnus.registry.eioio
>
> Surely it asks to rename to ~/.gnus.registry.eieio?
Yes, sorry. Typo on my part.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Nothing can exceed the vanity of our
http://nwalsh.com/ | existence but the folly of our
| pursuits.--Oliver Goldsmith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 172 bytes --]
next prev parent reply other threads:[~2016-09-28 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 15:54 Norman Walsh
2016-09-25 13:57 ` Eric Abrahamsen
2016-09-28 14:14 ` Norman Walsh [this message]
2016-12-11 14:43 ` Norman Walsh
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=87shskm7rn.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=ding@gnus.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 NNTP newsgroup(s).