From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: nnir problems with latest gnus
Date: Fri, 25 Sep 2020 09:18:24 -0700 [thread overview]
Message-ID: <877dshakz3.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87y2kxq1ri.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Hello all,
>
> I've been running into some strange errors in the past few days, all
> related in some way to nnir and possibly due to nnselect? I track emacs
> from git so I know I'm living dangerously...
>
> Anyway, one example. I have tried editing a message that I saved as a
> draft and I get the following error:
>
> ,----
> | Debugger entered--Lisp error: (void-function gnus-nnir-group-p)
> | gnus-nnir-group-p("nndraft:drafts")
> | gnus-draft-setup(1 "nndraft:drafts" t)
> | gnus-draft-edit-message()
> | funcall-interactively(gnus-draft-edit-message)
> | call-interactively(gnus-draft-edit-message record nil)
> | command-execute(gnus-draft-edit-message record)
> `----
>
> This is with gnus from Emacs from git as of a few minutes ago. Any
> pointers would be helpful.
This just means you have some stale *elc files lying around, with old
macro definitions in them. If you run "make bootstrap", or delete the
*elc files in the gnus directory and run plain "make", that should clear
it up.
> As an aside, are there any settings I should avoid with the appearance
> of nnselect? My .gnus dates back years and years...
I don't think nnselect has many (any?) user-facing options. It's very
much plumbing. Besides the fact that you can now make persistent search
groups, there should be nothing you can/should adjust.
next prev parent reply other threads:[~2020-09-25 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 16:06 Eric S Fraga
2020-09-25 16:18 ` Eric Abrahamsen [this message]
2020-09-25 16:57 ` Eric S Fraga
2020-09-25 17:06 ` Harry Putnam
2020-09-25 17:11 ` Harry Putnam
2020-09-25 18:10 ` Eric Abrahamsen
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=877dshakz3.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).