Gnus development mailing list
 help / color / mirror / Atom feed
From: Svend Tollak Munkejord <stm-direct_reply@pvv.org>
To: ding@gnus.org
Subject: Re: No Gnus v. 0.17 gives "Error in ~/.gnus: gnus-macroexpand-all"
Date: Sat, 21 May 2011 11:01:23 +0200	[thread overview]
Message-ID: <hddaaege8bg.fsf@microbel.pvv.ntnu.no> (raw)
In-Reply-To: <b4mliy6p7rg.fsf@jpl.org>

On 2011-05-17, Katsumi Yamaoka wrote:

> 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*.

Sorry, I should have remembered that.

Here is the backtrace:

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (void-function gnus-macroexpand-all)
  gnus-macroexpand-all((nnir-article-rsv (mail-header-number gnus-tmp-header)))
  byte-code("\300\301\302!\303BB\304\301\305!\306BB\307\310\311\312\313\314\301\315!\316BB\317\301\320!\321BB\322\323\324\301\325!\326BB\327\301\330!\331BB\332\333\334\335\336\337\340!\341BB\342BB\343\336\337\344!\345BB\346BB\347\336\337\350!\351BB\352BB\353\354\355\356\357\360\361\362\363\364\365\366\367\370\371\372\373\374\375\376\301\377!D\201@\0BB\257&\207" [78 macroexpand (mail-header-number gnus-tmp-header) (100) 83 (mail-header-subject gnus-tmp-header) (115) (115 gnus-tmp-subject-or-nil 115) (110 gnus-tmp-name 115) (65 (car ...) 115) (97 (or ... gnus-tmp-from) 115) (70 gnus-tmp-from 115) 120 (mail-header-xref gnus-tmp-header) (115) 68 (mail-header-date gnus-tmp-header) (115) (100 (gnus-dd-mmm ...) 115) (111 (gnus-date-iso8601 ...) 115) 77 (mail-header-id gnus-tmp-header) (115) 114 (mail-header-references gnus-tmp-header) (115) (99 (or ... 0) 100) (107 (gnus-summary-line-message-size gnus-tmp-header) 115) (76 gnus-tmp-lines 115) 90 or gnus-macroexpand-all (nnir-article-rsv (mail-header-number gnus-tmp-header)) (0) (100) 71 (nnir-article-group (mail-header-number gnus-tmp-header)) ("") (115) 103 (gnus-group-short-name (nnir-article-group ...)) ("") (115) (79 gnus-tmp-downloaded 99) (73 gnus-tmp-indentation 115) (84 (if ... "" ...) 115) (82 gnus-tmp-replied 99) (91 gnus-tmp-opening-bracket 99) (93 gnus-tmp-closing-bracket 99) (62 (make-string gnus-tmp-level 32) 115) ...] 41)
  (defvar gnus-summary-line-format-alist (byte-code "\300\301\302!\303BB\304\301\305!\306BB\307\310\311\312\313\314\301\315!\316BB\317\301\320!\321BB\322\323\324\301\325!\326BB\327\301\330!\331BB\332\333\334\335\336\337\340!\341BB\342BB\343\336\337\344!\345BB\346BB\347\336\337\350!\351BB\352BB\353\354\355\356\357\360\361\362\363\364\365\366\367\370\371\372\373\374\375\376\301\377!D\201@\0BB\257&\207" [78 macroexpand ... ... 83 ... ... ... ... ... ... ... 120 ... ... 68 ... ... ... ... 77 ... ... 114 ... ... ... ... ... 90 or gnus-macroexpand-all ... ... ... 71 ... ... ... 103 ... ... ... ... ... ... ... ... ... ... ...] 41) ("/home/pvv/l/stm/gnus-n0-17/lisp/gnus-sum.elc" . 50960))
  require(gnus-sum)
  byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\305\306\307\310\311\312\311\313\314\315&	\207" [require nnoo nnheader nnmail gnus-sum custom-declare-group gnus-namazu nil "Search nnmh and nnml groups in Gnus with Namazu." :group namazu gnus :prefix "gnus-namazu-"] 10)
  require(gnus-namazu)
  eval-buffer(#<buffer  *load*> nil "/home/pvv/l/stm/.gnus" nil t)  ; Reading at buffer position 2693
  load-with-code-conversion("/home/pvv/l/stm/.gnus" "/home/pvv/l/stm/.gnus" nil t)
  load("~/.gnus" nil t)
  gnus-read-init-file()
  gnus-1(nil nil nil)
  gnus(nil)
  call-interactively(gnus t nil)
  execute-extended-command(nil)
  call-interactively(execute-extended-command nil nil)
--8<---------------cut here---------------end--------------->8---

Does it tell you something?

> 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).

There is no such file in my home directory (except the one of No Gnus
v0.17). Do I need to disable the Gnus that comes with Emacs
explicitly, other than saying

(setq load-path (cons (expand-file-name "~/gnus-n0-17/lisp") load-path))

in ~/.emacs?

>> 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. ;-)

Yes, indeed, but in this case, that wouldn't be necessary, since the
problem only emerges in the new version ;-)

Regards,
-- 
Svend Tollak Munkejord 




  reply	other threads:[~2011-05-21  9:01 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
2011-05-21  9:01   ` Svend Tollak Munkejord [this message]
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=hddaaege8bg.fsf@microbel.pvv.ntnu.no \
    --to=stm-direct_reply@pvv.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).