emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: 5f095f5 is the first bad commit (for my use case)
Date: Tue, 26 Feb 2013 14:00:27 +0100	[thread overview]
Message-ID: <87hakzqlg4.fsf@gmail.com> (raw)
In-Reply-To: <86hakzz746.fsf@somewhere.org> (Sebastien Vauban's message of "Tue, 26 Feb 2013 11:45:13 +0100")



Hello,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> 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
>   │
>   │     * lisp/org-faces.el (org-latex-and-related): Renamed from
>   │       `org-latex-and-export-specials', which wasn't appropriate anymore.
>   │     * lisp/org.el (org-highlight-latex-and-related,
>   │       org-latex-and-related-regexp): New variables.
>   │     (org-compute-latex-and-related-regexp, org-do-latex-and-related): New
>   │     function, revived from a previous commit.
>   │     (org-set-regexps-and-options, org-set-font-lock-defaults): Use new
>   │     functions.
>   ╰────
>
> 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'?


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-02-26 13:11 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 [this message]
2013-02-27  8:44   ` Sebastien Vauban
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=87hakzqlg4.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.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).