From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: URGENT Need help fixing beamer exporting, can someone jump on IRC?
Date: Tue, 5 Mar 2013 16:44:34 +0100 [thread overview]
Message-ID: <20130305154434.GM7544@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <CAFniQ7Xq-UHVmveh_Doq9x4rkUhBnQAVJH36HwmyaFRBOeJAsA@mail.gmail.com>
Hi James,
On Tue, Mar 05, 2013 at 11:28:35PM +0800, James Harkins wrote:
> I had been using C-c C-x ! to reload org after doing a "make" but this
> turned out to mess things up pretty badly. I could get reasonable
> behavior only by quitting emacs and restarting it. I don't know if
> that should be considered a bug or not. Perhaps I don't understand
> what C-c C-x ! is supposed to do? Tonight at least, it was totally
> unreliable.
org-reload is there for convenience, quite often a proper emacs restart
is indeed required to get a consistent Org instance.
That said, I have noticed something odd about the new exporter and
org-reload. I think with the new exporter after doing org-reload, org
related config is not reloaded properly. This borks the Org instance.
This is more visible when using the Beamer backend since it requires
customisation of org-latex-classes by the user. One of these days, I'll
try to come up with a proper recipe to reproduce this.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-03-05 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 15:18 URGENT Need help fixing beamer exporting, can someone jump on IRC? James Harkins
2013-03-05 15:28 ` James Harkins
2013-03-05 15:42 ` Achim Gratz
2013-03-05 15:44 ` Suvayu Ali [this message]
2013-03-05 18:26 ` Achim Gratz
2013-03-05 20:26 ` [Bug] beamer backend and org-reload Suvayu Ali
2013-03-05 20:50 ` Achim Gratz
2013-03-05 22:26 ` Suvayu Ali
2013-03-05 23:29 ` Nicolas Goaziou
2013-03-06 12:10 ` Suvayu Ali
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=20130305154434.GM7544@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@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).