Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: ~/.gnus.registry.eioio (was Re: Emacs 24...)
Date: Wed, 22 Feb 2012 07:21:15 -0500	[thread overview]
Message-ID: <m2ty2j9hz8.fsf_-_@nwalsh.com> (raw)
In-Reply-To: <87ipizap35.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 21 Feb 2012 15:50:06 -0500")

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

Ted Zlatanov <tzz@lifelogs.com> writes:
> It's frustrating, how many times this has come up.

Yes. I finally had to build CEDET from trunk, like I said, to get
Emacs 24 to work at all. So this morning it "just works". Obviously I
had done something carelessly yesterday. My bad.

However, I do get this warning now:

  Warning: The Gnus registry could not be loaded from
  ~/.gnus.registry.eioio, creating a new one; The Gnus registry could
  not be loaded from ~/.gnus.registry.eioio, creating a new one

Despite the warning, Emacs seems to load and save the file. At least,
it doesn't disappear and seems to get larger...

I did delete the one from Emacs 23 but that didn't fix the warning.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | A rusty nail placed near a faithful
http://nwalsh.com/            | compass, will sway it from the truth,
                              | and wreck the argosy.--Sir Walter Scott

[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]

  reply	other threads:[~2012-02-22 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21 13:53 Emacs 24 Norman Walsh
2012-02-21 15:36 ` Andreas Schwab
2012-02-21 17:20   ` Norman Walsh
2012-02-21 20:50     ` Ted Zlatanov
2012-02-22 12:21       ` Norman Walsh [this message]
2012-02-22 12:56         ` ~/.gnus.registry.eioio (was Re: Emacs 24...) 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=m2ty2j9hz8.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).