From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: words starting with call_ confuse C-c C-c and export
Date: Sat, 14 Dec 2013 12:25:59 +0100 [thread overview]
Message-ID: <87k3f7ad2w.fsf@gmail.com> (raw)
In-Reply-To: <8761r14cjr.fsf@gmail.com> (Eric Schulte's message of "Fri, 06 Dec 2013 14:12:39 -0700")
Hello,
Eric Schulte <schulte.eric@gmail.com> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>> Just to be clear, I thought about making parens mandatory in inline
>> Babel call syntax. Underscore is overloaded already: underline,
>> subscript...
>>
>
> I'm open to this change.
In fact, they are already mandatory. The problem is different. Current
regexp is:
"\\([^\n]*?\\)call_\\([^()\n]+?\\)\\(\\[\\(.*?\\)\\]\\|\\(\\)\\)(\\([^\n]*?\\))\\(\\[\\(.*?\\)\\]\\)?"
In particular, name is \\([^()\n]+?\\), and can include whitespace
characters. Therefore "call_name (args)" is valid. Isn't it too much
permissive in the context of an Org (i.e. textual) document?
Also, couldn't we limit names to alphanumeric characters and, maybe,
some puctuation (e.g. hypen)?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-12-14 11:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 6:47 words starting with call_ confuse C-c C-c and export Daniel Clemente
2013-12-03 20:55 ` Nicolas Goaziou
2013-12-06 19:09 ` Eric Schulte
2013-12-06 19:46 ` Nicolas Goaziou
2013-12-06 21:12 ` Eric Schulte
2013-12-14 11:25 ` Nicolas Goaziou [this message]
2013-12-15 21:37 ` Eric Schulte
2013-12-15 22:43 ` Nicolas Goaziou
2013-12-16 15:12 ` Eric Schulte
2013-12-16 16:58 ` Nicolas Goaziou
2014-03-06 22:12 ` Eric Schulte
2014-03-10 14:28 ` Nicolas Goaziou
2014-03-10 14:44 ` Eric Schulte
2014-03-11 14:11 ` Nicolas Goaziou
2014-03-11 15:57 ` Eric Schulte
2014-03-11 20:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3f7ad2w.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.