emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: John Hendy <jw.hendy@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Updated syntax for #+bind and no LaTeX \maketitle command?
Date: Fri, 24 May 2013 11:32:39 -0500	[thread overview]
Message-ID: <CA+M2ft_0akuL+LmjGB8S9eVBb70EqDXCp8_WEyNPyu_XTKEOMQ@mail.gmail.com> (raw)
In-Reply-To: <87hahszxxd.fsf@pierrot.dokosmarshall.org>

On Fri, May 24, 2013 at 1:36 AM, Nick Dokos <ndokos@gmail.com> wrote:
> Nick Dokos <ndokos@gmail.com> writes:
>
>>> #+bind: org-latex-title-command ""
>>>
>>> This is still generating a \maketitle line in my .tex file.
>>>
>>> What's the proper way to do this on Org 8.0?
>>>
>>>
>>
>> I suspect this is the same problem as the one discussed in the following:
>>
>>    http://thread.gmane.org/gmane.emacs.orgmode/72085
>>
>> Nicolas suggested using a file local variable for that problem and I've
>> verified that that solution also works for this one. Just add
>>
>> # Local Variables:
>> # org-latex-title-command: ""
>> # End:
>>
>> at the end of your file.
>
> No, I'm wrong: it's not the same problem. And using BIND should
> work in this case, assuming that it is allowed.
>
> Check the value of org-export-allow-bind-keywords. If nil, then
> BIND keywords seem to be ignored silently.

Thanks all! Not knowing about the org-export-allow-bind-keywords was
my issue, and setting it to =t= fixed it. Out of curiosity, what's the
difference between org-export-allow-BIND and
org-export-allow-bind-keywords? They M-x help on them sounds very
similar.

#+begin_help org-export-allow-bind-keywords
Documentation:
Non-nil means BIND keywords can define local variable values.
This is a potential security risk, which is why the default value
is nil.  You can also allow them through local buffer variables.
#+end_help

#+begin_help org-export-allow-BIND
Documentation:
Non-nil means allow #+BIND to define local variable values for export.
This is a potential security risk, which is why the user must confirm the
use of these lines.
#+end_help

Ah, nevermind. Based on the customize-variable menu option, I'm
thinking the latter is how org should automatically accept #+bind
settings, and the former is whether to allow #+bind settings at all.
Oddly, my value for org-export-allow-bind is set to "confirm" but I
just tested things and didn't get asked...



John

>
> --
> Nick
>
>

next prev parent reply	other threads:[~2013-05-24 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 22:48 Updated syntax for #+bind and no LaTeX \maketitle command? John Hendy
2013-05-23 22:57 ` Marcin Borkowski
2013-05-23 23:14 ` Rasmus
2013-05-24  5:47 ` Nick Dokos
2013-05-24  6:36   ` Nick Dokos
2013-05-24 16:32     ` John Hendy [this message]
2013-05-24 21:28       ` Sebastien Vauban

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=CA+M2ft_0akuL+LmjGB8S9eVBb70EqDXCp8_WEyNPyu_XTKEOMQ@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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 public 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).