From: Greg Minshall <minshall@acm.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: non-space, paste, (???) character for inline results
Date: Wed, 31 Jan 2018 06:49:09 +0530 [thread overview]
Message-ID: <21575.1517361549@minshall-apollo.minshall.org> (raw)
In-Reply-To: Your message of "Tue, 30 Jan 2018 21:55:38 +0100." <87372nysl1.fsf@nicolasgoaziou.fr>
Nico,
ah, thanks!
not wanting to look gift horses, etc., but i've a question. if i
understand the change correctly
----
- (looking-at "\\<call_\\([^ \t\n[(]+\\)[([]"))
+ (looking-at "call_\\([^ \t\n[(]+\\)[([]"))
----
now something like "oncall_foo()" will be taken as "on" followed by the
inline results of call_foo(). is that right? (testing, seems to be.)
i worry that might be a bit too lenient. sometimes one might want
"oncall_foo()" to stay as "oncall_foo()". (that's why i was thinking of
some, hmm, "non-spacing break", like the string "{{{}}}", or, well,
almost anything, "\.", "\#", "#" -- maybe the cleanest? -- ...)
cheers, Greg
next prev parent reply other threads:[~2018-01-31 1:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 8:29 non-space, paste, (???) character for inline results Greg Minshall
2018-01-30 9:15 ` Nicolas Goaziou
2018-01-30 13:06 ` Greg Minshall
2018-01-30 20:55 ` Nicolas Goaziou
2018-01-31 1:19 ` Greg Minshall [this message]
2018-01-31 11:13 ` Nicolas Goaziou
2018-01-31 15:12 ` Greg Minshall
2018-01-31 16:19 ` Nicolas Goaziou
2018-01-31 17:41 ` Greg Minshall
2018-01-31 17:52 ` Kaushal Modi
2018-01-31 17:54 ` Kaushal Modi
2018-01-31 18:09 ` Nicolas Goaziou
2018-02-01 6:23 ` Greg Minshall
2018-02-03 14:01 ` Nicolas Goaziou
2018-02-03 14:27 ` Greg Minshall
2018-02-03 14:31 ` Nicolas Goaziou
2018-02-03 14:41 ` Greg Minshall
2018-02-03 23:33 ` Nicolas Goaziou
2018-02-05 23:15 ` Greg Minshall
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=21575.1517361549@minshall-apollo.minshall.org \
--to=minshall@acm.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).