From: Eric Schulte <schulte.eric@gmail.com>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: ding@lists.math.uh.edu
Subject: Re: GNUS ticks and Gmail flags or stars
Date: Fri, 29 Jul 2022 12:32:41 -0400 [thread overview]
Message-ID: <m235ejnal2.fsf@Mac-mini.fios-router.home> (raw)
In-Reply-To: <87bkt7j3co.fsf@undisclosedlocation.com> (Bob Newell's message of "Fri, 29 Jul 2022 06:22:31 -1000")
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Bob Newell <bobnewell@bobnewell.net> writes:
> Eric Schulte <schulte.eric@gmail.com> writes:
>>
>> When I 'tick' an article (in gnus terms) with `!' the resulting article
>> does not get a flag or a star in the gmail interface (or subsequently in
>> my other mail readers).
>
> I just tried this and it works as expected for me, with the
> understanding that the marks don't necessarily propagate until
> you actually exit gnus or exit the group in question (at least
> in my setup).
I just ticked your message, and saw it appear starred in Gmail and
flagged in my other mail app. After briefly wondering what was wrong
with me, I realized that ticks appear to be propagating for "new"
messages (where new means roughly initially received after I started
using GNUS) but somehow don't propagate for older messages. I think
this is a fine state of affairs, so I'm all set.
Thanks for helping me realize my problem maybe isn't really a problem!
--
Eric Schulte (he/him)
https://eschulte.github.io
PGP Fingerprint: FA8D C2C3 E8A0 A749 34CD 9DCF 3C1B 8581 614C A05D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]
next prev parent reply other threads:[~2022-07-29 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 15:59 Eric Schulte
2022-07-29 16:22 ` Bob Newell
2022-07-29 16:32 ` Eric Schulte [this message]
2022-07-30 3:43 ` Pankaj Jangid
2022-07-29 18:10 ` Tom Boyce
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=m235ejnal2.fsf@Mac-mini.fios-router.home \
--to=schulte.eric@gmail.com \
--cc=bobnewell@bobnewell.net \
--cc=ding@lists.math.uh.edu \
/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).