From: Philip Kaludercic <philipk@posteo.net>
To: "João Távora" <joaotavora@gmail.com>
Cc: "ram via Emacs development discussions." <emacs-devel@gnu.org>,
ram <chat@rj95.be>
Subject: Re: question regarding my emacs package
Date: Mon, 12 Jun 2023 10:54:17 +0000 [thread overview]
Message-ID: <87legpeysm.fsf@posteo.net> (raw)
In-Reply-To: <CALDnm52OHnVJ+c1cxaG=4ud2cdDDpftu78Ed0xwEw9wzs_f26A@mail.gmail.com> ("João Távora"'s message of "Mon, 12 Jun 2023 11:23:27 +0100")
João Távora <joaotavora@gmail.com> writes:
> On Mon, Jun 12, 2023 at 9:45 AM Philip Kaludercic <philipk@posteo.net> wrote:
>>
>> ram via "Emacs development discussions." <emacs-devel@gnu.org> writes:
>>
>> > thanks. did not know this existed. from a quick glance, it looks like
>> > there’s no crossover in prefixes? that seems ok
>>
>> Yes, but it is pretty close and will probably cause confusion. That
>> being said, João is not part of any ELPA so one could argue the name
>> hasn't been reserved...
>
> Just some thoughts:
>
> 1. There is no name clash, as ram observed
Yes, there is only the potential for confusion.
> 2. I'm not aware of a name reservation/parking procedure. As far as I can
> tell, ram's breadcrumbs.el isn't a part of any ELPA yet.
>
> 3. If early manifestation of adding a library is somehow relevant
> then I might point you to this ~8-month old thread where I propose we
> add breadcrumb.el to Emacs [1]. That's where breadcrumb.el was born and
> proposed for Emacs.
Oh, I did not know that. Intuitively, I would argue that you tried to
reserve the name in the "core emacs/ELPA namespace" first.
> I'm still on the fence about whether to propose
> it for a :core package or ELPA package. It takes inspiration on a
> similar-named lsp-mode feature and the "breadcrumb" concept is apparently
> a common name given to the type of feature breadcrumb.el enables.
I think that both options would be fine, and I'd be happy to help with
either.
> 4. There is no name clash, I think this bears repeating.
>
> 5. Above, I wrote "if early manifestation... is relevant". I don't think
> it should be. If avoiding confusion to users is a goal to pursue -- and
> if this confusion is indeed real (see 4 and 1) -- then I think it's more
> important to evaluate the potential consequences of a rename in existing
> users of each package. We don't know that number, but merely as data point,
> breadcrumbs.el has 6 github stars and breadcrumb.el has 116.
Arguing via stars is difficult, because on the one hand you are a well
known Elisp author and your packages are bound to attract more attention
over a longer period of time, but we cannot deduce anything from these
facts. E.g. None of my packages (except for Compat, which is
co-maintained) are on GitHub, so this metric couldn't be used if ram
decided to use SourceHut as well.
> 6. Please let's avoid another "meaning of names/meaning of life" thread.
> There is no name clash.
Ok, in that case I won't argue that that this is one of the issue of
using intuitive names ;)
> João
>
> [1]: https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-10/msg01027.html
--
Philip Kaludercic
next prev parent reply other threads:[~2023-06-12 10:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 3:18 question regarding my emacs package ram
2023-06-07 15:53 ` Philip Kaludercic
2023-06-07 18:04 ` Philip Kaludercic
2023-06-07 19:45 ` ram
2023-06-07 19:48 ` Philip Kaludercic
2023-06-07 19:50 ` ram
2023-06-07 22:34 ` ram
2023-06-08 7:13 ` ram
2023-06-08 7:26 ` Philip Kaludercic
2023-06-08 18:50 ` ram
2023-09-08 7:40 ` Philip Kaludercic
2023-06-11 11:41 ` Madhu
2023-06-12 12:52 ` Madhu
2023-06-12 16:40 ` Andrea Corallo
2023-06-13 4:01 ` Madhu
2023-06-13 8:55 ` Andrea Corallo
2023-06-13 9:19 ` Madhu
2023-06-13 23:55 ` Michael Heerdegen
2023-06-14 16:10 ` Mattias Engdegård
2023-06-16 3:53 ` Michael Heerdegen
2023-06-16 4:46 ` Madhu
2023-06-16 15:28 ` Michael Heerdegen
2023-06-17 3:01 ` ram via Emacs development discussions.
2023-06-18 0:40 ` Michael Heerdegen
2023-06-29 19:28 ` ram
2023-06-11 18:49 ` João Távora
2023-06-11 19:08 ` ram via Emacs development discussions.
2023-06-12 8:45 ` Philip Kaludercic
2023-06-12 10:23 ` João Távora
2023-06-12 10:54 ` Philip Kaludercic [this message]
2023-06-12 20:43 ` João Távora
2023-06-13 0:36 ` ram via Emacs development discussions.
2023-06-13 18:13 ` João Távora
2023-06-13 21:46 ` ram
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87legpeysm.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=chat@rj95.be \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.