From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: ding@gnus.org
Subject: Re: latest imap changes break refiling
Date: Thu, 05 Mar 2015 13:29:40 +0100 [thread overview]
Message-ID: <m2mw3r630r.fsf@polytechnique.org> (raw)
In-Reply-To: <m2d25ew3x0.fsf@charm-ecran.irisa.fr>
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
On 2015-02-13 10:34, Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> On 2015-02-13 17:23, Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>>
>>> I'm sorry, there is still a bug:
>>>
>>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>>> string-match("^[^:]+:" nil)
>>> nnimap-retrieve-group-data-early("local" (nil))
>>
>> This should be fixed in git Gnus now.
>
> Unfortunately it still breaks here. Here is what I see:
I've dug a little in this, here are my findings. It seems the problems
only occur in the following setting:
- the target group is in a different server
- the target group is empty.
I'm able to reproduce this without the expiring process: if I move
a message (using "B m") to a group satisfying these conditions I get the
same error.
The problem happens in the last line of that snippet
#+begin_src emacs-lisp
(deffoo nnimap-request-group (group &optional server dont-check info)
(setq group (nnimap-decode-gnus-group group))
(let ((result (nnimap-change-group
;; Don't SELECT the group if we're going to select it
;; later, anyway.
(if (and (not dont-check)
(assoc group nnimap-current-infos))
nil
group)
server))
articles active marks high low)
(with-current-buffer nntp-server-buffer
(when result
(when (or (not dont-check)
(not (setq active
(nth 2 (assoc group nnimap-current-infos)))))
(let ((sequences (nnimap-retrieve-group-data-early
server (list info))))
#+end_src
It happens if the function is called with info being nil, then
`nnimap-retrieve-group-data-early' is called with `(nil)' as second
argument (the singleton list containing the empty list).
Since `(nil)' is not nil, the guard of the `when' in the following
snippet does not prevent the code from being run
#+begin_src emacs-lisp
(deffoo nnimap-retrieve-group-data-early (server infos)
(when (and (nnimap-change-group nil server)
infos)
#+end_src
and the rest of the code breaks (when a `dolist' is done on the list
`(nil)').
Unfortunately I don't know what should be done in `nnimap-request-group'
if `info' is nil, so I cannot propose a patch.
I'll gladly take any suggestion as how to fix this.
Thanks,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2015-03-05 12:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 8:02 Alan Schmitt
2015-01-29 8:04 ` Alan Schmitt
2015-01-29 8:06 ` Lars Ingebrigtsen
2015-01-29 8:51 ` Alan Schmitt
2015-01-29 10:18 ` Alan Schmitt
2015-01-29 11:08 ` Lars Ingebrigtsen
2015-01-29 12:03 ` Alan Schmitt
2015-02-05 2:29 ` Lars Ingebrigtsen
2015-02-05 9:26 ` Alan Schmitt
2015-02-13 6:23 ` Lars Ingebrigtsen
2015-02-13 9:34 ` Alan Schmitt
2015-02-21 9:40 ` Alan Schmitt
2015-03-03 13:17 ` Alan Schmitt
2015-03-05 12:29 ` Alan Schmitt [this message]
2015-01-29 10:19 ` Alan Schmitt
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=m2mw3r630r.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.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).