Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: Question about article identification and backends.
Date: Mon, 19 May 2003 12:57:26 -0400	[thread overview]
Message-ID: <m365o6g9gz.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <871xywayng.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Sun, 18 May 2003 13:38:11 -0500")

Rob Browning <rlb@defaultvalue.org> wrote:
> Actually, I might just prefer to have gnus-summary-move-marking-as
> and gnus-summary-copy-marking-as.  With each you would invoke the
> function, it would expect a keypress to indicate the mark (?, u, U,
> d, etc.) and then it would process the article(s).  You could
> possibly also have a gnus-default-group-added-article-mark that
> would be initially set to " ".

That's similar to an idea I had a while ago: replacing
gnus-gcc-mark-as-read with gnuc-gcc-marks, which would be a list of
mark symbols that would be automatically added to Gcc'ed articles.

NB: any code that works with marks should always use the symbols, not
the characters, whenever possible.  The symbols represent the true
state of an article, and are nearly orthogonal.  The characters are a
lossy, non-orthogonal representation of the symbols, used for the sake
of conserving screen space.  But there's no reason to inflict lossage
on other parts of the code.


paul



  parent reply	other threads:[~2003-05-19 16:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 19:56 Rob Browning
2003-05-17 21:29 ` Andreas Fuchs
2003-05-18  2:57   ` Rob Browning
2003-05-18  3:19   ` Rob Browning
2003-05-18  9:52     ` Kai Großjohann
2003-05-18 18:38       ` Rob Browning
2003-05-18 18:50         ` Rob Browning
2003-05-19 13:02           ` Kai Großjohann
2003-05-19 13:02         ` Kai Großjohann
2003-05-19 16:57         ` Paul Jarc [this message]
2003-05-19 16:47       ` Paul Jarc
2003-05-19 20:49         ` Kai Großjohann
2003-05-19 20:57           ` Paul Jarc
2003-05-20 10:56             ` Kai Großjohann
2003-05-20 17:33           ` Rob Browning
2003-05-22  7:04             ` Kai Großjohann

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=m365o6g9gz.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    --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).