From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: gnus-user-format-function-* in non-user code
Date: Fri, 20 May 2011 08:15:56 +0200 [thread overview]
Message-ID: <878vu1ucbn.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87sjsbatci.fsf@lifelogs.com>
On Thu, May 19 2011, Ted Zlatanov wrote:
> On Thu, 19 May 2011 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>
> RS> On Wed, May 18 2011, Ted Zlatanov wrote:
>
> 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?
Maybe `gnus-registry-format-function-char' and
`gnus-registry-format-function-word'?
> 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?
Although it is not spelled out in the manual[1], I think that the user
defined functions (and format specifiers) should be reserved for the
user just like the keys[2] that are reserved for users. In this way
the user can be sure that Gnus won't overwrite his bindings[3].
[1]
,----[ (info "(gnus)Summary Buffer Lines") ]
| `u'
| User defined specifier. The next character in the format string
| should be a letter. Gnus will call the function
| `gnus-user-format-function-X', where X is the letter following
| `%u'. [...]
`----
[2] (info "(emacs)Keymaps")
[3] "bad example": (info "(gnus)The Gnus Diary Library")
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2011-05-20 6:15 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 ` gnus-user-format-function-* in non-user code Ted Zlatanov
2011-05-20 6:15 ` Reiner Steib [this message]
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=878vu1ucbn.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).