emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Ezequiel Birman <stormwatch@espiga4.com.ar>, emacs-orgmode@gnu.org
Subject: Re: new exporter, conditional options according to backend
Date: Sun, 20 Jan 2013 21:52:04 +0530	[thread overview]
Message-ID: <87libng6z7.fsf@gmail.com> (raw)
In-Reply-To: <87fw1w19v5.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 20 Jan 2013 10:28:46 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>
>>> #+begin_src emacs-lisp
>>> (defun my-options-change-fun (tree backend info)
>>>   (when (org-export-derived-backend-p backend 'e-beamer)
>>>     (plist-put info :with-author nil))
>>>   ;; Don't forget to return tree.
>>>   tree)
>>
>> CAVEAT: plist-put can return a different list, at times.
>>
>> I don't know enough about implementation of `plist-put' to ascertain
>> when it would return a new list.
>
> Since the OP wants to modify the values of _existing properties_ I'm
> quite sure the change will happen in place.

Look at example in Elisp manual.  New members seem to get appended.  

List being destructive is explainable if new members were to be added to
the head.  Since this is not the case, I am curious what the
implementation could be ...


>
>
> Regards,

-- 

  reply	other threads:[~2013-01-20 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 15:47 Ezequiel Birman
2013-01-19 22:48 ` Nicolas Goaziou
2013-01-20  4:38   ` Ezequiel Birman
2013-01-20  5:35   ` Jambunathan K
2013-01-20  9:28     ` Nicolas Goaziou
2013-01-20 16:22       ` Jambunathan K [this message]
2013-01-28  7:12         ` Nicolas Goaziou
2013-01-24 20:32   ` Andreas Leha
2013-01-25 13:23     ` Nicolas Goaziou
2013-01-25 17:37   ` cberry
2013-01-25 17:50     ` Nicolas Goaziou

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87libng6z7.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=stormwatch@espiga4.com.ar \
    --subject='Re: new exporter, conditional options according to backend' \
    /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

Code repositories for project(s) associated with this inbox:

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).