From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.help Subject: RE: Specifying plist requirements in defcustom? Date: Wed, 15 Oct 2008 08:41:59 -0700 Message-ID: <001701c92edc$9066f880$c2b22382@us.oracle.com> References: <006f01c92ed5$5b49e150$0200a8c0@us.oracle.com> <48F6041E.5050707@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1224085402 18471 80.91.229.12 (15 Oct 2008 15:43:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Oct 2008 15:43:22 +0000 (UTC) Cc: 'jrwats' , help-gnu-emacs@gnu.org To: "'Lennart Borgman \(gmail\)'" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Oct 15 17:44:22 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 1Kq8X9-000702-Oy for geh-help-gnu-emacs@m.gmane.org; Wed, 15 Oct 2008 17:43:36 +0200 Original-Received: from localhost ([127.0.0.1]:58406 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kq8W5-00005A-1d for geh-help-gnu-emacs@m.gmane.org; Wed, 15 Oct 2008 11:42:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kq8Vm-00004s-Kq for help-gnu-emacs@gnu.org; Wed, 15 Oct 2008 11:42:10 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kq8Vk-0008Vs-PR for help-gnu-emacs@gnu.org; Wed, 15 Oct 2008 11:42:10 -0400 Original-Received: from [199.232.76.173] (port=37440 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kq8Vk-0008Vm-Ga for help-gnu-emacs@gnu.org; Wed, 15 Oct 2008 11:42:08 -0400 Original-Received: from agminet01.oracle.com ([141.146.126.228]:46290) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Kq8Vk-00032u-6U for help-gnu-emacs@gnu.org; Wed, 15 Oct 2008 11:42:08 -0400 Original-Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id m9FFg1wV021037; Wed, 15 Oct 2008 10:42:01 -0500 Original-Received: from acsmt700.oracle.com (acsmt700.oracle.com [141.146.40.70]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m9FFg02p008212; Wed, 15 Oct 2008 09:42:00 -0600 Original-Received: from dradamslap1 (/130.35.178.194) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 15 Oct 2008 08:42:00 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <48F6041E.5050707@gmail.com> Thread-Index: Acku1l1NkLl61lozSFmw+jNi6Vul4AABWqgQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 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:58807 Archived-At: > >> 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. I call that extending Customize. Customize out of the box won't provide that behavior. ~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.