From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus-user-format-function-* in non-user code
Date: Thu, 19 May 2011 05:16:13 -0500 [thread overview]
Message-ID: <87sjsbatci.fsf@lifelogs.com> (raw)
In-Reply-To: <87mxijusk2.fsf_-_@marauder.physik.uni-ulm.de>
On Thu, 19 May 2011 08:13:01 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> On Wed, May 18 2011, Ted Zlatanov wrote:
>> On Wed, 18 May 2011 05:42:03 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> `gnus-registry-user-format-function-M' will give you those marks as
TZ> single characters, [...]
>> <Lars>What the hey, I wrote `gnus-registry-user-format-function-M2' to
>> do what you needed.</Lars>
RS> Why do you name these function gnus-registry-*user*-format-function if
RS> they are predefined rather than *user*-defined?
Because they are supposed to be defaliased to
gnus-user-format-function-X so the naming echoed that.
What name would you use?
RS> I know, we already have such (IMHO) bad examples[1], but we should try
RS> to eliminate those instead of adding new ones.
Why is this bad? Does it confuse people or cause technical problems?
Ted
next prev parent reply other threads:[~2011-05-19 10:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 10:13 Registry Mark in Summary buffer Deepak Tripathi
2011-05-18 10:42 ` Ted Zlatanov
2011-05-18 11:31 ` Deepak Tripathi
2011-05-18 14:03 ` Ted Zlatanov
2011-05-18 20:43 ` Ted Zlatanov
2011-05-19 6:13 ` gnus-user-format-function-* in non-user code (was: Registry Mark in Summary buffer.) Reiner Steib
2011-05-19 10:16 ` Ted Zlatanov [this message]
2011-05-20 6:15 ` gnus-user-format-function-* in non-user code Reiner Steib
2011-05-20 14:42 ` Ted Zlatanov
2011-05-20 20:17 ` Reiner Steib
2011-05-31 16:52 ` Ted Zlatanov
2011-05-19 10:11 ` Registry Mark in Summary buffer Deepak Tripathi
2011-05-19 10:37 ` Ted Zlatanov
2011-05-19 11:14 ` Deepak Tripathi
2011-05-19 12:47 ` 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=87sjsbatci.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).