From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Recursive require with emacs24?
Date: Thu, 24 Feb 2011 14:11:53 +0100 [thread overview]
Message-ID: <yb0wrkpziee.fsf@dod.no> (raw)
In-Reply-To: <m262s9y4ky.fsf@nwalsh.com>
>>>>> Norman Walsh <ndw@nwalsh.com>:
> So, I went off and built emacs24 to see what that was like...but I get
> a strange error about "recursive require for 'gnus-sum in ~/.gnus"
> when I try to load either the gnus that's part of emacs24 or the
> nognus-0.13 that I downloaded yesterday.
> This happens even if I remove all the require's from my .gnus file.
> $ grep require .gnus | grep -v ^\;
> $
> Uhm. Just me?
Hm... I haven't tried emacs 24 yet, but I have the following at the
start of my .gnus.el:
; git gnus specific variables at the start. Remove when going production.
(load "gnus-load")
The stuff in gnus-load is related to using no gnus, I think.
But that shouldn't be needed when using the native emacs24 gnus, I
guess...?
next prev parent reply other threads:[~2011-02-24 13:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 0:11 State of the art for HTML email Norman Walsh
2011-02-24 0:18 ` Edward O'Connor
2011-02-24 0:23 ` Norman Walsh
2011-02-24 23:08 ` Dave Goldberg
2011-02-25 15:46 ` Norman Walsh
2011-02-24 7:49 ` Reiner Steib
2011-02-24 11:42 ` Norman Walsh
2011-02-24 7:58 ` Steinar Bang
2011-02-24 12:28 ` Lars Ingebrigtsen
2011-02-24 12:55 ` Recursive require with emacs24? Norman Walsh
2011-02-24 13:11 ` Steinar Bang [this message]
2011-02-25 3:39 ` Lars Ingebrigtsen
2011-02-25 15:19 ` Norman Walsh
2011-03-05 12:07 ` Lars Magne Ingebrigtsen
2011-03-05 17:02 ` Andreas Schwab
2011-03-18 14:02 ` Recursive require with nognus? Norman Walsh
2011-03-18 18:42 ` nnir is pwetty kewl! (Was: Recursive require with nognus?) Steinar Bang
2011-03-18 19:24 ` Norman Walsh
2011-03-18 21:40 ` nnir is pwetty kewl! Steinar Bang
2011-03-19 21:34 ` Norman Walsh
2011-03-20 18:12 ` Steinar Bang
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=yb0wrkpziee.fsf@dod.no \
--to=sb@dod.no \
--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).