emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Sebastien Vauban
	<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [PATCH] Font-lock: allow hiding of brackets surrounding macros
Date: Wed, 05 Feb 2014 14:12:03 +0100	[thread overview]
Message-ID: <87ob2lbt5o.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86mwi5btdb.fsf@somewhere.org> (Sebastien Vauban's message of	"Wed, 05 Feb 2014 14:07:28 +0100")



Hi Sébastien,

"Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:

> I think that I would have left one pair of {} visible around macro calls
> (for making it clear that it's something special, even if we can play
> with the face `org-macro');

Playing with the face is the right thing to do I guess.

-- 
 Bastien

  reply	other threads:[~2014-02-05 13:12 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
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 [this message]
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=87ob2lbt5o.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.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).