emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Aaron Ecay <aaronecay@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: BEGIN_LATEX_HEADER [cont]
Date: Sun, 22 Jun 2014 11:36:53 +0200	[thread overview]
Message-ID: <877g492slm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m238ex8z2q.fsf@gorgonzola.lan> (Ken Mankoff's message of "Sat, 21 Jun 2014 22:19:17 -0400")

Ken Mankoff <mankoff@gmail.com> writes:

> It is not a 1x operation, it is a per-document operation. For example,
> in my use-case that started this whole discussion, each publication
> requires tweaking a dozen or more lines of biblatex config.

Of course there are an amount of lines that depends on the document.
This is where #+LATEX keywords comes handy.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2014-06-22  9:36 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
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 [this message]
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=877g492slm.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --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).