all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: MON KEY <monkey@sandpframing.com>
Cc: 3639@debbugs.gnu.org
Subject: bug#3639: 23.0.95; defcustom docstring ':link' ':tag' NAME and/or LABEL?
Date: Tue, 12 Jul 2011 17:21:59 +0200	[thread overview]
Message-ID: <m339ible20.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <878wjln1b4.fsf@sandpframing.com> (MON KEY's message of "Sun, 21 Jun 2009 09:50:23 -0400")

MON KEY <monkey@sandpframing.com> writes:

> The docstring for defcustom's keyword `:link' states:
>
> "You can specify the text to use in the customization buffer by adding `:tag
>  NAME' after the first element of the LINK-DATA; for example, (info-link :tag
>  "foo" "(emacs)Top") makes a link to the Emacs manual which appears in the
>  buffer as `foo'."
>
> Shortly thereafter a description of defcustom's keyword `:tag' states:
>
> ":tag LABEL Use LABEL, a string, instead of the item's name, to label the item
>         in customization menus and buffers."
>
> If these two uses of 'tag' have identical context, then the `:tag NAME'
> descriptor of the `:link' section should clarify this and/or change 'NAME' ->
> 'LABEL'. 
>
> If the context of 'tag' is mutually exclusive then _that_ should
> be clarified. As presented, it is not clear if `:tag' has different meanings within defcustom forms according to where it occurs.

The first talks about using :tag inside `info-link'.  The second about
using :tag in the `defcustom' top-level.  It seems pretty clear to me,
and I know next to nothing about `defcustom', so I think this doesn't
need clarification.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2011-07-12 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-21 13:50 bug#3639: 23.0.95; defcustom docstring ':link' ':tag' NAME and/or LABEL? MON KEY
2011-07-12 15:21 ` Lars Magne Ingebrigtsen [this message]
2011-07-15 19:16   ` MON KEY

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=m339ible20.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=3639@debbugs.gnu.org \
    --cc=monkey@sandpframing.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.