emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: autofrettage <autofrettage@protonmail.ch>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: A requires/provides approach to linking source code blocks
Date: Fri, 09 Jul 2021 17:00:10 +0000	[thread overview]
Message-ID: <95_WQAdCOQRo2u4VTanEqQ9QrbmOhFNk4aTCGlvgNU8PkVz3j7SQfwIZuwoxtQj0v5bGnRnP6NPf-Z6ImfWKpg_pHF6sTFHMgw0KVfir06U=@protonmail.ch> (raw)

Tim wrote:
> This could just be me, but recently, I'm becoming very concerned
> about the growth of additional features and options in org mode.

Count me in. I have been mostly been hanging around in the shadows, but this is serious enough for me to wave a flag on the right side.

I would go as far as saying that several suggestions have been so niche, as to be labeled feature bloats. They can be made available as user-added extensions through melpa, but should stay outside org itself.

just my ¢2

Rasmus


             reply	other threads:[~2021-07-09 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09 17:00 autofrettage [this message]
2021-07-12  9:55 ` A requires/provides approach to linking source code blocks Alexander Adolf
2021-07-13 19:18   ` Tom Gillespie
2021-07-13 19:42     ` George Mauer
2021-07-14  0:44     ` Tim Cross
2021-07-14  1:53       ` Samuel Wales
  -- strict thread matches above, loose matches on Subject: below --
2021-07-08 16:24 Marko Schuetz-Schmuck
2021-07-08 19:32 ` Tim Cross
2021-07-09 13:38   ` Maxim Nikulin
2021-07-09 20:27   ` Berry, Charles via General discussions about Org-mode.
2021-07-09  7:29 ` Stefan Nobis

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='95_WQAdCOQRo2u4VTanEqQ9QrbmOhFNk4aTCGlvgNU8PkVz3j7SQfwIZuwoxtQj0v5bGnRnP6NPf-Z6ImfWKpg_pHF6sTFHMgw0KVfir06U=@protonmail.ch' \
    --to=autofrettage@protonmail.ch \
    --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).