emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Lewis <richardlewis@fastmail.co.uk>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: #+LaTeX_CLASS regex too restrictive?
Date: Sat, 29 Oct 2011 17:52:23 +0100	[thread overview]
Message-ID: <8762j7n3js.wl%richard.lewis@gold.ac.uk> (raw)
In-Reply-To: <32194.1319906065@alphaville.dokosmarshall.org>

At Sat, 29 Oct 2011 12:34:25 -0400,
Nick Dokos wrote:
> Richard Lewis <richardlewis@fastmail.co.uk> wrote:
> > 
> > The class name I'm using includes "/" characters.
> It seems to me that that's a bad idea: class names correspond to file
> names (without the .cls extension), so "/" characters will probably
> cause confusion (at least on Unix-based filesystems).

But what's the relationship between org-export-latex-classes and LaTeX
class files?


  reply	other threads:[~2011-10-29 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 11:19 #+LaTeX_CLASS regex too restrictive? Richard Lewis
2011-10-29 12:44 ` Bastien
2011-10-29 16:34 ` Nick Dokos
2011-10-29 16:52   ` Richard Lewis [this message]
2011-10-29 17:59     ` Nick Dokos

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:

  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=8762j7n3js.wl%richard.lewis@gold.ac.uk \
    --to=richardlewis@fastmail.co.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \


* 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


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).