emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <tecosaur@gmail.com>
To: Russell Adams <RLAdams@AdamsInfoServ.Com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal
Date: Tue, 07 Dec 2021 02:47:28 +0800	[thread overview]
Message-ID: <87o85to8wh.fsf@gmail.com> (raw)
In-Reply-To: <Ya5Zplu/GsY7toqr@maokai>

[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]

Hi Russell,

I have a few comments on your comments :)

> These kind of issues snowball because we are also indirectly asking
> for our coders and maintainers to consider those external tools while
> continuing to support Org.

As I read it, considering other tools was just in the respect of indicating what
degree of support different tools have for Org as defined by org-mode. Not
changing anything we do based on those tools.

> How many syntax documents are we supposed to maintain outside of the working
> implementation in Emacs and the manual?

Just the one. I have some ideas on this that need to be written up, but I see
this more as polishing our syntax specification such that it’s is more
approachable for someone interested in supporting Org. IMO this leads to a
syntax document which is just better, period.

> The topic of software freedom comes up because by definition, other
> tools are outside of Emacs and may be non-free. It’s important to
> consider, but isn’t a reason to not discuss features. The key is our
> volunteers should not be required to code features for non-free tools
> outside of Emacs.

I don’t think anybody has proposed this. Personally I’m not even sure how we
went from making the website/docs more approachable to supporting 3rd party
tools ourselves, or changing anything in org-mode itself for them…

> An implied support requirement to preserve interoperability with
> external tools is a large commitment, and could also run into the
> non-free software issue. Expect people to have strong opinions about
> these matters.

With regards to this, by the very nature of things, any change that would break
interoperability with external tools would have to be a breaking change to the
syntax (with all the relevant implications for org-mode itself). In such a
situation, this would be the major concern, not external tools, so I see this
line of reasoning as being a bit moot.

> Discussions are often fruitful for all involved and shouldn’t be a
> problem when conducted in a respectful manner. Expect critical
> opinions at times, but we should keep it civil.

Indeed. I do find myself wishing that some discussions stayed more on-topic
though…

All the best,
Timothy

  reply	other threads:[~2021-12-06 19:02 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05  7:35 Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal Ihor Radchenko
2021-12-05  9:16 ` Juan Manuel Macías
2021-12-05 10:24   ` Ihor Radchenko
2021-12-05 11:08     ` Juan Manuel Macías
2021-12-05 11:54       ` Heinz Tuechler
2021-12-05 12:08       ` Ihor Radchenko
2021-12-05 13:32         ` Tim Cross
2021-12-05 13:52           ` Bruce D'Arcus
2021-12-05 22:20             ` Tim Cross
2021-12-05 14:30           ` Ihor Radchenko
2021-12-05 22:39             ` Tim Cross
2021-12-08 13:47               ` Ihor Radchenko
2021-12-08 14:39                 ` Tim Cross
2021-12-08 16:16                   ` Dr. Arne Babenhauserheide
2021-12-08 17:07                     ` Russell Adams
2021-12-08 19:22                       ` Dr. Arne Babenhauserheide
2021-12-08 20:14                         ` Russell Adams
2021-12-08 21:50                           ` Tim Cross
2021-12-09  8:12                             ` Dr. Arne Babenhauserheide
2021-12-08 21:25                         ` Tim Cross
2021-12-09  8:07                           ` Dr. Arne Babenhauserheide
2021-12-09  8:36                             ` Timothy
2021-12-09  9:18                               ` Ihor Radchenko
2021-12-09 10:46                     ` Eric S Fraga
2021-12-09 15:21                       ` Russell Adams
2021-12-09 16:25                         ` Eric S Fraga
2021-12-09 21:15                           ` Samuel Wales
2021-12-09 23:27                         ` Dr. Arne Babenhauserheide
2021-12-10  2:42                           ` Tim Cross
2021-12-10  6:08                             ` Dr. Arne Babenhauserheide
2021-12-11 10:03                   ` Ihor Radchenko
2021-12-11 21:19                     ` Tim Cross
2021-12-06 19:41             ` Karl Voit
2021-12-05 18:59         ` Juan Manuel Macías
2021-12-05 23:24           ` Russell Adams
2021-12-06  5:57             ` Juan Manuel Macías
2021-12-06  6:02               ` Timothy
2021-12-06  7:24                 ` Juan Manuel Macías
2021-12-06 10:04                   ` Greg Minshall
2021-12-06 14:59                     ` Juan Manuel Macías
2021-12-06 17:59                       ` Tom Gillespie
2021-12-06 18:25                         ` M. ‘quintus’ Gülker
2021-12-06 18:42                           ` Russell Adams
2021-12-06 18:47                             ` Timothy [this message]
2021-12-06 19:28                               ` Russell Adams
2021-12-06 19:34                                 ` Timothy
2021-12-06 18:30                         ` Russell Adams
2021-12-06 19:10                         ` Gerry Agbobada
2021-12-08 12:56                           ` Ihor Radchenko
2021-12-06 10:08         ` Greg Minshall
2021-12-06 19:45         ` Karl Voit
2021-12-07 11:08           ` Vincent Breton
2021-12-08 13:13             ` Ihor Radchenko
2021-12-08 13:30           ` Ihor Radchenko
2021-12-05 13:06   ` Tim Cross
2021-12-05 14:55     ` Ihor Radchenko
2021-12-05 18:54 ` Timothy
2021-12-06 11:08 ` Max Nikulin
2021-12-06 18:43 ` Russell Adams

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=87o85to8wh.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=RLAdams@AdamsInfoServ.Com \
    --cc=emacs-orgmode@gnu.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).