From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: org-agenda-bulk-custom-functions Customize mismatch
Date: Tue, 10 May 2016 23:34:37 +0200
Message-ID: <878tzhk36a.fsf@saiph.selenimh>
References: <87mvo0irem.fsf@quiz.hudson-it.ddns.net>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34383)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1b0FIq-0003iA-7J
	for emacs-orgmode@gnu.org; Tue, 10 May 2016 17:34:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1b0FIk-00060j-UK
	for emacs-orgmode@gnu.org; Tue, 10 May 2016 17:34:50 -0400
Received: from relay4-d.mail.gandi.net ([217.70.183.196]:56466)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1b0FIk-00060I-Gd
	for emacs-orgmode@gnu.org; Tue, 10 May 2016 17:34:46 -0400
In-Reply-To: <87mvo0irem.fsf@quiz.hudson-it.ddns.net> (Phil Hudson's message
	of "Sun, 08 May 2016 14:57:21 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Phil Hudson <phil.hudson@iname.com>
Cc: emacs-orgmode@gnu.org

Hello,

Phil Hudson <phil.hudson@iname.com> writes:

> The first approach is supported by defcustom and gives us the chance to
> be both more descriptive and more prescriptive. It shouldn't break
> anything that isn't in fact already broken.
>
> The second approach is as simple as changing that `cadr` to a `cdr`, but
> it does risk breaking working configs where the alist was populated
> procedurally.
>
> I propose the first. Here's a patch.

Looks good. Thank you.

Could you send it using "git format-patch". Also, could you provide an
appropriate commit message? See
<http://orgmode.org/worg/org-contribute.html> for details.

Regards,

-- 
Nicolas Goaziou