Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: James Thomas <jimjoe@gmx.net>
To: Thomas Ieong <th.ieong@free.fr>
Cc: info-gnus-english@gnu.org
Subject: Re: Custom tags/keywords/labels
Date: Sat, 17 Sep 2022 11:50:46 +0530	[thread overview]
Message-ID: <87h716r075.fsf@gmx.net> (raw)
In-Reply-To: <878rmnfv9q.fsf@free.fr> (Thomas Ieong's message of "Tue, 13 Sep 2022 11:56:40 +0200")

Thomas Ieong wrote:

> Also I saw that there was gnus-registry-marks-* and while it does allow
> to store important/todo/custom tags... locally it does not seems to push
> them to the remote server(imap) and as a result my webmail and
> Thunderbird can't see the tags.

You'll have to write custom code because nnimap-request-set-mark (see
also nnchoke-request-set-mark in the manual) currently uses a hardcoded
list of marks. And if you want to hitch it to the normal update (rather
than a custom asynchronous command) you'll probably have to modify
gnus-update-marks.

--


      reply	other threads:[~2022-09-17  6:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  9:56 Thomas Ieong
2022-09-17  6:20 ` James Thomas [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=87h716r075.fsf@gmx.net \
    --to=jimjoe@gmx.net \
    --cc=info-gnus-english@gnu.org \
    --cc=th.ieong@free.fr \
    /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).