From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: gnus-registry flags API
Date: Sat, 16 Feb 2008 21:26:36 +0100 [thread overview]
Message-ID: <v9k5l48x6r.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <86d4raats5.fsf@lifelogs.com>
On Wed, Feb 06 2008, Ted Zlatanov wrote:
> On Wed, 16 Jan 2008 15:52:29 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote:
> TZ> 1) do we push the registry on everyone?
I think it should be optional.
[...]
> TZ> gnus-registry-trim will always keep articles with marks and any other
> TZ> extra symbols you put in gnus-registry-extra-entries-precious.
Good.
> TZ> Please test and review if you have a chance.
>
> I haven't heard back about these questions, so:
>
> 1)
>
> Has anyone started using registry marks?
I didn't, sorry.
> Also a formatting function that shows them in the modeline would be
> nice, but since there can be many flags and little space I'm not
> sure what's the best way to display them.
I'd expected them to show up in the summary buffer just like ticked,
answered, etc. We could display a string or a small image (I never
tried):
'(("Important" "I" "summary_important")
("Work" "W" "summary_work")
("Personal" "P" "summary_personal")
("To do" "T" "summary_todo")
("Later" "L" "summary_later"))
"Alist of regular expressions and summary line indicators."
("summary_*": images corresponding to the labels.)
Can we have multiple registry marks for a single article? If not, we
may either display all strings/images or add a plus sign.
> Also, what keys should I bind to set custom flags in the group
s/group/summary/ ?
> and article buffers?
Maybe use `M m' or `M M' as prefix command? (e.g. `M M t' for "To
do", ...)
> 2)
>
> If no one has objections, I'll set up the interactive query for registry
> first-time use in gnus.el. There will be three values for
> gnus-registry-enabled:
>
> nil: unknown, ask the user next time
> t: enable
> 'no-thanks: user doesn't want it
>
> Every user will have to answer it by default. Is that a bad idea?
Yes.
> What else can I do?
I'd prefer an interface like `message-use-idna':
:type '(choice (const :tag "Ask" ask)
(const :tag "Never" nil)
(const :tag "Always" t))
nil and t are clear, I think. When `ask', prompt the user to enable
the registry when trying to set a mark (cf. the safe-local-variables
interface). When the user allows, store gnus-registry-enabled = t in
via customize.
Is that feasible?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-02-16 20:26 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
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 [this message]
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=v9k5l48x6r.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).