Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Ding Mailing List <ding@gnus.org>
Subject: Re: gnus-registry flags API
Date: Tue, 18 Dec 2007 19:22:35 -0600	[thread overview]
Message-ID: <861w9jeaw4.fsf@lifelogs.com> (raw)
In-Reply-To: <m2bqbq3e5b.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 25 Sep 2007 11:26:08 -0500")

On Tue, 25 Sep 2007 11:26:08 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> The frontend functionality I would like:

TZ> - set a flag for an article (this should be a simple function a user can
TZ> call from a group or message buffer, which grabs the message ID and uses
TZ> the gnus-registry API afterwards)

TZ> - indicate the article flags somehow (fringe or status line maybe?)

TZ> - add summary line formatting support for arbitrary flags

TZ> Any suggestions or contributions (especially the three items above) are
TZ> welcome.  Please review and criticize the code if you can, I haven't
TZ> done Emacs Lisp in a bit :)

I added the essential functions (first on the list) in CVS, now we need
a status line / summary line integration for these.  Note that the MARK
here is really any Lisp symbol, so 'hello-there-flag and
'goodbye-here-but-I-like-verbosity-flag are OK.  Go wild.

gnus-registry-mark-article ARTICLE &optional MARK REMOVE

- if ARTICLE is nil, use current article

- if MARK is nil, use gnus-registry-flag-default (you don't want that,
  it's boring)

- if REMOVE is t, remove MARK from the flags

gnus-registry-article-marks ARTICLE: get list of marks for the article

- if ARTICLE is nil, use current article

Let me know if you find bugs or inconsistencies.  I am especially
curious how these should integrate with the other Gnus summary
functions, and if they should take prefix arguments, etc.  For me that's
not a big deal.

Ted



  parent reply	other threads:[~2007-12-19  1:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 16:26 Ted Zlatanov
2007-09-25 19:58 ` Bastien
2007-09-25 23:40 ` Leo
2007-12-19  1:22 ` Ted Zlatanov [this message]
2008-01-03 17:10   ` Reiner Steib
2008-01-03 17:55     ` Ted Zlatanov
2008-01-04 17:43       ` Reiner Steib
2008-01-15 21:56         ` Ted Zlatanov
2008-01-16 21:52           ` Ted Zlatanov
2008-02-06 17:17             ` Ted Zlatanov
2008-02-16 20:26               ` Reiner Steib
2008-02-28 15:12                 ` Ted Zlatanov
2008-02-28 20:04                   ` Reiner Steib
2008-02-29 23:19                     ` Ted Zlatanov
2008-03-04 22:43                     ` Ted Zlatanov
2008-03-05 19:00                       ` Ted Zlatanov
2008-03-06 21:50                         ` Ted Zlatanov

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=861w9jeaw4.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).