Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Cc: 20672@debbugs.gnu.org, Nikolaus Rath <Nikolaus@rath.org>
Subject: Re: bug#20672: [PATCH] Support hiding deleted IMAP messages (v2)
Date: Thu, 26 Jan 2017 20:15:11 +0100	[thread overview]
Message-ID: <87poj9r5ts.fsf@gnus.org> (raw)
In-Reply-To: <873817cmk6.fsf@vostro.rath.org> (Nikolaus Rath's message of "Wed, 01 Jul 2015 19:36:57 -0700")

Nikolaus Rath <Nikolaus@rath.org> writes:

> The previous patch did not take into account that an IMAP server is free
> to send the UID, FLAGS and RFC822.SIZE response data items in arbitrary
> order. This has been fixed in this version of the patch.

[...]

> +        (if (and nnimap-hide-deleted
> +                 (member "\\Deleted" flags))
> +            (delete-region (line-beginning-position)
> +                           (or (re-search-forward "^\r$\\|^)\r?$" nil t)
> +                               (point-max)))

Hm...  won't this make Gnus think that the articles doesn't exist?  So
they'll end up in the "unexist tracking" list?  I don't think that's
correct...

I think it would be better to just convey the information up to the Gnus
layer, and then Gnus could have a switch to not display these deleted
messages.

Or perhaps just pretend like all \Deleted messages are \Read?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  parent reply	other threads:[~2017-01-26 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  4:29 [PATCH] Support hiding deleted IMAP messages Nikolaus Rath
2015-05-28 13:42 ` Eric Abrahamsen
2015-07-02  2:36 ` [PATCH] Support hiding deleted IMAP messages (v2) Nikolaus Rath
2015-07-02 17:14   ` Andreas Schwab
2017-01-26 19:15   ` Lars Ingebrigtsen [this message]
2020-08-13  8:47     ` bug#20672: " Lars Ingebrigtsen

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=87poj9r5ts.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=20672@debbugs.gnu.org \
    --cc=Nikolaus@rath.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).