emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Olivier <olivier107@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Any column character in #+LATEX_HEADER breaks the export [9.5.5 (release_9.5.5 @ c:/Program Files/Emacs/emacs-28.2/share/emacs/28.2/lisp/org/)]
Date: Fri, 18 Nov 2022 08:27:36 +0000	[thread overview]
Message-ID: <87sfigk6pz.fsf@localhost> (raw)
In-Reply-To: <CAEfUq3jk9fprk5EjZEKB+gcFv0FX6YRmocjDdai59DnxGzQh1A@mail.gmail.com>

Olivier <olivier107@gmail.com> writes:

> #+LATEX_HEADER:\newcommand{\macroOne}{drive:/windows-path/to/file1}
> #+LATEX_HEADER:\newcommand{\macroTwo}{drive/windows-path/to/file1}
> #+LATEX_HEADER:\newcommand{\macroThree}{:nothing}
> #+LATEX_HEADER:anything:with:columns

Thanks for reporting!

No space is not strictly prohibited, but if there is no space, we
consider the last colon to be the end of keyword name.

I'd say that we should suggest to use space everywhere yet keeping the
present behaviour for backwards compatibility.

I have amended the manual as you suggested.

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

      parent reply	other threads:[~2022-11-18  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 16:58 [BUG] Any column character in #+LATEX_HEADER breaks the export [9.5.5 (release_9.5.5 @ c:/Program Files/Emacs/emacs-28.2/share/emacs/28.2/lisp/org/)] Olivier
2022-11-17  9:59 ` Olivier
2022-11-18  8:27 ` Ihor Radchenko [this message]

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:

  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=87sfigk6pz.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=olivier107@gmail.com \


* 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


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).