bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Gerd Möllmann]

I get the following error when starting Gnus with M-x gnus.

  No such function: nnfolder-server-opened

The function nnfolder-server-opened is indeed defined nowhere I can
find.  In case it matters, I had a Gnus autosave file.  After M-x gnus,
I answered 'n' to the question if the autosave file should be used.
After that, the error is signaled.

In GNU Emacs 30.0.50 (build 1, aarch64-apple-darwin22.6.0, NS
 appkit-2299.70 Version 13.5 (Build 22G74)) of 2023-08-21 built on
 Mini.fritz.box
Repository revision: 18c85306ac211402e4772bdb94b63d300a2ac119
Repository branch: master
Windowing system distributor 'Apple', version 10.3.2299
System Description:  macOS 13.5

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Gerd Möllmann]

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> I get the following error when starting Gnus with M-x gnus.
>
>   No such function: nnfolder-server-opened
>
> The function nnfolder-server-opened is indeed defined nowhere I can
> find.  In case it matters, I had a Gnus autosave file.  After M-x gnus,
> I answered 'n' to the question if the autosave file should be used.
> After that, the error is signaled.

Once nnfolder is loaded, nnfolder-server-opened is defined as a
function.  It is defined by the macro

(nnoo-define-basics nnfolder)

in nnfolder.el.

I can work around this by manually requiring nnfolder in init.el.  Alas,
I don't know much about Gnus internals to determine what the right fix
would be.

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Andreas Schwab]

On Aug 22 2023, Gerd Möllmann wrote:

> I get the following error when starting Gnus with M-x gnus.
>
>   No such function: nnfolder-server-opened
>
> The function nnfolder-server-opened is indeed defined nowhere I can
> find.

It should be defined by (nnoo-define-basics nnfolder).

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Gerd Möllmann]

Andreas Schwab <schwab@suse.de> writes:

> It should be defined by (nnoo-define-basics nnfolder).

Right, I found that in the meantime.  The function is indeed defined
once nnfolder is loaded.

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Eli Zaretskii]

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Date: Tue, 22 Aug 2023 09:29:39 +0200
> 
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> 
> > I get the following error when starting Gnus with M-x gnus.
> >
> >   No such function: nnfolder-server-opened
> >
> > The function nnfolder-server-opened is indeed defined nowhere I can
> > find.  In case it matters, I had a Gnus autosave file.  After M-x gnus,
> > I answered 'n' to the question if the autosave file should be used.
> > After that, the error is signaled.
> 
> Once nnfolder is loaded, nnfolder-server-opened is defined as a
> function.  It is defined by the macro
> 
> (nnoo-define-basics nnfolder)
> 
> in nnfolder.el.
> 
> I can work around this by manually requiring nnfolder in init.el.  Alas,
> I don't know much about Gnus internals to determine what the right fix
> would be.

Andrew and Eric, can you please help Gerd with this issue?

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Eric Abrahamsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Date: Tue, 22 Aug 2023 09:29:39 +0200
>> 
>> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>> 
>> > I get the following error when starting Gnus with M-x gnus.
>> >
>> >   No such function: nnfolder-server-opened
>> >
>> > The function nnfolder-server-opened is indeed defined nowhere I can
>> > find.  In case it matters, I had a Gnus autosave file.  After M-x gnus,
>> > I answered 'n' to the question if the autosave file should be used.
>> > After that, the error is signaled.

This is almost certainly the source of the problem. Your .newsrc.eld
file should have entries for groups looking like:

("nnfolder+archive:sent.2022-02" 3 ((1 . 1)) ((unexist) (seen 1))
 (nnfolder
  "archive" (nnfolder-directory "~/.mail/archive")
  (nnfolder-active-file "~/.mail/archive/active")
  (nnfolder-get-new-mail nil)
  (nnfolder-inhibit-expiry t)))

Long story short, at Gnus startup time the `nnfolder' symbol at the head
of the method list will get turned into a `require' call for the
appropriate library, so the nnfolder functions should be available early
on.

I'm not sure exactly how you got there, but it sounds like there are
references to your nnfolder group(s) somewhere in Gnus, but the groups
are not listed in your .newsrc.eld, so the library is never loaded.

What nnfolder groups show up in your Group buffer (hitting "L" first).
Are those groups present in your .newsrc.eld file?

Eric

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Gerd Möllmann]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>>> Date: Tue, 22 Aug 2023 09:29:39 +0200
>>> 
>>> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>>> 
>>> > I get the following error when starting Gnus with M-x gnus.
>>> >
>>> >   No such function: nnfolder-server-opened
>>> >
>>> > The function nnfolder-server-opened is indeed defined nowhere I can
>>> > find.  In case it matters, I had a Gnus autosave file.  After M-x gnus,
>>> > I answered 'n' to the question if the autosave file should be used.
>>> > After that, the error is signaled.
>
> This is almost certainly the source of the problem. Your .newsrc.eld
> file should have entries for groups looking like:
>
> ("nnfolder+archive:sent.2022-02" 3 ((1 . 1)) ((unexist) (seen 1))
>  (nnfolder
>   "archive" (nnfolder-directory "~/.mail/archive")
>   (nnfolder-active-file "~/.mail/archive/active")
>   (nnfolder-get-new-mail nil)
>   (nnfolder-inhibit-expiry t)))
>
> Long story short, at Gnus startup time the `nnfolder' symbol at the head
> of the method list will get turned into a `require' call for the
> appropriate library, so the nnfolder functions should be available early
> on.

My .newsrc.eld contains, among other stuff

(setq gnus-server-alist
      '(("archive" nnfolder "archive"
	 (nnfolder-directory "~/Mail/archive")
	 (nnfolder-active-file "~/Mail/archive/active")
	 (nnfolder-get-new-mail nil)
	 (nnfolder-inhibit-expiry t))))

(setq gnus-topic-topology '(("Gnus" visible) (("misc" visible))))

(setq gnus-topic-alist
      '(("misc"
	 "INBOX"
	 "Emacs"
	 "[Google Mail]/Entw\303\274rfe"
	 "[Google Mail]/Markiert"
	 "nndraft:drafts"
	 "[Google Mail]/Alle Nachrichten"
	 "[Google Mail]/Gesendet"
	 "[Google Mail]/Papierkorb"
	 "[Google Mail]/Spam"
	 "[Google Mail]/Wichtig"
	 "Notes" "[Gmail]/Drafts"
	 "Emacs/Emacs"
	 "nnfolder+archive:sent.2022-06")
	("Gnus")))

Above these, there's also a (setq gnus-newsrc-alist '(...)) with a large
list containomg references to nnfolder, e.g. (nnfolder-inhibit-expiry
t), but since that list is quoted...

> I'm not sure exactly how you got there, but it sounds like there are
> references to your nnfolder group(s) somewhere in Gnus, but the groups
> are not listed in your .newsrc.eld, so the library is never loaded.
>
> What nnfolder groups show up in your Group buffer (hitting "L" first).
> Are those groups present in your .newsrc.eld file?

and the summary shows

       0: Emacs
       0: Emacs/Emacs
       0: INBOX
       0: Notes
       0: [Gmail]/Drafts
*      0: [Google Mail]/Alle Nachrichten
       0: [Google Mail]/Entwürfe
*      0: [Google Mail]/Gesendet
*      0: [Google Mail]/Markiert
*U     0: [Google Mail]/Papierkorb
 U    72: [Google Mail]/Spam
       5: [Google Mail]/Wichtig
      13: nndraft:drafts
       2: nnfolder+archive:sent.2022-06
      24: nnfolder+archive:sent.2022-07
      31: nnfolder+archive:sent.2022-08
      71: nnfolder+archive:sent.2022-09
      57: nnfolder+archive:sent.2022-10
      15: nnfolder+archive:sent.2022-11
       7: nnfolder+archive:sent.2023-08

Which I think is what gnus-topic-alist has, except for the archives.

Here is what my .gnus looks like.  I think I copied it from
somewhere on the Internet.

(setq mml-secure-openpgp-signers '("xxx")
      ;; We want to be able to read the emails we wrote.
      mml-secure-openpgp-encrypt-to-self t)

(setq gnus-select-method
      '(nnimap "gmail"
	       (nnimap-address "imap.gmail.com")
	       (nnimap-server-port "imaps")
	       (nnimap-stream ssl)))

(setq smtpmail-smtp-server "smtp.gmail.com"
      smtpmail-smtp-service 587)

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Eric Abrahamsen]

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>>>> Date: Tue, 22 Aug 2023 09:29:39 +0200
>>>> 
>>>> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>>>> 
>>>> > I get the following error when starting Gnus with M-x gnus.
>>>> >
>>>> >   No such function: nnfolder-server-opened
>>>> >
>>>> > The function nnfolder-server-opened is indeed defined nowhere I can
>>>> > find.  In case it matters, I had a Gnus autosave file.  After M-x gnus,
>>>> > I answered 'n' to the question if the autosave file should be used.
>>>> > After that, the error is signaled.
>>
>> This is almost certainly the source of the problem. Your .newsrc.eld
>> file should have entries for groups looking like:
>>
>> ("nnfolder+archive:sent.2022-02" 3 ((1 . 1)) ((unexist) (seen 1))
>>  (nnfolder
>>   "archive" (nnfolder-directory "~/.mail/archive")
>>   (nnfolder-active-file "~/.mail/archive/active")
>>   (nnfolder-get-new-mail nil)
>>   (nnfolder-inhibit-expiry t)))
>>
>> Long story short, at Gnus startup time the `nnfolder' symbol at the head
>> of the method list will get turned into a `require' call for the
>> appropriate library, so the nnfolder functions should be available early
>> on.
>
> My .newsrc.eld contains, among other stuff
>
> (setq gnus-server-alist
>       '(("archive" nnfolder "archive"
> 	 (nnfolder-directory "~/Mail/archive")
> 	 (nnfolder-active-file "~/Mail/archive/active")
> 	 (nnfolder-get-new-mail nil)
> 	 (nnfolder-inhibit-expiry t))))
>
> (setq gnus-topic-topology '(("Gnus" visible) (("misc" visible))))
>
> (setq gnus-topic-alist
>       '(("misc"
> 	 "INBOX"
> 	 "Emacs"
> 	 "[Google Mail]/Entw\303\274rfe"
> 	 "[Google Mail]/Markiert"
> 	 "nndraft:drafts"
> 	 "[Google Mail]/Alle Nachrichten"
> 	 "[Google Mail]/Gesendet"
> 	 "[Google Mail]/Papierkorb"
> 	 "[Google Mail]/Spam"
> 	 "[Google Mail]/Wichtig"
> 	 "Notes" "[Gmail]/Drafts"
> 	 "Emacs/Emacs"
> 	 "nnfolder+archive:sent.2022-06")
> 	("Gnus")))
>
> Above these, there's also a (setq gnus-newsrc-alist '(...)) with a large
> list containomg references to nnfolder, e.g. (nnfolder-inhibit-expiry
> t), but since that list is quoted...

Yes, it's `gnus-newsrc-alist' that will contain group definitions,
including seven (it looks like) for your archive groups, each one with
an identical method definition looking like:

(nnfolder "archive"
	  (nnfolder-directory "~/Mail/archive")
	  (nnfolder-active-file "~/Mail/archive/active")
	  (nnfolder-get-new-mail nil)
	  (nnfolder-inhibit-expiry t))

I know the file is a bit eye-watering to look at, but try to confirm
that you have seven archive groups in there, and each one ends with the
form above.

It's pretty weird that you're seeing this with your archive server,
because that one gets special treatment. Take a close look at the file
first, and maybe we can try something else.

Eric

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Gerd Möllmann]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Yes, it's `gnus-newsrc-alist' that will contain group definitions,

Ah, ok.  Sorry, I didn't know that.

> including seven (it looks like) for your archive groups, each one with
> an identical method definition looking like:
>
> (nnfolder "archive"
> 	  (nnfolder-directory "~/Mail/archive")
> 	  (nnfolder-active-file "~/Mail/archive/active")
> 	  (nnfolder-get-new-mail nil)
> 	  (nnfolder-inhibit-expiry t))
>
> I know the file is a bit eye-watering to look at, but try to confirm
> that you have seven archive groups in there, and each one ends with the
> form above.

No problem.  When I 'pp' the list, I see these 7:

 (\"nnfolder+archive:sent.2022-06\" 3 nil ((unexist) (seen (1 . 2)))
  (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
	    (nnfolder-active-file \"~/Mail/archive/active\")
	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t)))
 (\"nnfolder+archive:sent.2022-07\" 3 nil nil
  (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
	    (nnfolder-active-file \"~/Mail/archive/active\")
	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
  nil)
 (\"nnfolder+archive:sent.2022-08\" 3 nil nil
  (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
	    (nnfolder-active-file \"~/Mail/archive/active\")
	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
  nil)
 (\"nnfolder+archive:sent.2022-09\" 3 nil nil
  (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
	    (nnfolder-active-file \"~/Mail/archive/active\")
	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
  nil)
 (\"nnfolder+archive:sent.2022-10\" 3 nil nil
  (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
	    (nnfolder-active-file \"~/Mail/archive/active\")
	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
  nil)
 (\"nnfolder+archive:sent.2022-11\" 3 nil nil
  (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
	    (nnfolder-active-file \"~/Mail/archive/active\")
	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
  nil)
 (\"nnfolder+archive:sent.2023-08\" 3 nil nil
  (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
	    (nnfolder-active-file \"~/Mail/archive/active\")
	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
  nil))

> It's pretty weird that you're seeing this with your archive server,

I am weird :-).

> because that one gets special treatment. Take a close look at the file
> first, and maybe we can try something else.

I can also try to catch that in the debugger, if it helps.  Since
setting debug-on-error seems not to help, can I perhaps set a breakpoint
somewhere in Gnus?

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Eric Abrahamsen]

On 08/23/23 07:18 AM, Gerd Möllmann wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Yes, it's `gnus-newsrc-alist' that will contain group definitions,
>
> Ah, ok.  Sorry, I didn't know that.

No problem :)

>> including seven (it looks like) for your archive groups, each one with
>> an identical method definition looking like:
>>
>> (nnfolder "archive"
>> 	  (nnfolder-directory "~/Mail/archive")
>> 	  (nnfolder-active-file "~/Mail/archive/active")
>> 	  (nnfolder-get-new-mail nil)
>> 	  (nnfolder-inhibit-expiry t))
>>
>> I know the file is a bit eye-watering to look at, but try to confirm
>> that you have seven archive groups in there, and each one ends with the
>> form above.
>
> No problem.  When I 'pp' the list, I see these 7:
>
>  (\"nnfolder+archive:sent.2022-06\" 3 nil ((unexist) (seen (1 . 2)))
>   (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
> 	    (nnfolder-active-file \"~/Mail/archive/active\")
> 	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t)))
>  (\"nnfolder+archive:sent.2022-07\" 3 nil nil
>   (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
> 	    (nnfolder-active-file \"~/Mail/archive/active\")
> 	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
>   nil)
>  (\"nnfolder+archive:sent.2022-08\" 3 nil nil
>   (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
> 	    (nnfolder-active-file \"~/Mail/archive/active\")
> 	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
>   nil)
>  (\"nnfolder+archive:sent.2022-09\" 3 nil nil
>   (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
> 	    (nnfolder-active-file \"~/Mail/archive/active\")
> 	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
>   nil)
>  (\"nnfolder+archive:sent.2022-10\" 3 nil nil
>   (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
> 	    (nnfolder-active-file \"~/Mail/archive/active\")
> 	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
>   nil)
>  (\"nnfolder+archive:sent.2022-11\" 3 nil nil
>   (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
> 	    (nnfolder-active-file \"~/Mail/archive/active\")
> 	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
>   nil)
>  (\"nnfolder+archive:sent.2023-08\" 3 nil nil
>   (nnfolder \"archive\" (nnfolder-directory \"~/Mail/archive\")
> 	    (nnfolder-active-file \"~/Mail/archive/active\")
> 	    (nnfolder-get-new-mail nil) (nnfolder-inhibit-expiry t))
>   nil))
>
>> It's pretty weird that you're seeing this with your archive server,
>
> I am weird :-).
>
>> because that one gets special treatment. Take a close look at the file
>> first, and maybe we can try something else.
>
> I can also try to catch that in the debugger, if it helps.  Since
> setting debug-on-error seems not to help, can I perhaps set a breakpoint
> somewhere in Gnus?

The error has to be coming out of `gnus-get-function', in gnus-int.el.
Right above the spot where the error is signaled, we have a:

(require (car method))

In your case, (car method) is supposed to be the symbol 'nnfolder. I
can't imagine how the function name has been constructed as
`nnfolder-server-opened', yet (car method) is something other than
`nnfolder'. So the place to set a breakpoint would be at the bottom of
`gnus-get-function', maybe you can put it behind a check for
(eq func 'nnfolder-server-opened).

Then we would want to know what the value of `method' is here, and also
where in the startup sequence we are.

Thanks!
Eric

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Gerd Möllmann]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> The error has to be coming out of `gnus-get-function', in gnus-int.el.
> Right above the spot where the error is signaled, we have a:
>
> (require (car method))
>
> In your case, (car method) is supposed to be the symbol 'nnfolder. I
> can't imagine how the function name has been constructed as
> `nnfolder-server-opened', yet (car method) is something other than
> `nnfolder'. So the place to set a breakpoint would be at the bottom of
> `gnus-get-function', maybe you can put it behind a check for
> (eq func 'nnfolder-server-opened).
>
> Then we would want to know what the value of `method' is here, and also
> where in the startup sequence we are.

I have kind of bad news:

My reproducer recipe does not work anymore, today.  What I formerly
did was start Gnus in one session until an #.newsrc.dribble# appeared.
Then I started another Emacs session, and also started Gnus, got the
autosave file warning, replied with 'n', and the error was signaled.

Worked yesterday, no longer does.

Any idea?

bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened

[Gerd Möllmann]

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> The error has to be coming out of `gnus-get-function', in gnus-int.el.
>> Right above the spot where the error is signaled, we have a:
>>
>> (require (car method))
>>
>> In your case, (car method) is supposed to be the symbol 'nnfolder. I
>> can't imagine how the function name has been constructed as
>> `nnfolder-server-opened', yet (car method) is something other than
>> `nnfolder'. So the place to set a breakpoint would be at the bottom of
>> `gnus-get-function', maybe you can put it behind a check for
>> (eq func 'nnfolder-server-opened).
>>
>> Then we would want to know what the value of `method' is here, and also
>> where in the startup sequence we are.
>
> I have kind of bad news:
>
> My reproducer recipe does not work anymore, today.  What I formerly
> did was start Gnus in one session until an #.newsrc.dribble# appeared.
> Then I started another Emacs session, and also started Gnus, got the
> autosave file warning, replied with 'n', and the error was signaled.
>
> Worked yesterday, no longer does.
>
> Any idea?

I think I should close this because I'm unable to reproduce the problem.

Maybe it's a MacOS problem.  I've seen a number of such spurious
problems in the last months on macOS, like freezes in some macOS code,
buffers containing text that's not in the file they visit, font sizes
changing spuriously while writing text, input being reversed while
typing...  Or it's me, I don'T know. 

So, I'm closing this.  Thanks for helping me!