Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@myrealbox.com>
Subject: Re: CVS update of gnus/lisp (ChangeLog message.el)
Date: Fri, 28 Nov 2003 23:26:41 +0100	[thread overview]
Message-ID: <m365h4yvry.fsf@defun.localdomain> (raw)
In-Reply-To: <E1APqoO-0003Ah-00@quimby.gnus.org>

"Reiner Steib" <reiner.steib@gmx.de> writes:

> Modified: ChangeLog message.el
>
> Added custom-manual links to all variables that have
> an index entry in the message manual.

I'm not sure that this is really a good idea.

It's probably nice when you use `customize-option', but it makes
`customize-group' awfully cluttered with a lot of identical and
redundant links.



       reply	other threads:[~2003-11-28 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1APqoO-0003Ah-00@quimby.gnus.org>
2003-11-28 22:26 ` Jesper Harder [this message]
2003-11-28 22:58   ` Adding :link '(custom-manual ...) in defcustom (was: CVS update of gnus/lisp (ChangeLog message.el)) Reiner Steib
2003-11-28 23:52     ` Adding :link '(custom-manual ...) in defcustom Reiner Steib
2003-11-29  9:01     ` Jesper Harder
2003-11-30 14:07       ` Per Abrahamsen

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=m365h4yvry.fsf@defun.localdomain \
    --to=harder@myrealbox.com \
    /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).