From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Syntax for macros
Date: Thu, 30 Jan 2014 18:22:18 +0100 [thread overview]
Message-ID: <87txclbd11.fsf@gmail.com> (raw)
In-Reply-To: 87y51x8kyr.fsf@alphaville.bos.redhat.com
Nick Dokos <ndokos@gmail.com> writes:
> "Sebastien Vauban" <sva-news@mygooglest.com>
> writes:
>
>>> There is also backwards compatibility to consider.
Not only that, probability of false positives matters
too. E.g. inserting text snippets in PicoLisp Wiki Syntax into an Org
file could easily cause errors given the frequent use of {}:
,-----------------------------------------------------------------------
| 1{Contrived Example}
|
| In /{picolisp-wiki-mode} braces are !{very} important, and in PicoLisp
| itself Database objects are identified like this:
|
| :{{36}}
|
| denotes Object 36.
|
| Here is a list of objects in the DB:
|
|
| *{
| -{{11}}
| -{{36}}
| -{{45}}
| }
`-----------------------------------------------------------------------
This might be contrived, but is actually not that exotic.
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-01-30 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 8:49 [RFC] Syntax for macros Sebastien Vauban
2014-01-29 9:25 ` Bastien
2014-01-30 10:29 ` Sebastien Vauban
2014-01-30 10:41 ` Bastien
2014-01-30 10:48 ` Sebastien Vauban
2014-01-30 14:08 ` Nick Dokos
2014-01-30 14:56 ` Sebastien Vauban
2014-01-30 16:59 ` Nick Dokos
2014-01-30 17:22 ` Thorsten Jolitz [this message]
2014-01-30 18:03 ` Bastien
2014-01-31 22:13 ` [PATCH] Font-lock: allow hiding of brackets surrounding macros Florian Beck
2014-02-01 0:22 ` Bastien
2014-02-05 10:14 ` Bastien
2014-02-05 13:07 ` Sebastien Vauban
2014-02-05 13:12 ` Bastien
2014-01-30 19:25 ` [RFC] Syntax for macros Florian Beck
2014-01-30 21:11 ` Thomas S. Dye
2014-01-30 18:24 ` Achim Gratz
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=87txclbd11.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).