* 5f095f5 is the first bad commit (for my use case)
@ 2013-02-26 10:45 Sebastien Vauban
2013-02-26 13:00 ` Nicolas Goaziou
2013-02-26 13:43 ` Bastien
0 siblings, 2 replies; 9+ messages in thread
From: Sebastien Vauban @ 2013-02-26 10:45 UTC (permalink / raw)
To: emacs-orgmode-mXXj517/zsQ
Hello,
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?
Best regards,
Seb
--
Sebastien Vauban
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 5f095f5 is the first bad commit (for my use case)
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
2013-02-26 13:43 ` Bastien
1 sibling, 1 reply; 9+ messages in thread
From: Nicolas Goaziou @ 2013-02-26 13:00 UTC (permalink / raw)
To: Sebastien Vauban; +Cc: public-emacs-orgmode-mXXj517/zsQ
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 5f095f5 is the first bad commit (for my use case)
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-26 13:43 ` Bastien
1 sibling, 0 replies; 9+ messages in thread
From: Bastien @ 2013-02-26 13:43 UTC (permalink / raw)
To: Sebastien Vauban; +Cc: public-emacs-orgmode-mXXj517/zsQ
Hi Sébastien,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> 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.
Is this with Emacs/24.2.91 on windows-nt?
Do you have this error with emacs -Q?
--
Bastien
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 5f095f5 is the first bad commit (for my use case)
2013-02-26 13:00 ` Nicolas Goaziou
@ 2013-02-27 8:44 ` Sebastien Vauban
2013-02-27 9:01 ` Nicolas Goaziou
0 siblings, 1 reply; 9+ messages in thread
From: Sebastien Vauban @ 2013-02-27 8:44 UTC (permalink / raw)
To: emacs-orgmode-mXXj517/zsQ
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 5f095f5 is the first bad commit (for my use case)
2013-02-27 8:44 ` Sebastien Vauban
@ 2013-02-27 9:01 ` Nicolas Goaziou
2013-02-27 10:43 ` Sebastien Vauban
0 siblings, 1 reply; 9+ messages in thread
From: Nicolas Goaziou @ 2013-02-27 9:01 UTC (permalink / raw)
To: Sebastien Vauban; +Cc: public-emacs-orgmode-mXXj517/zsQ
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> You've directly put me on the right track: some (untested) code I added just
> before leaving on vacation...
>
> ;; highlight LaTeX and related syntax
> (setq org-highlight-latex-and-related
> '('latex
> 'script
> 'entities))
>
> This is obviously wrong (shame on me!), but has the interesting effect of
> causing an infloop on opening Org files...
I fixed the infloop. Thank you.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 5f095f5 is the first bad commit (for my use case)
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
0 siblings, 2 replies; 9+ messages in thread
From: Sebastien Vauban @ 2013-02-27 10:43 UTC (permalink / raw)
To: emacs-orgmode-mXXj517/zsQ
Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> You've directly put me on the right track: some (untested) code I added
>> just before leaving on vacation...
>>
>> ;; highlight LaTeX and related syntax
>> (setq org-highlight-latex-and-related
>> '('latex
>> 'script
>> 'entities))
>>
>> This is obviously wrong (shame on me!), but has the interesting effect of
>> causing an infloop on opening Org files...
>
> I fixed the infloop. Thank you.
Thanks!
Do you know if there was a way out -- other than killing Emacs -- in such a
case where `C-g' is not working?
Best regards,
Seb
--
Sebastien Vauban
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 5f095f5 is the first bad commit (for my use case)
2013-02-27 10:43 ` Sebastien Vauban
@ 2013-02-27 15:25 ` Nicolas Goaziou
2013-02-27 19:52 ` Aaron Ecay
1 sibling, 0 replies; 9+ messages in thread
From: Nicolas Goaziou @ 2013-02-27 15:25 UTC (permalink / raw)
To: Sebastien Vauban; +Cc: public-emacs-orgmode-mXXj517/zsQ
> Do you know if there was a way out -- other than killing Emacs -- in such a
> case where `C-g' is not working?
None that I can think of.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 5f095f5 is the first bad commit (for my use case)
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
1 sibling, 1 reply; 9+ messages in thread
From: Aaron Ecay @ 2013-02-27 19:52 UTC (permalink / raw)
To: Sebastien Vauban, emacs-orgmode
2013ko otsailak 27an, Sebastien Vauban-ek idatzi zuen:
>
> Do you know if there was a way out -- other than killing Emacs -- in such a
> case where `C-g' is not working?
If you are on Linux (or OS X, I suppose), you can sometimes break an
infloop by sending emacs the SIGUSR2 signal (in the shell, “kill -USR2
`pidof emacs`”). This also generates a backtrace in the lisp debugger,
which is useful for debugging. See C-h v debug-on-event .
--
Aaron Ecay
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 5f095f5 is the first bad commit (for my use case)
2013-02-27 19:52 ` Aaron Ecay
@ 2013-02-28 8:18 ` Sebastien Vauban
0 siblings, 0 replies; 9+ messages in thread
From: Sebastien Vauban @ 2013-02-28 8:18 UTC (permalink / raw)
To: emacs-orgmode-mXXj517/zsQ
Hi Aaron,
Aaron Ecay wrote:
> 2013ko otsailak 27an, Sebastien Vauban-ek idatzi zuen:
>>
>> Do you know if there was a way out -- other than killing Emacs -- in such a
>> case where `C-g' is not working?
>
> If you are on Linux (or OS X, I suppose), you can sometimes break an
> infloop by sending emacs the SIGUSR2 signal (in the shell, “kill -USR2
> `pidof emacs`”). This also generates a backtrace in the lisp debugger,
> which is useful for debugging. See C-h v debug-on-event .
Thanks for the info!
Best regards,
Seb
--
Sebastien Vauban
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2013-02-28 8:18 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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).