emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Tue, 11 Mar 2014 21:49:33 +0100	[thread overview]
Message-ID: <87iork1mw2.fsf@gmail.com> (raw)
In-Reply-To: <87iorkn2x2.fsf@gmail.com> (Eric Schulte's message of "Tue, 11 Mar 2014 09:57:45 -0600")

Eric Schulte <schulte.eric@gmail.com> writes:

>> Note there is no limitation on the contents of NAME keywords. Unless the
>> same limitation propagates to those (but should it?), Babel calls will
>> be ignored if forbidden characters are used.
>>
>
> I think it is more important that code block names resemble data names
> than macro names, so I'm afraid that I'm back to my original position of
> preferring to keep as many characters as possible in function names.

You can still have forbidden characters even with the current permissive
regexp:

  #+NAME: how do you call me?

is a valid NAME value but not a valid Babel name.

Another option is, as noted before, to restrict NAME values accordingly.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2014-03-11 20:49 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
2014-03-11 14:11                         ` Nicolas Goaziou
2014-03-11 15:57                           ` Eric Schulte
2014-03-11 20:49                             ` Nicolas Goaziou [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=87iork1mw2.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 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).