I used it for some days now. I tried to get rid of false positives,
especially for `gnus-button-handle-man' and
`gnus-button-handle-mid-or-mail'. Needless to say that it works for
me. ;-)

Suggested ChangeLog entry:

--8<---------------cut here---------------start------------->8---
	* gnus-art.el (gnus-button-handle-custom,
	gnus-button-handle-mid-or-mail,
	gnus-button-handle-describe-{function,variable,key},
	gnus-button-handle-apropos{,command,variable}): New functions.
	(gnus-button-prefer-mid-or-mail,gnus-button-guessed-mid-regexp,
	gnus-button-{man,emacs,mail}-level): New variables.
	(gnus-button-alist): Use the above to buttonize emacs and mail
	related links.
--8<---------------cut here---------------end--------------->8---

I have to mention, that the stuff related to custom is borrowed from
Simon's previous posting.

As I'm a Lisp beginner I would appreciate your comments.

Some remarks and questions:

(1)

Is `intern' (used in `gnus-button-handle-describe-*') the correct way
to get a symbol corresponding to a given string? `intern' creates a
symbol if it doesn't exist. Should we avoid this side effect in
`gnus-button-handle-describe-{function,variable}'?

(2)

Feel free to change (or suggest changes to) the doc-strings. I'm not
a native speaker, neither for English nor Gnus-speek. :-)

(3)

I couldn't find out how to implement `g-b-handle-describe-key'. I
added a regexp (needs to be improved!) in the list and a dummy
function. But the button is not enabled by default. If it doesn't seem
to be feasible this should be removed.

(4)

The regexp for g-b-handle-apropos could be improved too. It only
matches expressions without space up to now:

"M-x[ \t\n]apropos[ \t\n]\\([^ ]+\\)[ \t\n]RET"

(5)

Per Abrahamsen suggested in news:<rjvg5fz1rr.fsf@zuse.dina.kvl.dk>:
"We might want button types specific for groups whose name match some
regexp.".

Why don't we use the `FORM' mentioned in the doc-string of
`gnus-button-alist' in combination with group parameters or
`gnus-parameters'? I've chosen this way and added the
`gnus-button-*-level' variables (should we use a different naming
convention?). The user may set this variables specific to certain
groups. If he doesn't like buttons, he can set the `g-b-*-level'
variables to zero.

Andreas Fuchs mentioned <URL:http://asf.void.at/emacs/gnus-BTS.el>: He
uses `in-debian-group-p' (a variable. BTW: shouldn't *-p be a function
by convention?) and `gnus-article-mode-hook' to set the additional
buttons. Are there advantages over the `FORM'/gnus-parameters approach
described above?

(6)

I've signed the paperwork of the FSF for Emacs.

(7)

In news:<v9elbrt7tc.fsf@marauder.physik.uni-ulm.de> (in gnus.test)
you'll see some examples of the new buttons. Hope you like it.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/