emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: 5f095f5 is the first bad commit (for my use case)
Date: Wed, 27 Feb 2013 09:44:32 +0100	[thread overview]
Message-ID: <86k3pu9mdr.fsf@somewhere.org> (raw)
In-Reply-To: 87hakzqlg4.fsf@gmail.com

Hello Nicolas,

Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> Since updating to latest Org this morning, I couldn't open anymore my file
>> ~/org/work.org.
>>
>> Symptom?  Org-mode gets loaded, but buffer remains blank, and Emacs is
>> (apparently) inflooping, with letting me stop it (with C-g).
>>
>> Solution?  Kill Emacs through the task manager, and bisect:
>>
>>   ╭────
>>   │ 5f095f59099e77eda5cf7cae64119f9f246c4c70 is the first bad commit
>>   │ commit 5f095f59099e77eda5cf7cae64119f9f246c4c70
>>   │ Author: Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>   │ Date:   Sun Feb 10 00:07:48 2013 +0100
>>   │
>>   │     Fontify latex, entities and sub/superscript again
>>   ╰────
>>
>> Now, having my Git tip on commit 3f95d81, everything's OK. I can work again,
>> but the most difficult problem is that I don't see how to debug further the
>> above problem.
>>
>> Any idea why this fails?
>
> Probably an infloop, as you suggest. It would be great if you could
> provide an ECM (even not "M") for that problem. You can send it through
> private mail if you want.
>
> Also, what's your value for `org-highlight-latex-and-related'?

You've directly put me on the right track: some (untested) code I added just
before leaving on vacation...

--8<---------------cut here---------------start------------->8---
  ;; highlight LaTeX and related syntax
  (setq org-highlight-latex-and-related
        '('latex
          'script
          'entities))
--8<---------------cut here---------------end--------------->8---

This is obviously wrong (shame on me!), but has the interesting effect of
causing an infloop on opening Org files...

Thanks!

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2013-02-27  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 10:45 5f095f5 is the first bad commit (for my use case) Sebastien Vauban
2013-02-26 13:00 ` Nicolas Goaziou
2013-02-27  8:44   ` Sebastien Vauban [this message]
2013-02-27  9:01     ` Nicolas Goaziou
2013-02-27 10:43       ` Sebastien Vauban
2013-02-27 15:25         ` Nicolas Goaziou
2013-02-27 19:52         ` Aaron Ecay
2013-02-28  8:18           ` Sebastien Vauban
2013-02-26 13:43 ` Bastien

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=86k3pu9mdr.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).