🚀 go-pugleaf

This is just a quick note to find out how other people feel about
this; I can see a disagreement is possible here about how the commands
in question should behave.
 
Basically, my situation is this: when I mark an article with
gnus-Subject-mark-as-unread-forward (typically key "u"), I want that
mark to stay until I explicity clear it.  This is not the case in two
situations, however. If I apply my kill file to a group or use
gnus-Subject-catch-up[-and-exit], the mark can be cleared.  Some
people will probably say that it is their proper function to do so; it
is not, however, the behaviour which I desire.  In case the kill file
one is a little confusing, here is a quick sample for news.groups.KILL:

(gnus-kill "Subject" "[Rr]e\:")    ;; regexp is case-sensitive (can we
                                   ;; make it not so?)
(gnus-kill "Subject" "gnu" '(gnus-Subject-mark-as-unread nil t))

gnus-Subject-mark-as-unread is providing its advertised function:
clearing any sort of mark.  This is exactly what I want it to do for
articles I have not seen yet; it is not what I want it to do for
articles I have previously marked as unread.
 
The fixes that I can see simply involve adding a step in catch-up and
gnus-kill that skip already marked articles.  If people think that the
behaviour is as it should be already, perhaps the step could only be
executed if an &optional arg was non-nil.

I'll be expecting a from letter from Japan on this in about two days,
Masanobu.  (Can we ask about your gateway yet? |:-)

Dave
--
      tale@rpitsmts.bitnet, tale%mts@rpitsgw.rpi.edu, tale@pawl.rpi.edu