emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>,
	Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BEGIN_LATEX_HEADER [cont]
Date: Sat, 21 Jun 2014 20:42:39 -0400	[thread overview]
Message-ID: <87tx7dbwqo.fsf@gmail.com> (raw)
In-Reply-To: <87simyk796.fsf@nicolasgoaziou.fr>

Hi Nicolas,

2014ko ekainak 21an, Nicolas Goaziou-ek idatzi zuen:
> 
> Hello,
> 
> Aaron Ecay <aaronecay@gmail.com> writes:
> 
>> The first is that editing non-trivial latex code embedded in an elisp
>> string quickly becomes tedious, whereas it’s much pleasanter in org
>> using org-edit-special, syntax highlighting of src blocks, etc.
> 
> This is a no-op since you only do it a limited number of times, i.e.
> once for each document type.

If you do it once, then it’s not a no-op, by definition.  I think you
mean that you disagree in the amount which you weight this as a concern,
which is a reasonable opinion to have.  But phrasing it in the way you
did is inaccurate and rather curt.

FWIW, in my experience latex (or any) code rarely flows from mind to
keyboard perfectly in the first attempt; there is some period of
revision, during which convenient editing matters.

> 
>> The second is that it’s impossible to share without distributing elisp
>> code.  From the twin standpoints of reproducible research and security,
>> I think org ought to maximize the degree to which export use cases are
>> sharable without resorting to executing elisp code.
> 
> This is also a no-op. You cannot be serious about reproducible research
> if you don't share `org-export-async-init-file' anyway.

This is also not true (or it’s some kind of value judgment).  Org’s
default settings + #+bind + local variables can do quite a bit.

> 
> Eventually, if you insist on writing your full preamble within the
> document, you can start to write it in a LaTeX-mode buffer, copy it in
> your Org document and add "#+LATEX_HEADER: " in front of each line.
> This last step is done easily with `string-rectangle' (C-x r t).

This is basically making the user do (something like) org-edit-special
manually.  It can probably be automated somewhat – I’ll work on a patch.

Thanks,

-- 
Aaron Ecay

  reply	other threads:[~2014-06-22  0:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 23:37 BEGIN_LATEX_HEADER [cont] Ken Mankoff
2014-06-19 23:48 ` Aaron Ecay
2014-06-20  7:51   ` Sebastien Vauban
2014-06-20  8:50     ` Nicolas Goaziou
2014-06-20 11:17       ` Ken Mankoff
2014-06-20 11:52         ` Fabrice Popineau
2014-06-20 12:11         ` Nicolas Goaziou
2014-06-21  5:43           ` Aaron Ecay
2014-06-21  8:16             ` Nicolas Goaziou
2014-06-22  0:42               ` Aaron Ecay [this message]
2014-06-22  2:00                 ` [ANN] ox-extras (was: BEGIN_LATEX_HEADER [cont]) Aaron Ecay
2014-06-22 22:07                   ` [ANN] ox-extras Rasmus
2014-06-22 22:08                     ` Rasmus
2014-06-23 19:57                   ` Nicolas Goaziou
2014-06-23 20:29                     ` Thomas S. Dye
2014-06-22  2:19                 ` BEGIN_LATEX_HEADER [cont] Ken Mankoff
2014-06-22  9:36                   ` Nicolas Goaziou
2014-06-22  9:35                 ` 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=87tx7dbwqo.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=mankoff@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).