From: tsd@tsdye.com (Thomas S. Dye)
To: Jacob Gerlach <jacobgerlach@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Macro Argument Truncation
Date: Sun, 21 Sep 2014 15:40:51 -1000 [thread overview]
Message-ID: <m2bnq8sa8s.fsf@tsdye.com> (raw)
In-Reply-To: <CAA6UvuHMNt34uCQOLFXjyNm_ek4z5=5rJoVe+twap5t=nw+5MA@mail.gmail.com> (Jacob Gerlach's message of "Sun, 21 Sep 2014 21:12:30 -0400")
Aloha Jacob,
Jacob Gerlach <jacobgerlach@gmail.com> writes:
> I am making heavy use of latex strikeout for a report I'm preparing in org
> mode. I defined a macro for the necessary latex snippet, but the argument
> gets truncated on export.
>
> MWE:
> ----
> * Section
> {{{stk(The argument for this macro is several lines long. It seems
> that after a certain length, the macro argument gets truncated, as the
> tex output from exporting this org buffer contains a properly
> terminated strikeout block with only part of this text.)}}}
> #+MACRO: stk @@latex:\sout{$1}@@
>
> ----
> C-c C-e l L produces:
> ----
> ....
> \sout{The argument for this macro is several lines long. It seems
> that after a certain length}
> % Emacs 24.3.1 (Org mode 8.2.7c)
> ----
>
> I see no mention of any reason for this in the macro node of the manual or
> on list archives. Am I doing something wrong or is it a bug?
Arguments to the macro are separated by commas. Your text gets
truncated at the first comma.
From the manual:
/============================================================\
| You can define text snippets with |
| |
| #+MACRO: name replacement text $1, $2 are arguments |
| |
| which can be referenced {{{name(arg1, arg2)}}}. |
\============================================================/
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2014-09-22 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 1:12 [BUG] Macro Argument Truncation Jacob Gerlach
2014-09-22 1:40 ` Thomas S. Dye [this message]
2014-09-22 1:50 ` Jacob Gerlach
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=m2bnq8sa8s.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jacobgerlach@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
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/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).