From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: No Gnus v. 0.17 gives "Error in ~/.gnus: gnus-macroexpand-all"
Date: Tue, 17 May 2011 08:04:19 +0900 [thread overview]
Message-ID: <b4mliy6p7rg.fsf@jpl.org> (raw)
In-Reply-To: <hddoc333pb3.fsf@microbel.pvv.ntnu.no>
Svend Tollak Munkejord wrote:
> Even though I'm not so much into Gnus fiddling anymore, I thought I'd
> try to upgrade from No Gnus v. 0.8 (the previous 1st May release?) to
> v. 0.17. However, Gnus didn't like my .gnus:
> byte-code: Error in ~/.gnus: gnus-macroexpand-all
> This is all that's said, so I don't know how to fix it.
First of all, in such a case normally what you have to do first
is debugging and report a backtrace. See:
(info "(gnus)Troubleshooting") <-- Type `C-x C-e' here.
;; `M-x set-variable RET debug-on-error RET t RET', or
;; `M-x toggle-debug-on-error RET', launch Gnus, and report what
;; Emacs says in the buffer named *Backtrace*.
I guess you load an old gnus-util.el(c), that is not of No Gnus
v0.17, and does not provide the function `gnus-macroexpand-all'
(new gnus-sum.el(c) uses it).
> Am I better off staying with the standard Gnus (Gnus/5.13 (Gnus
> v5.13) Emacs/23.2 (gnu/linux)), which does not complain, or does
> anyone have a good idea?
I can only tell is that Gnus developers will probably not be
interested in debugging of old Gnus. ;-)
next prev parent reply other threads:[~2011-05-16 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 10:36 Svend Tollak Munkejord
2011-05-16 23:04 ` Katsumi Yamaoka [this message]
2011-05-21 9:01 ` Svend Tollak Munkejord
2011-05-30 18:48 ` Lars Magne Ingebrigtsen
2011-05-30 19:22 ` Svend Tollak Munkejord
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=b4mliy6p7rg.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).