From: Tom Gillespie <tgbugs@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Tim Cross <theophilusx@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org mode and Emacs (was: Convert README.org to plain text README while installing package)
Date: Thu, 16 Jun 2022 03:05:11 -0700 [thread overview]
Message-ID: <CA+G3_PPGLV595Kf+E=A1NO5QQgVOnUK0h--TyBDG0rAXfBb_ug@mail.gmail.com> (raw)
In-Reply-To: <87h74mv56b.fsf@localhost>
Having read the whole thread now: oof. Thank you Ihor for shepherding
that and for the performance improvements!
With regard to the key-bindings straw man. I guess I'm a bit of an
outsider on this one, because I started writing org documents by just
typing them in and only over time learning some of the bindings. Maybe
having an org-markup-mode or something like that would be a way to
provide a sandbox for the +recalcitrants+ newcomers? It might also be
a nice way to a/b test them on whether the Emacs editing commands
really are as good as they think they are (said the evil-mode user).
With regard to ... everything else. I guess at this point it is
unsurprising that (for lack of a better term) the uninitiated in the
dark corners of org syntax frequently think that syntactic extensions
are advisable, skipping over the consideration of possible.
Given the opportunities that seem to be lurking in the thread, it
seems like it would be good to have some examples of how the
e.g. texinfo semantic markup could (or could not) be implemented using
existing org syntax. The suggestion to use custom link types seems
very practical. It requires no new syntax, and is basically fully
extensible for semantic markup needs.
I say this having recently spent time reworking the paragraph grammar
and the lexer needed to enable it in laundry for the 3rd (or is it
4th?) time. Say it with me: No new syntactic forms! We have more than
enough syntax to enable all the extensibility that pretty much anyone
will ever need (we just have to document how to use it).
In-document extensibility of link types might be possible if we get my
regularized keyword syntax implemented, if that were done then all the
configuration could in-principle live in a setup file (I have a
response on the syntax thread drafted, will try to get back to it).
Nesting markup inside code or verbatim seems more difficult because
they are intentionally terminal. I am also unfamiliar with texinfo so
will be of no help with the examples, but I do look forward to them.
Best!
Tom
next prev parent reply other threads:[~2022-06-16 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YpuV9DKe9kzNt5np@ACM>
[not found] ` <871qw31ois.fsf@yahoo.com>
[not found] ` <8735gj4ceo.fsf@gnu.org>
[not found] ` <87ee038ipt.fsf@gmx.de>
[not found] ` <87o7z61v59.fsf@gmail.com>
[not found] ` <Yp3l+rjJ0mAIcVZJ@ACM>
[not found] ` <87bkv527p5.fsf@gmail.com>
[not found] ` <835yld93w7.fsf@gnu.org>
[not found] ` <877d5t0yrn.fsf@gmail.com>
[not found] ` <Yp92eI2pEuc/gQu4@ACM>
[not found] ` <jwvtu8wbbjb.fsf-monnier+emacs@gnu.org>
[not found] ` <87r140yuof.fsf@gmail.com>
[not found] ` <E1nzQh5-0001OB-22@fencepost.gnu.org>
[not found] ` <875yl9e7zm.fsf@gmail.com>
[not found] ` <83czfh12kp.fsf@gnu.org>
[not found] ` <87pmjhghu2.fsf@localhost>
[not found] ` <835yl910gp.fsf@gnu.org>
[not found] ` <87wndndbhq.fsf@gmail.com>
[not found] ` <83bkuzznws.fsf@gnu.org>
[not found] ` <877d5mqmkh.fsf@localhost>
[not found] ` <E1o0sgC-0000jg-U3@fencepost.gnu.org>
2022-06-14 0:43 ` Org mode and Emacs (was: Convert README.org to plain text README while installing package) Ihor Radchenko
2022-06-15 5:58 ` Ihor Radchenko
2022-06-16 10:05 ` Tom Gillespie [this message]
2022-06-18 10:56 ` Simplified Org mode for newcomer Emacs veterans (was: Org mode and Emacs (was: Convert README.org to plain text README while installing package)) Ihor Radchenko
2022-06-18 22:04 ` Tim Cross
2022-06-19 8:49 ` Ihor Radchenko
2022-06-17 6:42 ` Org syntax compatibility with texinfo syntax " Ihor Radchenko
[not found] ` <E1o0Bgv-0008SK-Gs@fencepost.gnu.org>
[not found] ` <874k0qbrhe.fsf@localhost>
[not found] ` <E1o0WEH-0004wk-Hw@fencepost.gnu.org>
[not found] ` <87v8t3wfgd.fsf@localhost>
[not found] ` <87zgifxt48.fsf@gmail.com>
2022-06-15 6:13 ` Cusom special block export, similar org org-link :export parameter (was: Org mode and Emacs) Ihor Radchenko
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='CA+G3_PPGLV595Kf+E=A1NO5QQgVOnUK0h--TyBDG0rAXfBb_ug@mail.gmail.com' \
--to=tgbugs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.com \
--cc=yantar92@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).