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: Fri, 06 Dec 2013 14:12:39 -0700 [thread overview]
Message-ID: <8761r14cjr.fsf@gmail.com> (raw)
In-Reply-To: 87wqjhu5i1.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>>> We may tweak `org-babel-inline-lob-one-liner-regexp' in order to make it
>>> harder to trigger it unwillingly.
>>>
>>
>> The trade-off here is between raising an error when e.g., a like
>> matching the call line syntax has a problem or failing silently. The
>> former is preferable in the case where you intend the syntax to be a
>> call and you *do* want to know if there is a problem, and the latter is
>> preferable if you aren't trying to issue a call and just stumbled upon
>> the syntax.
>>
>> I'm open to either solution, it's just a question of which use case is
>> more important and which failure condition is more onerous.
>
> 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.
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2013-12-07 2:32 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 [this message]
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
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=8761r14cjr.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).