emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: "Andreas Gösele" <goesele@hfph.mwn.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: problem with latex export
Date: Wed, 11 Nov 2009 02:25:00 +0100	[thread overview]
Message-ID: <878wed26qb.fsf@gmx.de> (raw)
In-Reply-To: <loom.20091111T003318-635@post.gmane.org> ("Andreas Gösele"'s message of "Tue, 10 Nov 2009 23:42:53 +0000 (UTC)")

Andreas Gösele <goesele@hfph.mwn.de> writes:
> Hi Sebastian!
>
> Sebastian Rose <sebastian_rose <at> gmx.de> writes:
>> > I have the following problem: If I start emacs (22.2.1) or xemacs
>> > (21.4.21) normally I cannot export to latex (or pdf, which goes
>> > through latex). The process starts, but then hangs. In XEmacs the last
>> > thing I see is "untabify done" and then a small window with a process
>> > bar saying "fontifying org-mode-tmp...". But there is no progress and
>> > I have to quit. (There's a "Stop" button, but that doesn't work.) In
>> > Emacs I just see the first time I try it: "Loading tabify...done" and
>> > then nothing happens, again I have to quit. The second time I try it I
>> > only get: "Exporting to LaTeX...", again everything hangs.
>> >
>> > If I start without the init files (-q) and then load my init files by
>> > hand everthing works. (I did this, to see whether something in my init
>> > files causes the problems. But if everthing works if I load them
>> > later, I guess it's not a problem of my init files.)
>> >
>> > Org-mode is version 6.21b


So `M-x org-version' gives you "Org-mode 6.32trans ..."?


>> As I cannot reproduce this, I suggest updating to the current
>> git-version.
>
> I did, but the problem continues.


OK. Then we need more precise information.

1. The smallest possible file that's needed to reproduce the error.
2. If possible, execute `M-x org-submit-bug-report' and confirm to send
   your Org-mode setup. In the following screen, copy your setup and
   append it your email. Make sure to delete all private data in it.


That way we will be able to reproduce the error in most cases.


> I have BTW to make a small correction to my last post: There is a small
> difference in the case of emacs and xemacs: Having started emacs without the
> init-files I then can open and evaluate my init.el and custom.el as a whole
> without causing problems. In the case of xemacs that's true only for init.el. If
> I evaluate custom.el as a whole buffer the problems returns. But if a evaluate
> the (only four) expressions in it one after the other - no problem.
>  
> Thanks again
>
> Andreas Gösele



  Sebastian

  reply	other threads:[~2009-11-11  1:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 15:34 problem with latex export Andreas Goesele
2009-11-10 21:48 ` Sebastian Rose
2009-11-10 23:42   ` Andreas Gösele
2009-11-11  1:25     ` Sebastian Rose [this message]
2009-11-11 20:49       ` Andreas Gösele

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=878wed26qb.fsf@gmx.de \
    --to=sebastian_rose@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=goesele@hfph.mwn.de \
    /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).