emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Vladimir Nikishkin <lockywolf@gmail.com>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Wrong syntax in org-mode files with babel fragments in src blocks [9.2.6 (9.2.6-4-ge30905-elpaplus @ /home/lockywolf/.emacs.d/elpa/org-plus-contrib-20191021/)]
Date: Wed, 30 Oct 2019 10:16:04 +0800	[thread overview]
Message-ID: <CA+A2iZaiWpX4FRVS1+9OQ125w=mU8m3uzmw2_TNNCfMHOB3FVw@mail.gmail.com> (raw)
In-Reply-To: <xuu6sgnbld3w.fsf@ucl.ac.uk>

That's probably a working solution, but I still wonder why org 8
doesn't have this problem.

Thanks anyway.

ср, 30 окт. 2019 г. в 00:40, Fraga, Eric <e.fraga@ucl.ac.uk>:
>
> On Tuesday, 29 Oct 2019 at 23:50, Vladimir Nikishkin wrote:
> > The MWE would be the following:
> >
> > #+begin_src scheme
> > (display (< 1 3))
> > #+end_src
> >
> > In this example, if you put the point on the "<" symbol, it is
> > highlighted (fontified) together with the ")" following 3, which is
> > incorrect, since in general, "<" is not a paired entity. (I.e. is a
> > symbol "less" rather than an angular bracket.)
>
> I have the following 2 lines in my org-mode-hook to cater for this issue
> which arises when using source blocks.
>
>     (modify-syntax-entry ?< ".")
>     (modify-syntax-entry ?> ".")
>
> HTH
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-544-gd215c3



-- 
Yours sincerely, Vladimir Nikishkin

next prev parent reply	other threads:[~2019-10-30  2:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 15:50 Bug: Wrong syntax in org-mode files with babel fragments in src blocks [9.2.6 (9.2.6-4-ge30905-elpaplus @ /home/lockywolf/.emacs.d/elpa/org-plus-contrib-20191021/)] Vladimir Nikishkin
2019-10-29 16:37 ` John Kitchin
2019-10-29 16:40 ` Fraga, Eric
2019-10-30  2:16   ` Vladimir Nikishkin [this message]
2020-02-05  8:14   ` Bastien
2020-02-05  9:47     ` Fraga, Eric
2020-02-05 10:12       ` 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='CA+A2iZaiWpX4FRVS1+9OQ125w=mU8m3uzmw2_TNNCfMHOB3FVw@mail.gmail.com' \
    --to=lockywolf@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@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

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).