From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Fixed bug with custom marks in registry
Date: Wed, 07 Nov 2018 00:33:42 +0100 [thread overview]
Message-ID: <87o9b1ixwp.fsf@web.de> (raw)
In-Reply-To: <87sh0ewxqs.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 05 Nov 2018 22:01:15 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> TBH I hadn't even looked into this part of the code before you brought
> it up last time, so I'm not really ahead of you in this game. I think in
> principle it would be nice to have a higher-level, more user-friendly
> way of adjusting this behavior. I could certainly imagine using an
> option that let me say "always display any message that has registry
> keys marked "precious"".
Yeah, something like that would be nice.
> I tried this with a basic setup, and didn't see a problem -- the message
> lines were not duplicated as I added/removed marks. Do you have multiple
> functions added to `gnus-alter-articles-to-read-function' that might be
> interacting with each other?
No, only this one.
> I actually tried this with gnus-mock [...]
> [...]
> That should get you as close to "gnus -Q" as you can get, and might
> provide a starting place for tracking down the weird behavior.
That worked nice. I couldn't reproduce there. Furthermore, I can't now
reproduce with my own setup as well. Dunno why - maybe all Gnus wanted
was a restart.
Thanks for your help.
Michael.
next prev parent reply other threads:[~2018-11-06 23:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 18:26 Eric Abrahamsen
2018-10-11 18:44 ` Emanuel Berg
2018-10-11 21:00 ` Ted Zlatanov
2018-11-06 0:54 ` Michael Heerdegen
2018-11-06 4:56 ` Michael Heerdegen
2018-11-06 6:01 ` Eric Abrahamsen
2018-11-06 23:33 ` Michael Heerdegen [this message]
2018-11-07 5:00 ` Eric Abrahamsen
2018-11-17 0:32 ` Eric Abrahamsen
2018-11-17 15:01 ` Michael Heerdegen
2018-11-19 23:51 ` Eric Abrahamsen
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=87o9b1ixwp.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).