From: Nick Dokos <nicholas.dokos@hp.com>
To: emacs-orgmode@gnu.org
Subject: Re: TeX-master: TeX-master is let-bound
Date: Mon, 29 Oct 2012 18:25:48 -0400 [thread overview]
Message-ID: <647.1351549548@alphaville> (raw)
In-Reply-To: Message from Christopher Schmidt <christopher@ch.ristopher.com> of "Mon, 29 Oct 2012 21:18:39 -0000." <87625tj7tb@ch.ristopher.com>
Christopher Schmidt <christopher@ch.ristopher.com> wrote:
> Nick Dokos <nicholas.dokos@hp.com> writes:
> > In any case, if you can get rid of the let-bind (or the need to muck
> > with TeX-master at all within org), without introducing a regression,
> > we are all ears.
>
> I think adding (require 'tex nil t) before the let form is a nice fix.
>
Not really: you end up pulling in auctex even if you are not going to
use it.
> IMO the situation ATM is pretty bad. If AUCTeX is not loaded pre export
> the missing variable definition breaks AUCTeX completely.
>
What missing variable definition? By the time the export is finished,
the let-bind is gone. There is no definition of TeX-master anywhere,
just as if you never had org loaded: why should auctex object to that?
So I don't understand why it would break: all the common scenarios that
I have tried work with no problem for me. I can load an org file, export to
latex, open the latex file (which loads auctex) and do auctex things to
it. I don't get any error. What exactly do I have to do in order to
break it?
Nick
next prev parent reply other threads:[~2012-10-29 22:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 16:48 TeX-master: TeX-master is let-bound Christopher Schmidt
2012-10-25 21:45 ` Suvayu Ali
2012-10-25 22:19 ` Christopher Schmidt
2012-10-26 6:51 ` Suvayu Ali
2012-10-26 8:43 ` Christopher Schmidt
2012-10-26 9:30 ` Christopher Witte
2012-10-26 11:41 ` Suvayu Ali
2012-10-26 15:34 ` Christopher Schmidt
[not found] ` <christopher@ch.ristopher.com>
2012-10-26 16:31 ` Nick Dokos
2012-10-29 21:18 ` Christopher Schmidt
2012-10-29 22:25 ` Nick Dokos [this message]
2012-10-29 22:57 ` Christopher Schmidt
2013-02-23 9:16 ` Bastien
2013-02-23 14:32 ` Christopher Schmidt
2013-03-02 15:11 ` Bastien
2012-11-01 14:50 ` Christopher Schmidt
2012-10-29 23:25 ` Nick Dokos
2012-10-30 7:52 ` Christopher Schmidt
2012-10-30 17:45 ` Nick Dokos
2012-10-30 19:01 ` Christopher Schmidt
2012-10-30 20:32 ` Sebastien Vauban
2012-10-30 20:54 ` Nick Dokos
2012-11-01 15:22 ` Nick Dokos
2013-01-24 19:25 ` Christopher Schmidt
2013-01-25 10:42 ` Bastien
2013-01-25 11:36 ` Christopher Schmidt
2013-01-26 13:54 ` Christopher Schmidt
2013-01-26 14:20 ` Bastien
2013-01-26 14:28 ` Christopher Schmidt
2013-01-26 15:35 ` Bastien
2013-01-26 16:23 ` Christopher Schmidt
2013-02-19 10:38 ` Christopher Schmidt
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=647.1351549548@alphaville \
--to=nicholas.dokos@hp.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).