emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Dynerman <emperordali@block-party.net>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>,
	"Glenn Morris" <rgm@gnu.org>,
	"David Dynerman" <emperordali@block-party.net>
Cc: 25132@debbugs.gnu.org
Subject: bug#25132: 26.0.50; emacs hangs when loading org file with python source blocks
Date: Wed, 07 Dec 2016 23:17:36 -0800	[thread overview]
Message-ID: <m260murisv.fsf__13130.6503586986$1481181530$gmane$org@block-party.net> (raw)
In-Reply-To: <4aa23451-b6cd-88b0-369e-99f6fe5f2175@gmail.com>

Dear Glenn + bug-gnu-emacs,

Did you try the steps to reproduce? Indeed Clément was right! The bug also reliably reproduces also with org 8.2.10, if you additionally set org-src-fontify-natively to t.

Please let me know if you need any more information for the bug report,
David

Clément Pit--Claudel <clement.pit@gmail.com> writes:

> On 2016-12-07 21:08, Glenn Morris wrote:
>> David Dynerman wrote:
>>> The bug does NOT occur with org 8.2.10.
>> 
>> Since that's the version included with Emacs, I'm confused as to why
>> you've been encouraged to report this to bug-gnu-emacs.
>
> I can reproduce the issue in emacs -Q on master; hence my suggestion to report it here.  Glenn, can you try running the following after downloading the attached file?
>
>    emacs -Q --eval '(setq debug-on-signal t org-src-fontify-natively t)' test.org 
>
> It hangs reproducibly for me.  No idea why the OP can't reproduce it (David, are you sure it doesn't occur with org 8.2.10? Could it be that org-src-fontify-natively isn't enabled by default in 8.2.10?)
>
> Clément.

  parent reply	other threads:[~2016-12-08  7:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2fulz4mjc.fsf@CIVIC-TV.local>
2016-12-08  2:08 ` bug#25132: 26.0.50; emacs hangs when loading org file with python source blocks Glenn Morris
     [not found] ` <qwa8c75g0r.fsf@fencepost.gnu.org>
2016-12-08  2:40   ` Clément Pit--Claudel
     [not found]   ` <4aa23451-b6cd-88b0-369e-99f6fe5f2175@gmail.com>
2016-12-08  7:17     ` David Dynerman [this message]
     [not found]     ` <m260murisv.fsf@block-party.net>
2017-01-07  6:38       ` npostavs
     [not found]       ` <87y3yn2x4j.fsf@users.sourceforge.net>
2017-01-07 21:20         ` npostavs
2017-01-19 16:25           ` Dmitry Gutov
2017-01-20  0:52             ` npostavs
     [not found]             ` <878tq6wo1p.fsf@users.sourceforge.net>
2017-01-20  2:22               ` Clément Pit--Claudel
     [not found]               ` <4674bf9b-38f0-8839-fadb-e9a719faf163@gmail.com>
2017-01-20  3:18                 ` npostavs
2017-01-23  3:53               ` Dmitry Gutov
     [not found]               ` <345079d3-9578-9ab9-1444-353843a70f8b@yandex.ru>
2017-01-24  3:36                 ` npostavs
     [not found]                 ` <874m0puo2a.fsf@users.sourceforge.net>
2017-01-29 16:05                   ` npostavs

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='m260murisv.fsf__13130.6503586986$1481181530$gmane$org@block-party.net' \
    --to=emperordali@block-party.net \
    --cc=25132@debbugs.gnu.org \
    --cc=clement.pit@gmail.com \
    --cc=rgm@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).