From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: gnus-user-format-function-* in non-user code (was: Registry Mark in Summary buffer.)
Date: Thu, 19 May 2011 08:13:01 +0200 [thread overview]
Message-ID: <87mxijusk2.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87tycr3fjk.fsf@lifelogs.com>
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>
Why do you name these function gnus-registry-*user*-format-function if
they are predefined rather than *user*-defined?
I know, we already have such (IMHO) bad examples[1], but we should try
to eliminate those instead of adding new ones.
Bye, Reiner.
[1]
,----[ grep -nH -e user-format-function *.el ]
| gnus-diary.el:159:(defun gnus-user-format-function-d (header)
| gnus-diary.el:196:(defun gnus-user-format-function-D (header)
| gnus.el:2981: function gnus-user-format-function-X, where X is the
| gnus-group.el:196: be a letter. Gnus will call the function gnus-user-format-function-X,
| gnus-load.el:728:;;;### (autoloads (gnus-user-format-function-D gnus-user-format-function-d)
| gnus-load.el:732:(autoload (quote gnus-user-format-function-d) "gnus-diary" "\
| gnus-load.el:737:(autoload (quote gnus-user-format-function-D) "gnus-diary" "\
| gnus-registry.el:65:;; (defalias 'gnus-user-format-function-M 'gnus-registry-user-format-function-M)
| gnus-registry.el:68:;; (defalias 'gnus-user-format-function-M 'gnus-registry-user-format-function-M2)
| gnus-registry.el:901:;; (defalias 'gnus-user-format-function-M 'gnus-registry-user-format-function-M)
| gnus-registry.el:902:(defun gnus-registry-user-format-function-M (headers)
| gnus-registry.el:914:;; (defalias 'gnus-user-format-function-M 'gnus-registry-user-format-function-M2)
| gnus-registry.el:915:(defun gnus-registry-user-format-function-M2 (headers)
| gnus-spec.el:620: "gnus-user-format-function-%s"
| gnus-spec.el:621: "gnus-user-format-function-%c")
| spam.el:1180:(defun spam-user-format-function-S (headers)
`----
Grep finished (matches found) at Thu May 19 08:08:32
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2011-05-19 6:13 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 ` Reiner Steib [this message]
2011-05-19 10:16 ` gnus-user-format-function-* in non-user code Ted Zlatanov
2011-05-20 6:15 ` 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=87mxijusk2.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).