all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joel Reicher <joel.reicher@gmail.com>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: Christopher Howard <christopher@librehacker.com>,
	 Robert Pluim <rpluim@gmail.com>,
	 Help Gnu Emacs Mailing List <help-gnu-emacs@gnu.org>
Subject: Re: Gnus: Permanently killing a thread?
Date: Sat, 14 Dec 2024 23:08:23 +1100	[thread overview]
Message-ID: <86ldwilb60.fsf@gmail.com> (raw)
In-Reply-To: <675cbe7a.170a0220.2de1ab.4598SMTPIN_ADDED_BROKEN@mx.google.com> ("Björn Bidar"'s message of "Sat, 14 Dec 2024 01:08:40 +0200")

Björn Bidar <bjorn.bidar@thaodan.de> writes:

> Joel Reicher <joel.reicher@gmail.com> writes:
>
>> IMAP is a bit of a special case; where possible (always, 
>> perhaps?)  Gnus will use IMAP flags stored on the server for 
>> representing things like readedness marks, ticks, etc.
>
> It could do that but doesn't at the moment. Nnimap Gnus IMAP 
> backend can already query capabilities. If it implements rfc5464 
> IMAP METADATA it could be possible to store these inside the 
> metadata of severs which support the extension.

OK, so just seen, flagged, and answered? (That's what I can see in 
nnimap-mark-alist; should have looked earlier)

Regards,

        - Joel



  parent reply	other threads:[~2024-12-14 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 16:52 Gnus: Permanently killing a thread? Christopher Howard
2024-12-11 17:58 ` Robert Pluim
2024-12-11 20:25   ` Christopher Howard
2024-12-11 20:42     ` Greg Farough
2024-12-12 10:08     ` Joel Reicher
2024-12-12 16:12       ` Christopher Howard
2024-12-12 21:12         ` Joel Reicher
2024-12-13 23:08       ` Björn Bidar
     [not found]       ` <675cbe7a.170a0220.2de1ab.4598SMTPIN_ADDED_BROKEN@mx.google.com>
2024-12-14 12:08         ` Joel Reicher [this message]
2024-12-11 18:17 ` Manuel Giraud via Users list for the GNU Emacs text editor

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=86ldwilb60.fsf@gmail.com \
    --to=joel.reicher@gmail.com \
    --cc=bjorn.bidar@thaodan.de \
    --cc=christopher@librehacker.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rpluim@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 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.