From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.help Subject: Re: Specifying plist requirements in defcustom? Date: Wed, 15 Oct 2008 16:54:22 +0200 Message-ID: <48F6041E.5050707@gmail.com> References: <006f01c92ed5$5b49e150$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1224082613 7137 80.91.229.12 (15 Oct 2008 14:56:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Oct 2008 14:56:53 +0000 (UTC) Cc: 'jrwats' , help-gnu-emacs@gnu.org To: Drew Adams Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Oct 15 16:57:53 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Kq7oZ-0004oZ-BV for geh-help-gnu-emacs@m.gmane.org; Wed, 15 Oct 2008 16:57:31 +0200 Original-Received: from localhost ([127.0.0.1]:35853 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kq7nU-0000Bg-1A for geh-help-gnu-emacs@m.gmane.org; Wed, 15 Oct 2008 10:56:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kq7nC-0000Ba-4R for help-gnu-emacs@gnu.org; Wed, 15 Oct 2008 10:56:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kq7n9-0000BO-P3 for help-gnu-emacs@gnu.org; Wed, 15 Oct 2008 10:56:04 -0400 Original-Received: from [199.232.76.173] (port=40299 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kq7n9-0000BL-Ic for help-gnu-emacs@gnu.org; Wed, 15 Oct 2008 10:56:03 -0400 Original-Received: from ch-smtp01.sth.basefarm.net ([80.76.149.212]:47450) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Kq7n8-0002qE-Rl for help-gnu-emacs@gnu.org; Wed, 15 Oct 2008 10:56:03 -0400 Original-Received: from c83-254-151-87.bredband.comhem.se ([83.254.151.87]:59649 helo=[127.0.0.1]) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Kq7mQ-0004Vu-4D; Wed, 15 Oct 2008 16:55:30 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: <006f01c92ed5$5b49e150$0200a8c0@us.oracle.com> X-Enigmail-Version: 0.95.7 X-Antivirus: avast! (VPS 081014-0, 2008-10-14), Outbound message X-Antivirus-Status: Clean X-Originating-IP: 83.254.151.87 X-Scan-Result: No virus found in message 1Kq7mQ-0004Vu-4D. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1Kq7mQ-0004Vu-4D 299f7f0b59d7cec55a922b2bb819f403 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6? (barebone, rare!) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:58804 Archived-At: Drew Adams wrote: >>> (defcustom corext-enlistments nil >>> "..." >>> :type >>> '(repeat >>> (restricted-sexp >>> :match-alternatives >>> ((lambda (x) (and (symbolp x) >>> (let ((pl (symbol-plist x))) >>> (and (plist-get pl 'branch) >>> (plist-get pl 'drive) >>> (plist-get pl 'path))))))))) >>> >> From what I could tell, this worked, but I was also to have a user- >> friendly customization interface when a user, say, clicked customoize >> corext-enlistments. I'd like a prompt for the symbol-name, and the >> individual property list values: branch, drive, and path. It seems >> that to acheive something like this, I'd need to just make them >> alists.... > > You'll have to extend Customize to get that, AFAIK. Or write your own command to > customize this particular option. Customize doesn't really guide you with > prompts and such. Customize could use a little more guidance, especially for > complex structures such as this one. I do not think that you have to extend Customize. Writing a new widget type should be enough. > There are a lot of ways in which Customize could be improved, but no one seems > to want to work on it. Many Emacs developers have, I think, written it off as > being either (1) superfluous (~real Emacs users don't use Customize~, meaning > that they don't use it) or (2) too difficult/bothersome (the Customize code is > hard to follow). No flames please - that's just one person's impression. > > > >