From: Aaron Ecay <aaronecay@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: "W. Greenhouse" <wgreenhouse@riseup.net>, emacs-orgmode@gnu.org
Subject: Re: [Out-of-Thread] Re: [RFC] Org syntax (draft)
Date: Mon, 18 Mar 2013 23:47:56 -0400 [thread overview]
Message-ID: <87txo8vymr.fsf@gmail.com> (raw)
In-Reply-To: <B72CDC2B-72F6-43A8-AC70-E6E6295766EC@gmail.com> (Carsten Dominik's message of "Mon, 18 Mar 2013 20:19:42 +0100")
Hi Carsten,
Thank you for your very insightful thoughts. I would like to make one note.
2013ko martxoak 18an, Carsten Dominik-ek idatzi zuen:
> Now to the discussion with Z about additional emphasis definitions
> which he/she uses for custom highlighting of stuff. Right now this
> relies on modifying the emph-alist variable. However, for the purpose
> of in-buffer only highlighting, it is not necessary to go through
> parser-sensitive code. You can do this simply with additions to
> font-lock, for example using font-lock-add-keywords or something like
> this, see also Thorsten's post. If someone wants, I can provide an
> example for Z's case, and we could encapsulate such behavior into a
> little library in contrib, to make it easy to configure such behavior.
> Compromising the parser for this application is not necessary.
I use org to write articles which discuss words in foreign languages.
These need to be distinctively typeset (in italics), and sometimes need
to be set in a special font with coverage for exotic characters. I
would find it very useful to be able to define special emphasis
environments for these words. Using macros feels too much like writing
LaTeX (which I use org to avoid having to write directly, as much as
possible...)
I see the goal of the syntactic standardization as making it easier to
operate with non-emacs tools; as Nicolas said:
> My point of view is the following: Org (as a format) definition
> shouldn't depend on Emacs. It should be totally parseable by any
> language (which is not the case actually, since syntax relies on
> variables defined in Emacs). IOW, we should work to make it a real
> plain-text markup format.
Personally, I am OK with articles I have written for export never being
able to be read by non-emacs tools (as opposed to other uses of org as a
database/schedule/agenda, where the ability to access the information in
other programs/programming languages would be useful). I sympathize
with the goal of making the format accessible to other tools, but I also
think the ability to have within emacs additional flexibility
wrt. formatting (for both display and export) is worth preserving.
--
Aaron Ecay
next prev parent reply other threads:[~2013-03-19 3:48 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 [this message]
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
-- 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=87txo8vymr.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=carsten.dominik@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).