emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: inconsistent escaping of coderef regexp
Date: Mon, 05 Apr 2021 01:12:39 +0200	[thread overview]
Message-ID: <877dlhod94.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CA+G3_PO+srFr4c5JwSOrn=P=F3HnLeSXB6S_r+xAqQAXPVOBcA@mail.gmail.com> (Tom Gillespie's message of "Sun, 4 Apr 2021 15:01:42 -0700")

Hello,

Tom Gillespie <tgbugs@gmail.com> writes:

>     After a bit of investigation I understand the issue better now.
> There are two problems here. One is an easy single line change,
> the other is a deeper issue, which is that it is impossible for the
> user to specify their own coderef regexp that can be used in both
> cases. No matter what change we make we are likely to break
> existing org files if users relied on one behavior and not the other.

[...]

> If we want a temporary fix, a patch is attached, but I would suggest
> against changing the behavior right now and instead work toward
> a new, more consistent system using header args.

If possible, I'd like not to conflate current issue with switches
deprecation, which needs to be discussed separately.

What do you mean by "it is impossible for the user to specify their own
coderef regexp that can be used in both cases"? In particular, what is
a coderef regexp in this context? I know about coderef format, but
I don't think users are supposed to provide a regexp here.

Regards,
-- 
Nicolas Goaziou


  reply	other threads:[~2021-04-04 23:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 20:33 Bug: inconsistent escaping of coderef regexp Tom Gillespie
2021-04-01 15:45 ` Nicolas Goaziou
2021-04-01 16:09   ` Timothy
2021-04-04 22:01   ` Tom Gillespie
2021-04-04 23:12     ` Nicolas Goaziou [this message]
2021-04-05  5:22       ` Tom Gillespie
2021-04-05  7:42         ` Tom Gillespie
2021-04-07 17:58         ` Nicolas Goaziou
2021-04-07 19:44           ` Tom Gillespie
2021-04-09 22:19             ` Nicolas Goaziou

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=877dlhod94.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=tgbugs@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).