From: Eric Schulte <schulte.eric@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: words starting with call_ confuse C-c C-c and export
Date: Mon, 10 Mar 2014 08:44:31 -0600 [thread overview]
Message-ID: <87fvmqkt9s.fsf@gmail.com> (raw)
In-Reply-To: <87r46a2kmw.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 10 Mar 2014 15:28:23 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>>> We're talking about function names, not free-form text, so limitations
>>> are understandable. For example, macro names only allow alphanumeric
>>> characters or hyphens and have to start with an alphabetic character.
>>
>> Having considered this, unless there are user objections I'd be happy
>> limiting function names to the same restricted alphabet as macro names.
>>
>> This would be a breaking change though, and should be mentioned as such
>> in the notes.
>
> Once you have settled for a regexp (do you want to include "/"
> character?), please let me know, I'll update org-element accordingly.
>
Is "/" allowed in macro names? I think the biggest benefit here is
unification between macro and function names. Is there a macro name
regexp which could be used directly (to ensure that these two stay
unified)? I don't see one, so I expect we'll want to add an
org-babel-function-name regexp along the lines of "[a-zA-Z0-9\-\/]+".
This would then be used in the following variables.
- org-babel-src-block-regexp
- org-babel-src-name-w-name-regexp
And the following functions should be updated to ensure that the name
only includes the allowed characters.
- org-babel-named-data-regexp-for-name
- org-babel-named-src-block-regexp-for-name
Does this sound about right?
>
> Regards,
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2014-03-10 14:46 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
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 [this message]
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
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=87fvmqkt9s.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).