From: Bastien <bzg@gnu.org>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Syntax for macros
Date: Thu, 30 Jan 2014 19:03:07 +0100 [thread overview]
Message-ID: <87ha8lgxes.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87y51x8kyr.fsf@alphaville.bos.redhat.com> (Nick Dokos's message of "Thu, 30 Jan 2014 11:59:08 -0500")
Nick Dokos <ndokos@gmail.com> writes:
> No: I'm saying that if this change is implemented, {{{foo}}} should be
> deprecated (probably raising a deprecation warning when encountered) and
> that both {{foo}} and {{{foo}}} should work identically, at least until
> the next major release (we can debate whether that's 8.3 or 8.4 or
> 9.0). At that point and forever after, the old syntax starts raising
> errors instead of warnings.
Agreed. Also, the whole issue is not that important IMO.
If the {{{...}}} are visually annoying, we can as well rely
on text properties to hide them and on faces to display
them in a different way (as we do already.)
--
Bastien
next prev parent reply other threads:[~2014-01-30 18:03 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
2014-01-30 18:03 ` Bastien [this message]
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=87ha8lgxes.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@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).