Gnus development mailing list
 help / color / mirror / Atom feed
From: "St. Suika Fenderson Roberts" <wrobert2@mailhost.tcs.tulane.edu>
Subject: Re:  discussion: marking old articles
Date: Fri, 13 Dec 1996 12:18:39 -0600	[thread overview]
Message-ID: <199612131818.MAA27199@rs1.tcs.tulane.edu> (raw)

>Lars wanted me to post the thought here and see what other people
>thought about it.  After having noticed this problem, I'm still
>tempted just to leave it unless someone else feels strongly, as it is
>nice to have them visibly marked as read when browsing old messages...

Being able to just reset marks to random other marks would be a really nifty
thing.  Esp. if it followed process marks, num. arguments, etc.

Thus one could look at a bunch of old articles, process mark them, hit the
gnus-summary-change-mark keysequence, enter the mark one wants them to have,
and poof!  the lot of them go from being marked with `R' to `O' or `E' or
whatever ^_^

This would be useful, I would think.  But then I would also really like it if
`gnus-summary-mark-as-expirable' followed the process mark ^_^

Thanks,
	Suika
--
                wrobert2@mailhost.tcs.tulane.edu
Go??+ TB B15DBr(R)^1.5 c9(5)c++++ P6 M+ a- n+++ b+: H161 g- mA8+ w+ 
r++(Discordia) D- k+++ R? Ssw LusLA(NM)++ 


             reply	other threads:[~1996-12-13 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-12-13 18:18 St. Suika Fenderson Roberts [this message]
1996-12-16 13:00 ` Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
1996-12-13  7:43 Wesley.Hardaker
1996-12-13  8:20 ` Per Abrahamsen
1996-12-13 10:37   ` Graham Murray

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=199612131818.MAA27199@rs1.tcs.tulane.edu \
    --to=wrobert2@mailhost.tcs.tulane.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).