Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Fixed bug with custom marks in registry
Date: Thu, 11 Oct 2018 11:26:00 -0700	[thread overview]
Message-ID: <87efcw1gsn.fsf@ericabrahamsen.net> (raw)

Obviously not too many people were using this feature, or else we would
have heard about it sooner, but there was a bug in the Gnus registry
where entries with custom marks attached to them could still be pruned
(deleted), even though they're not supposed to be.

That's fixed now, and the fix will go into Emacs 26.2 and 27, so if
you'd run into this before and decided not to use custom marks in the
registry, watch for updates.

Eric




             reply	other threads:[~2018-10-11 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 18:26 Eric Abrahamsen [this message]
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
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=87efcw1gsn.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).