unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Jan Rehders <jan@sheijk.net>
Cc: emacs-devel@gnu.org
Subject: Re: Adding new package org-menu to nongnu elpa
Date: Sat, 16 Nov 2024 23:38:46 -0500	[thread overview]
Message-ID: <E1tCX3e-0005fm-Hn@fencepost.gnu.org> (raw)
In-Reply-To: <F4C06F55-0D0A-4F4C-B76B-35A071FA1A5E@sheijk.net> (message from Jan Rehders on Thu, 14 Nov 2024 22:01:04 +0900)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

We try to aim to make Emacs coherent.  So when we consider adding to
Emacs a package that implemnts a new feature, it isn't just a matter
of how many users lke that feature.

There are several things we might want to do with a new feature
implemented as a eparate package:

* Add it to Emacs as written.
* Leave it out.
* Merge the code into related parts of Emacs for better integration.
* Reimplement the feature for better integration
* And someimes others.

Since I don't use Org mode, I don't have an opinion about what to do
in this case.  I'm simply reminding people to think about these
options for the functionaliy of org-menu, and make a good choice.



-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





      parent reply	other threads:[~2024-11-17  4:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 13:01 Adding new package org-menu to nongnu elpa Jan Rehders
2024-11-15 13:45 ` Philip Kaludercic
2024-11-15 16:20   ` Jan Rehders
2024-11-16  0:54     ` Philip Kaludercic
2024-11-16  6:30 ` Adam Porter
2024-11-17 14:02   ` Jan Rehders
2024-11-17  4:38 ` Richard Stallman [this message]

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1tCX3e-0005fm-Hn@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan@sheijk.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.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).