From: jrwats <jrwats@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Specifying plist requirements in defcustom?
Date: Wed, 15 Oct 2008 09:27:16 -0700 (PDT) [thread overview]
Message-ID: <d3430bb6-d754-4326-9ddb-c6481f1499cb@2g2000hsn.googlegroups.com> (raw)
In-Reply-To: mailman.1123.1224085332.25473.help-gnu-emacs@gnu.org
> ~All you have to do is write...~ means that it's not there already. Playing with
> widgets is, in my book, extending Customize. And it's not necessarily a
> clear-cut exercise.
I ostensibly agree. Despite all the searching I did, I could not find
a solid example of creating a new widget. And they all seemed
graphics related... The default customization prompt that occurs with
something like this:
(defcustom rep-list '(("wcdc" "working.client.deskcomm" "e:" "e:
\wcdeskomm"))
"test this!"
:type '(repeat (list
(string :tag "name")
(string :tag "branch")
(string :tag "drive")
(string :tag "path"))))
is EXACTLY what I want - I just want a plist with keys: name, branch,
drive, and path rather than a list, so I don't have to write silly
things like:
(defun path (cadddr list))
...I might just give in to silly application code for the sake of user-
friendly client experience.
next prev parent reply other threads:[~2008-10-15 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 20:46 Specifying plist requirements in defcustom? jrwats
2008-10-12 23:18 ` Lennart Borgman (gmail)
2008-10-13 1:31 ` Drew Adams
[not found] ` <mailman.901.1223861517.25473.help-gnu-emacs@gnu.org>
2008-10-15 14:32 ` jrwats
2008-10-15 14:50 ` Drew Adams
2008-10-15 14:54 ` Lennart Borgman (gmail)
2008-10-15 15:41 ` Drew Adams
[not found] ` <mailman.1123.1224085332.25473.help-gnu-emacs@gnu.org>
2008-10-15 16:27 ` jrwats [this message]
2008-10-15 16:33 ` jrwats
2008-10-15 16:48 ` jrwats
2008-10-15 16:58 ` Drew Adams
[not found] ` <mailman.1126.1224089933.25473.help-gnu-emacs@gnu.org>
2008-10-15 17:43 ` jrwats
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=d3430bb6-d754-4326-9ddb-c6481f1499cb@2g2000hsn.googlegroups.com \
--to=jrwats@gmail.com \
--cc=help-gnu-emacs@gnu.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.
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.