From: Marco Wahl <marcowahlsoft@gmail.com>
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Parens matching off in babel code block
Date: Fri, 03 May 2019 10:20:20 +0200 [thread overview]
Message-ID: <84ftpwne4b.fsf@gmail.com> (raw)
In-Reply-To: <87imusbkpk.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 02 May 2019 23:38:47 +0200")
Hi,
>> Using < and > as parenthesis in Org is questionable, I think.
>
> In Org syntax, < and > often come in pair (timestamps, some links,
> targets, radio targets). There is at least some interest in the current
> behaviour.
Yes, okay.
>> Also this behavior is not documented AFAICT.
>
> I don't think you can document every single detail. Even if it was
> possible, it wouldn't be desirable.
Agreed. My statement was thought as a pointer to the possibility to
drop the <>-parenthesis-feature without touching the documentation.
>> What about removing this special? Or does anyone enjoy this behavior?
>
> This needs to be carefully tested and weighted.
Yes, agreed.
Currently I run Org mode without the <> parenthesis using the patch:
modified lisp/org.el
- (modify-syntax-entry ?< "(>")
- (modify-syntax-entry ?> ")<")
+ ;; (modify-syntax-entry ?< "(>")
+ ;; (modify-syntax-entry ?> ")<")
Up to now I don't miss the <> parenthesis. But this is just me.
Ciao,
--
Marco
prev parent reply other threads:[~2019-05-03 8:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 2:56 Parens matching off in babel code block Lawrence Bottorff
2019-05-02 15:35 ` Berry, Charles
2019-05-02 16:01 ` Lawrence Bottorff
2019-05-02 20:11 ` Bruno BARBIER
2019-05-02 20:28 ` Marco Wahl
2019-05-02 21:38 ` Nicolas Goaziou
2019-05-03 2:11 ` Lawrence Bottorff
2019-05-03 9:23 ` Fraga, Eric
2019-05-04 12:54 ` John Kitchin
2019-05-05 15:02 ` Marco Wahl
2019-05-03 8:20 ` Marco Wahl [this message]
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=84ftpwne4b.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--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
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).