From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 65447@debbugs.gnu.org
Subject: bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened
Date: Wed, 23 Aug 2023 10:01:49 -0700 [thread overview]
Message-ID: <87h6ophev6.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2lee2z69b.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Wed, 23 Aug 2023 07:18:08 +0200")
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
next prev parent reply other threads:[~2023-08-23 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 5:18 bug#65447: 30.0.50; Gnus: No such function: nnfolder-server-opened Gerd Möllmann
2023-08-22 7:29 ` Gerd Möllmann
2023-08-22 11:20 ` Eli Zaretskii
2023-08-22 16:25 ` Eric Abrahamsen
2023-08-22 17:13 ` Gerd Möllmann
2023-08-23 4:18 ` Eric Abrahamsen
2023-08-23 5:18 ` Gerd Möllmann
2023-08-23 17:01 ` Eric Abrahamsen [this message]
2023-08-24 8:56 ` Gerd Möllmann
2023-08-27 7:16 ` Gerd Möllmann
2023-08-22 7:37 ` Andreas Schwab
2023-08-22 7:54 ` Gerd Möllmann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6ophev6.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=65447@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).