emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Feng Shu <tumashu@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Better way to specify the latex documentclass of an exported file without changing my configuration?
Date: Wed, 26 Mar 2014 13:47:02 +0100	[thread overview]
Message-ID: <m2siq52kl5.fsf@polytechnique.org> (raw)
In-Reply-To: <87ob0tjorv.fsf@news.tumashu-localhost.org> (Feng Shu's message of "Wed, 26 Mar 2014 17:24:36 +0800")

Feng Shu <tumashu@gmail.com> writes:

> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> Hello,
>>
>> I'm collaborating on a paper with some colleagues, and I convinced them
>> to use org-mode. I'm trying to make sure the paper is as self-contained
>> as possible (I don't want them to have to change their emacs
>> configuration file).To change the documentclass name of the exported
>
> Maybe you can write a Makefile to change their emacs configure...

I don't want to push my luck ;-)

>> My questions are:
>> - is there a way to do this without an emacs-lisp block?
>> - is there a nicer way to make sure that an emacs-lisp block is
>> evaluated upon export than ":exports results :results silent"? (If
>> I don't put it there, the block is not evaluated.)
>> - is there a way to just say the name of the documentclass without all
>> the boilerplate code below? In other words, can I say "this is a llncs
>> documentclass with the same sectioning as an article"?
>
> You should defun a classe for llncs.sty before use it. maybe
> you can rename llncs.sty to article.sty, and put it to directory which contain
> your org file.

Yes, this could be a way to do it. The current approach works, I find it
a little bit too verbose, though.

Thank you for the suggestion,

Alan

  parent reply	other threads:[~2014-03-26 12:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  8:37 Better way to specify the latex documentclass of an exported file without changing my configuration? Alan Schmitt
2014-03-26  9:24 ` Feng Shu
2014-03-26 12:38   ` Fabrice Niessen
2014-03-26 12:53     ` Alan Schmitt
2014-03-26 18:46       ` Thomas S. Dye
2014-03-26 22:03         ` Alan Schmitt
2014-03-26 12:47   ` Alan Schmitt [this message]
2014-03-26 23:26     ` Richard Lawrence
2014-03-26 13:21 ` Nicolas Goaziou
2014-03-26 13:54   ` Alan Schmitt
2014-03-26 14:10     ` Nicolas Goaziou
2014-03-26 14:57       ` Alan Schmitt

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=m2siq52kl5.fsf@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=tumashu@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).