* nnir problems with latest gnus
@ 2020-09-25 16:06 Eric S Fraga
2020-09-25 16:18 ` Eric Abrahamsen
0 siblings, 1 reply; 6+ messages in thread
From: Eric S Fraga @ 2020-09-25 16:06 UTC (permalink / raw)
To: ding
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.
As an aside, are there any settings I should avoid with the appearance
of nnselect? My .gnus dates back years and years...
Thank you,
eric
--
Eric S Fraga via Emacs 28.0.50 & org 9.4 on Debian bullseye/sid
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: nnir problems with latest gnus
2020-09-25 16:06 nnir problems with latest gnus Eric S Fraga
@ 2020-09-25 16:18 ` Eric Abrahamsen
2020-09-25 16:57 ` Eric S Fraga
2020-09-25 17:06 ` Harry Putnam
0 siblings, 2 replies; 6+ messages in thread
From: Eric Abrahamsen @ 2020-09-25 16:18 UTC (permalink / raw)
To: ding
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: nnir problems with latest gnus
2020-09-25 16:18 ` Eric Abrahamsen
@ 2020-09-25 16:57 ` Eric S Fraga
2020-09-25 17:06 ` Harry Putnam
1 sibling, 0 replies; 6+ messages in thread
From: Eric S Fraga @ 2020-09-25 16:57 UTC (permalink / raw)
To: ding
On Friday, 25 Sep 2020 at 09:18, Eric Abrahamsen wrote:
> 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.
And it does indeed! Thank you. I really must get in the habit of
making bootstrap more often but I would have hoped that the dependencies
in the Makefile would catch such things. Must be tricky, I guess.
> I don't think nnselect has many (any?) user-facing options.
Ah, okay. That's good (I think ;-)).
Thanks again,
eric
--
Eric S Fraga via Emacs 28.0.50 & org 9.4 on Debian bullseye/sid
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: nnir problems with latest gnus
2020-09-25 16:18 ` Eric Abrahamsen
2020-09-25 16:57 ` Eric S Fraga
@ 2020-09-25 17:06 ` Harry Putnam
2020-09-25 17:11 ` Harry Putnam
1 sibling, 1 reply; 6+ messages in thread
From: Harry Putnam @ 2020-09-25 17:06 UTC (permalink / raw)
To: ding
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> 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.
Harry writes:
I inadvertently just posted something very similar from trying to Send
finished message from nndrafts. see:
Subject: Possibe recent introduction of bug in nndrafts.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: nnir problems with latest gnus
2020-09-25 17:06 ` Harry Putnam
@ 2020-09-25 17:11 ` Harry Putnam
2020-09-25 18:10 ` Eric Abrahamsen
0 siblings, 1 reply; 6+ messages in thread
From: Harry Putnam @ 2020-09-25 17:11 UTC (permalink / raw)
To: ding
Harry Putnam <reader@newsguy.com> writes:
[...]
> Harry writes:
> I inadvertently just posted something very similar from trying to Send
> finished message from nndrafts. see:
>
> Subject: Possibe recent introduction of bug in nndrafts.
OOPS Wrong above, should have been:
Subject: May have run across a recently introduced bug
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: nnir problems with latest gnus
2020-09-25 17:11 ` Harry Putnam
@ 2020-09-25 18:10 ` Eric Abrahamsen
0 siblings, 0 replies; 6+ messages in thread
From: Eric Abrahamsen @ 2020-09-25 18:10 UTC (permalink / raw)
To: ding
Harry Putnam <reader@newsguy.com> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>
> [...]
>
>> Harry writes:
>> I inadvertently just posted something very similar from trying to Send
>> finished message from nndrafts. see:
>>
>> Subject: Possibe recent introduction of bug in nndrafts.
>
> OOPS Wrong above, should have been:
>
> Subject: May have run across a recently introduced bug
And I responded before reading this :)
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-09-25 18:15 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-25 16:06 nnir problems with latest gnus Eric S Fraga
2020-09-25 16:18 ` Eric Abrahamsen
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
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).