From: Feng Shu <tumashu@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Override the default class name with a new one.
Date: Fri, 14 Jun 2013 18:42:02 +0800 [thread overview]
Message-ID: <87li6dc6th.fsf@news.tumashu-localhost.org> (raw)
In-Reply-To: <87k3lxxbqe.fsf@pierrot.dokosmarshall.org> (Nick Dokos's message of "Fri, 14 Jun 2013 05:50:17 -0400")
Nick Dokos <ndokos@gmail.com> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> Feng Shu <tumashu@gmail.com> writes:
>>
>>> #+LATEX_CLASS: article
>>> #+LATEX_CLASS_NAME: ctexart
>>
>> I'm not sure this is the right approach. . . I can certainly see the
>> value of generating classes on the fly, though. But somehow the
>> proposed syntax just seems to counter-intuitive. I'm not sure how to
>> overcome this, but perhaps it would be better to allow for an argument
>> to LATEX_CLASS, e.g.
>>
>> (*) #+LATEX_CLASS: myclass :class-name ctexart.
>>
>
> That was what popped into my head as well - I didn't much care for the
> OP's approach. Now that I've thought about it some more, I'm not sure I
> like this one much better...
>
>> as e.g. the INCLUDE command. Of course (*) is somewhat different from
>> how stuff like this is usually handled, cf. e.g. LATEX_CLASS_OPTIONS.
>>
> ...but this sounds a bit more promising: maybe LATEX_CLASS_OPTIONS can
> be eliminated in favor of LATEX_CLASS with arguments:
>
> #+LATEX_CLASS: key :class-name foo :class-options a4paper,12pt
May be we should add this feature too:
#+LaTEX_CLASS: key :class-name foo :class-options+ twoside
#+LaTEX_CLASS: key :class-name foo :class-options- twoside
>
> where "key" selects from org-latex-classes (and is optional, default
> "article"), class-name is optional and defaults to key (or article if
> key is absent).
--
next prev parent reply other threads:[~2013-06-14 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 6:14 [PATCH] Override the default class name with a new one Feng Shu
2013-06-13 23:55 ` Feng Shu
2013-06-14 9:13 ` Rasmus
2013-06-14 9:50 ` Nick Dokos
2013-06-14 10:09 ` Rasmus
2013-06-14 10:42 ` Feng Shu [this message]
2013-06-14 9:55 ` Feng Shu
2013-06-14 11:50 ` Suvayu Ali
2013-06-14 13:36 ` Nicolas Goaziou
2013-06-14 15:13 ` Feng Shu
2013-06-18 19:34 ` Nicolas Goaziou
2013-06-18 22:33 ` 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=87li6dc6th.fsf@news.tumashu-localhost.org \
--to=tumashu@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).