From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: :format strings in Custom ending in %h
Date: Thu, 21 Aug 2003 14:22:04 +0200 [thread overview]
Message-ID: <rjzni3kxoz.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: 200308210154.h7L1sJc21082@raven.dms.auburn.edu
Does this fix the problem?
We should probably always call widget-children-value-delete, as any
widget may have children if they have a long doc string.
-- Per
2003-08-21 Per Abrahamsen <abraham@dina.kvl.dk>
* wid-edit.el (item): Delete children (due to doc-string).
*** wid-edit.el.~1.120.~ Thu Aug 21 14:17:37 2003
--- wid-edit.el Thu Aug 21 14:19:14 2003
***************
*** 1556,1562 ****
"Constant items for inclusion in other widgets."
:convert-widget 'widget-value-convert-widget
:value-create 'widget-item-value-create
! :value-delete 'ignore
:value-get 'widget-value-value-get
:match 'widget-item-match
:match-inline 'widget-item-match-inline
--- 1556,1562 ----
"Constant items for inclusion in other widgets."
:convert-widget 'widget-value-convert-widget
:value-create 'widget-item-value-create
! :value-delete 'widget-children-value-delete
:value-get 'widget-value-value-get
:match 'widget-item-match
:match-inline 'widget-item-match-inline
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Sorry, my original file had an inconsistency with the defgroup and the
> :group. The bug is real however and stays with the following
> corrected file. Only difference:
>
> :group 'nifty-group gets replaced with:
>
> :group 'nifty
>
> ===File ~/customdoc.el======================================
> (defgroup nifty nil
> "Single item group"
> :group 'convenience)
>
> (defcustom nifty-var nil
> "*Nifty doc string."
> :group 'nifty
> :type '(choice (const :tag "True"
> :format "%t\n%h"
> :doc
> "True stuff.
> Second line of true stuff."
> t)
> (other :tag "False"
> :format "%t\n%h"
> :doc
> "Falsehoods.
> Second line of falsehoods"
> nil)))
>
> ============================================================
next prev parent reply other threads:[~2003-08-21 12:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 1:54 :format strings in Custom ending in %h Luc Teirlinck
2003-08-21 12:22 ` Per Abrahamsen [this message]
2003-08-21 20:50 ` Luc Teirlinck
2003-08-21 21:00 ` Luc Teirlinck
2003-08-22 11:22 ` Per Abrahamsen
2003-08-22 14:41 ` Luc Teirlinck
2003-08-24 15:38 ` Per Abrahamsen
2003-08-24 17:17 ` Luc Teirlinck
2003-08-24 18:30 ` Per Abrahamsen
2003-10-20 18:05 ` Luc Teirlinck
2003-10-20 21:10 ` Luc Teirlinck
2003-10-22 9:24 ` Richard Stallman
2003-10-22 9:41 ` Per Abrahamsen
2003-10-23 18:37 ` Richard Stallman
2003-10-24 16:00 ` Per Abrahamsen
2003-10-25 22:26 ` Richard Stallman
2003-10-21 12:03 ` Per Abrahamsen
2003-08-23 2:44 ` Luc Teirlinck
2003-08-23 15:32 ` Luc Teirlinck
2003-08-23 3:25 ` Luc Teirlinck
2003-08-23 18:09 ` Luc Teirlinck
2003-08-23 18:32 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2003-08-21 1:42 Luc Teirlinck
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rjzni3kxoz.fsf@zuse.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).