From: Thomas S. Dye <tsd@tsdye.com>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>, Rasmus <rasmus@gmx.us>
Subject: Re: Subtree export problems
Date: Sat, 06 Feb 2016 13:39:40 -1000 [thread overview]
Message-ID: <m2wpqhh0hv.fsf@tsdye.com> (raw)
In-Reply-To: <87wpqhqyo8.fsf@gmail.com>
Aloha Aaron,
Aaron Ecay <aaronecay@gmail.com> writes:
> PS Tom, the approach you are using to this looks rather convoluted.
> Instead of a src block + keyword thing, why not just use #+latex (or
> #+latex_header) to insert the code you need?
Agreed. I'm trying to write to a general audience. The convoluted
approach works well for bits of text that get typeset in the front
matter of a book, for instance. I can direct the user to change a
keyword in plain view at the top of the buffer, rather than ask them to
change an argument to a function, or rummage through some LaTeX code to
find where a change should be made.
MARGIN-NOTE-FONT isn't a particularly good example of this because the
user is expected to know some LaTeX. If I find time, I'll browse my
library to see if I can classify margin notes. If so, then
MARGIN-NOTE-FONT can be set to a class name rather than LaTeX code.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2016-02-06 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 0:34 Subtree export problems Thomas S. Dye
2016-02-06 14:17 ` Rasmus
2016-02-06 22:08 ` Aaron Ecay
2016-02-06 22:24 ` Rasmus
2016-02-06 23:39 ` Thomas S. Dye [this message]
2016-02-06 23:03 ` Thomas S. Dye
2016-02-07 0:14 ` Rasmus
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=m2wpqhh0hv.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).