unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daimrod <daimrod@gmail.com>
To: emacs-devel@gnu.org
Subject: Customization Types: Splicing into Lists
Date: Mon, 01 Sep 2014 20:36:47 +0200	[thread overview]
Message-ID: <878um3w5kw.fsf@tanger.home> (raw)

Hi,

When I tried to use org-feed.el (an org-mode module used to follow
RSS/Atom feeds in org files) I found (I think) a weird bug.

It looks like it's impossible to use splicing as it is shown in the
manual.

(info "(elisp) Splicing into Lists") says:
> When the element-type is a ‘choice’, you use ‘:inline’ not in the
> ‘choice’ itself, but in (some of) the alternatives of the ‘choice’.  For
> example, to match a list which must start with a file name, followed
> either by the symbol ‘t’ or two strings, use this customization type:
> 
>      (list file
>            (choice (const t)
>                    (list :inline t string string)))
> 
> If the user chooses the first alternative in the choice, then the
> overall list has two elements and the second element is ‘t’.  If the
> user chooses the second alternative, then the overall list has three
> elements and the second and third must be strings.

To reproduce this "bug" I did:

1. evaluate
   (defcustom foo '("" t)
     "bar"
     :type '(list string (choice (const t)
                                 (list :inline t string string))))
2. M-x customize-variable RET foo RET
3. Change the "Choice" field by the "list" type.
4. Apply the change
5. M-x customize-variable RET foo RET -> error (mismatch)
   It looks like the structure isn't recognized by the Customize interface.

I encountered this "bug" on master, emacs24 and emacs23.


Am I crazy? Did I miss something?

Best,
-- 
Daimrod/Greg



             reply	other threads:[~2014-09-01 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 18:36 Daimrod [this message]
2014-09-05 11:16 ` Customization Types: Splicing into Lists Daimrod

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=878um3w5kw.fsf@tanger.home \
    --to=daimrod@gmail.com \
    --cc=emacs-devel@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 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).