From: Samuel Wales <samologist@gmail.com>
To: "W. Greenhouse" <wgreenhouse@riseup.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Out-of-Thread] Re: [RFC] Org syntax (draft)
Date: Mon, 18 Mar 2013 21:07:51 -0700 [thread overview]
Message-ID: <CAJcAo8u7BDntvGm5Ohhs=45GFQ597+mK4xTzBPutQG+v8NqtMw@mail.gmail.com> (raw)
In-Reply-To: <87mwu0n371.fsf@riseup.net>
On 3/18/13, W. Greenhouse <wgreenhouse@riseup.net> wrote:
> Perhaps a compromise could be reached on variables such as
> `org-emphasis-alist' and others possibly slated for the defconst
> treatment: instead of doing that, let's consider keeping them
> customizable but include the default values in the Org format
> specification. Org users who are never using Org outside of Emacs will
I think this is a good idea.
===
Here is a brainstorm involving an old idea:
If the problem is external parsers vs. flexibility, I wonder if it
might be possible to have zeltak's cake and eat it too. This applies
to more than just coloring in the buffer transiently.
In the case of color, $[face :foreground "red"]we can actually color
something in a way that external parsers can understand and export
backends can support$[end]. To some degree, at least.
We can do so $[face :foreground "yellow" :underline t]using a syntax
that will work for other features also and can be upgraded$[end]. Not
only for faces. Just change "face" to the name of your feature.
Every feature that uses the $[] syntax starts out as experimental or
in the user's .emacs. Then after we experiment with a feature and
decide it's worth being a default, we add it to the RFC and no longer
call it Emacs-only.
One big win is that Emacs and external parsers need only understand
the $[] notation, and do not need to come up with new parsing
techniques for syntax, because it is a Lisp lambda list. Even the
user can do this.
All sorts of things then come for free. For example, quoting,
escaping, nesting, pretty-printing, exporting, hiding, making the $[]
parts look human-friendly by making them invisible or collapsing them,
and so on. They are all available for new features that need syntax,
including user-defined ones.
A possibility for what it's worth.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. ANYBODY
can get it. There is NO hope without action. This means YOU.
next prev parent reply other threads:[~2013-03-19 4:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 23:02 [Out-of-Thread] Re: [RFC] Org syntax (draft) zeltak
2013-03-18 6:08 ` Carsten Dominik
2013-03-18 10:48 ` Thorsten Jolitz
2013-03-18 13:33 ` zeltak
2013-03-18 15:21 ` W. Greenhouse
2013-03-18 16:05 ` Marcin Borkowski
2013-03-18 19:19 ` Carsten Dominik
2013-03-18 21:24 ` Rasmus
2013-03-19 3:47 ` Aaron Ecay
2013-03-19 9:49 ` Nicolas Richard
2013-03-21 21:36 ` Nicolas Goaziou
2013-04-12 6:23 ` Bastien
2013-04-12 6:23 ` Bastien
2013-03-19 4:07 ` Samuel Wales [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-20 17:47 zeltak
2013-03-07 20:37 Nicolas Goaziou
2013-03-09 23:16 ` Achim Gratz
2013-03-09 23:49 ` Nicolas Goaziou
2013-03-10 4:35 ` Jambunathan K
2013-03-10 7:08 ` Nicolas Goaziou
2013-03-10 10:14 ` Bastien
2013-03-10 15:44 ` Jambunathan K
2013-03-14 16:58 ` Eric S Fraga
2013-03-14 18:26 ` Jambunathan K
2013-03-14 18:51 ` David Engster
2013-03-14 19:03 ` [Out-of-Thread] " Jambunathan K
2013-03-14 19:15 ` David Engster
2013-03-14 19:23 ` Jambunathan K
2013-03-14 19:29 ` David Engster
2013-03-14 19:52 ` Jambunathan K
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='CAJcAo8u7BDntvGm5Ohhs=45GFQ597+mK4xTzBPutQG+v8NqtMw@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wgreenhouse@riseup.net \
/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).