all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Sean Connor <sconnor@allyinics.org>
Cc: 43129@debbugs.gnu.org, 43129-done@debbugs.gnu.org
Subject: bug#43129: 25.2; Typo in lisp/gnus/nnimap.el
Date: Wed, 02 Sep 2020 09:09:40 -0700	[thread overview]
Message-ID: <87h7sg9n3v.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87zh6bgsu1.fsf@allyinics.org>


On 09/02/20 01:38 AM, Sean Connor wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> And my dovecot test was done in a clean environment where, by default,
>> Gnus doesn't let dovecot use MOVE, so in effect I was only testing
>> COPY as well. Looks like cautious is the way to go!
>
> Yes.
>
> [...]
>
>> Thanks, this is helpful. I feel like the "outer edges" of execution is
>> the wrong place to be checking this stuff -- if the response parsing
>> process handled the differences, this would never have been an issue in
>> the first place. And ugh, this can-move thing is all over the place, and
>> begging to be refactored...
>
> I don't know.
>
>> But! We will not be drawn down that rabbit hole. It seems to me that
>> changing the code to read:
>>
>
> [code]
>
> Nice.  That's much clearer.
>
> [...]
>
>>> I tested with courier, dovecot, RFC sample sessions and gmail IMAP
>>> transcripts, FWIW.
>>
>> That's good to know! That gives us some confidence.
>
> Yep.
>
> Thank you.

In it goes! Thanks for the report.

Eric





      parent reply	other threads:[~2020-09-02 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31  7:47 bug#43129: 25.2; Typo in lisp/gnus/nnimap.el Sean Connor
2020-08-31 16:47 ` Eric Abrahamsen
2020-09-01 14:40   ` Sean Connor
2020-09-01 22:43     ` Eric Abrahamsen
     [not found]       ` <87ft80hh5x.fsf@allyinics.org>
2020-09-02 16:09         ` Eric Abrahamsen [this message]

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=87h7sg9n3v.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=43129-done@debbugs.gnu.org \
    --cc=43129@debbugs.gnu.org \
    --cc=sconnor@allyinics.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.