emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Florian Beck <fb@miszellen.de>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [RFC] Syntax for macros
Date: Thu, 30 Jan 2014 11:11:09 -1000	[thread overview]
Message-ID: <m18utx9nv6.fsf@tsdye.com> (raw)
In-Reply-To: <52EAA72D.70405@miszellen.de> (Florian Beck's message of "Thu, 30 Jan 2014 20:25:33 +0100")

Florian Beck <fb@miszellen.de> writes:

> 3. Of course, since macros are only relevant when exporting, it should
> be easy to write an export filter that translates arbitrary chars to
> brackets.

I think this might be the way forward for Org mode users who don't like
the look of the current macro syntax.

Backwards compatibility is an issue for my work with Org mode. I'm happy
to track changes that result from enhanced capabilities, but unhappy to
track changes that are cosmetic, like this suggestion to change the
syntax for macros.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2014-01-30 21:11 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
2014-01-30 19:25               ` [RFC] Syntax for macros Florian Beck
2014-01-30 21:11                 ` Thomas S. Dye [this message]
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=m18utx9nv6.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fb@miszellen.de \
    --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).