From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: [PATCH 0/2] two minor fixes for new/empty nnimap group handling
Date: Mon, 13 Jul 2015 13:36:57 +0800 [thread overview]
Message-ID: <87a8v0ipom.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87io9pz4xc.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> Dan Christensen <jdc@uwo.ca> writes:
>>>
>>>> Could nnmairix be adjusted to make an extra call at some point to
>>>> activate the appropriate group? Maybe it needs to call
>>>> nnimap-request-group-scan instead of nnimap-request-group, now that
>>>> 447c5 changed the behaviour of the latter?
>>>
>>> I think this is probably the right solution. I'm still convinced that
>>> nnimap should do something in the group creation process to register the
>>> group with Gnus, but you're right that your problem is likely a direct
>>> result of "request-group" getting split into "request-group" and
>>> "request-group-scan", and nnmairix not being edited to follow.
>>>
>>> I'm a little bit out of my depth here, but give this patch a whirl and
>>> see how it goes.
>>
>> Dammit, I think that was wrong. Would you try it anyway, then unapply it
>> and try this one instead?
>
> I tried the first, the second, and both, and didn't notice any change.
> (I still had your nnimap.el patches applied as
> Here is the backtrace with the patch nnmairix-scan-imap-groups.patch
> applied.
Bah! Thanks for testing. I'm going to stop throwing patches at you until
I can get my own nnmairix installation working, and test things there.
This is a silly way of doing it.
More later...
eric
next prev parent reply other threads:[~2015-07-13 5:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 11:37 Bjørn Mork
2015-07-01 11:37 ` [PATCH 1/2] nnimap.el (nnimap-request-group): don't make nil into a list Bjørn Mork
2015-07-01 11:37 ` [PATCH 2/2] nnimap.el (nnimap-request-group): group could be empty Bjørn Mork
2015-07-01 11:50 ` [PATCH 0/2] two minor fixes for new/empty nnimap group handling Alan Schmitt
2015-07-01 12:23 ` Bjørn Mork
2015-07-01 13:49 ` Alan Schmitt
2015-07-02 2:18 ` Nikolaus Rath
2015-07-06 2:45 ` Eric Abrahamsen
2015-07-06 8:40 ` Bjørn Mork
2015-07-06 15:11 ` Eric Abrahamsen
2015-07-06 15:32 ` Dan Christensen
2015-07-07 2:48 ` Eric Abrahamsen
2015-07-07 23:12 ` Dan Christensen
2015-07-08 4:20 ` Eric Abrahamsen
2015-07-08 21:45 ` Dan Christensen
2015-07-09 1:53 ` Eric Abrahamsen
2015-07-09 2:52 ` Dan Christensen
2015-07-09 13:47 ` Dan Christensen
2015-07-10 2:41 ` Eric Abrahamsen
2015-07-10 12:42 ` Dan Christensen
2015-07-12 4:11 ` Eric Abrahamsen
2015-07-12 4:27 ` Eric Abrahamsen
2015-07-12 17:01 ` Dan Christensen
2015-07-13 5:36 ` Eric Abrahamsen [this message]
2015-07-08 12:41 ` 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=87a8v0ipom.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).