From: Jan Rehders <jan@sheijk.net>
To: emacs-devel@gnu.org
Subject: Re: Adding new package org-menu to nongnu elpa
Date: Sat, 23 Nov 2024 00:18:42 +0900 [thread overview]
Message-ID: <BC476264-83AB-4289-AC3A-7464032ABDB2@sheijk.net> (raw)
In-Reply-To: <6F39D8DC-48AD-4F48-96D0-C8BE353198C6@sheijk.net>
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
Haven’t gotten any reaction from maintainers so I think we can continue with adding this to nongnu elpa
> On 17. Nov 2024, at 23:02, Jan Rehders <jan@sheijk.net> wrote:
>
> Yes the name is a good point. I don’t mind renaming it but I’m not sure to what. org-transient has been proposed but that one might just have the same issue. Proposals are very welcome!
>
> I’ve written a mail to emacs-orgmode@gnu.org <mailto:emacs-orgmode@gnu.org> ("Contributing org-menu (using transient) to Orgmode?”). Lets put adding this this on hold until that discussion finishes
>
> — Jan
>
>> On 16. Nov 2024, at 15:30, Adam Porter <adam@alphapapa.net> wrote:
>>
>> Hello Jan,
>>
>> A Transient menu system for Org is definitely needed. Have you discussed this on the Org mailing list? Now that Transient is built in to Emacs, this is a feature that ought to be built in to Org. And it ought to be standardized and modularized so that it can (eventually) be expanded and adapted to all parts of Org.
>>
>> As well, I have a minor concern about the name: org-menu is so obviously the right name for the feature, that having it as a package on (non-) GNU ELPA would present a conflict, preventing Org from implementing the feature internally under that name.
>>
>> So it would seem best if you could contribute the package upstream to Org; it could be an example and foundation for this work to grow on.
>>
>> What do you think?
>>
>> --Adam
>
[-- Attachment #2: Type: text/html, Size: 2317 bytes --]
next prev parent reply other threads:[~2024-11-22 15:18 UTC|newest]
Thread overview: 9+ 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-22 15:18 ` Jan Rehders [this message]
2024-11-22 16:24 ` Ihor Radchenko
2024-11-17 4:38 ` Richard Stallman
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=BC476264-83AB-4289-AC3A-7464032ABDB2@sheijk.net \
--to=jan@sheijk.net \
--cc=emacs-devel@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.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).