From: Sebastian Gimeno <changimeno@gmail.com>
To: Jack Kamm <jackkamm@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode fontification error in #<buffer myfile.org> in python and ipython source blocks
Date: Mon, 2 Nov 2020 00:43:35 +0100 [thread overview]
Message-ID: <CAPUJosBsnjo1ZRc5ErQi+a4Or30Kf5rKFvwHn_BU7xeABj2QBg@mail.gmail.com> (raw)
In-Reply-To: <87d00wq18o.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
Hi Jack,
thanks for replying!
The error does not happen using "emacs -q" (built-in package: org 9.3). I
haven't tried with the git version yet. i will and let you know.
Cheers,
Sebastian
On Sun, Nov 1, 2020 at 9:19 PM Jack Kamm <jackkamm@gmail.com> wrote:
> Hi Sebastian --
>
> > I am having problems with the fontification of python and ipython source
> > blocks when the code contains curly brackets "{}" (other course blocks
> are
> > ok). For instance, the following snippet
> >
> > #+BEGIN_SRC python :results drawer
> > import matplotlib.pyplot as plt
> > plt.plot([1,2,3])
> > plt.show()
> > a=1
> > print("a={}".format{a})
> > #+END_SRC
> >
> > does not fontify correctly in either python or ipython source blocks.
> >
> > As a consequence, when exporting the org file to HTML (C-c C-e h h), it
> > fails with the following message:
> >
> > font-lock-fontify-keywords-region: Invalid function: #<subr progn>
>
> I'm unable to reproduce this behavior on emacs 27.1 and git
> master. Fontification and export work fine with this code block for me.
>
> Does the error still happen when you use emacs -q ? Or if you use git
> master?
>
> Jack
>
>
[-- Attachment #2: Type: text/html, Size: 1726 bytes --]
next prev parent reply other threads:[~2020-11-01 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 2:01 Org mode fontification error in #<buffer myfile.org> in python and ipython source blocks Sebastian Gimeno
2020-11-01 20:19 ` Jack Kamm
2020-11-01 23:43 ` Sebastian Gimeno [this message]
2020-11-02 0:41 ` Sebastian Gimeno
2020-11-03 5:49 ` stardiviner
2020-11-03 9:53 ` Sebastian Gimeno
2020-11-03 15:55 ` John Kitchin
2020-11-04 3:10 ` Kyle Meyer
2020-11-04 3:22 ` stardiviner
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=CAPUJosBsnjo1ZRc5ErQi+a4Or30Kf5rKFvwHn_BU7xeABj2QBg@mail.gmail.com \
--to=changimeno@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jackkamm@gmail.com \
/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).