emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Bastien <bzg@gnu.org>
Cc: Vladimir Nikishkin <lockywolf@gmail.com>,
	"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, 5 Feb 2020 09:47:21 +0000	[thread overview]
Message-ID: <xuu6tv45mkm0.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87ftfpbgcl.fsf@gnu.org> (Bastien's message of "Wed, 05 Feb 2020 09:14:50 +0100")

On Wednesday,  5 Feb 2020 at 09:14, Bastien wrote:

[...]

> Org-mode sets:
>
>   (modify-syntax-entry ?< "(>")
>   (modify-syntax-entry ?> ")<")
>
> should we adapt Org's default syntax?

Difficult to judge but my gut feeling would be to leave as is.  My use
case involves significant amount of coding, where < and > are logical
operators.  However, for many, these may make more sense as brackets.

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.2-199-ga557cf

  reply	other threads:[~2020-02-05  9:47 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
2020-02-05  8:14   ` Bastien
2020-02-05  9:47     ` Fraga, Eric [this message]
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=xuu6tv45mkm0.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=lockywolf@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).