From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: question regarding my emacs package Date: Mon, 12 Jun 2023 10:54:17 +0000 Message-ID: <87legpeysm.fsf@posteo.net> References: <6cG8Tc55Zz8xk6rE6mJLfDxckAINPcYqp781yltsndzqq5146yw76EZ_2CoUtQT4P2j2afSx5VRD5G1-9qzFHWAW3LxYWwmxh87lvB2MgNE=@rj95.be> <6mCY9snoMM3JtwsTaSp34B-_9KfmBytTJID4gppHZ2B9xyTbkofc60vHD1qEI7WWpn2BwgaS1WaVjGJRatECpFJNbtUxg3FgqgcCBPnbD3s=@rj95.be> <87y1kpf4r0.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35817"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "ram via Emacs development discussions." , ram To: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jun 12 12:54:55 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q8fCI-000908-6f for ged-emacs-devel@m.gmane-mx.org; Mon, 12 Jun 2023 12:54:54 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q8fBo-0005Du-P0; Mon, 12 Jun 2023 06:54:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q8fBm-0005DX-Lg for emacs-devel@gnu.org; Mon, 12 Jun 2023 06:54:22 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q8fBk-0006aN-Bu for emacs-devel@gnu.org; Mon, 12 Jun 2023 06:54:22 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id BEC69240104 for ; Mon, 12 Jun 2023 12:54:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1686567257; bh=4yBUueN2NQKQZgTn/Rg0Qua2JKxzELCY9l7Q0/HwUoc=; h=From:To:Cc:Subject:Autocrypt:Date:Message-ID:MIME-Version: Content-Transfer-Encoding:From; b=gwEzy3ltK7MuGs7PqM5FuBlqimaEOuAkQybAGz3UT/bbhggqXlphDjyFdg9GmF4iN Bvb9E7jwUovK72BpwU6b2cheZBrrP0eKhxrCEth0R+ByEonFcy0CVXsc+jRmHhKaVI QEJL3sh0dXeVVuczjFHb0tDBv1jksbDLWFIP06wuKVGsuhEB+7LJ9vq4rJBADWglCH tgZCVx2Xr0w0YpOg62xcRaAbe5u5vIaJs4/pXu0zf20cAwec9/1jv5kFeAqhUhNOzD cr+L00gAD5/5eMnhhoD3D32W4gwugdN2cOoTRGM5RhsK1JqzeRP1brX5gf9AaKcGP8 h4gZPXcJ0bb5Q== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QfpTj2v2Gz6twR; Mon, 12 Jun 2023 12:54:17 +0200 (CEST) In-Reply-To: (=?utf-8?Q?=22Jo=C3=A3o_T=C3=A1vora=22's?= message of "Mon, 12 Jun 2023 11:23:27 +0100") X-Hashcash: 1:20:230612:joaotavora@gmail.com::vqUc4EeP/m8vnVyn:nko X-Hashcash: 1:20:230612:chat@rj95.be::ImVUHRAIRcfdgVJW:/ib X-Hashcash: 1:20:230612:emacs-devel@gnu.org::L5fPKic/W5vypxSQ:7Ny0 Autocrypt: addr=philipk@posteo.net; keydata= mDMEZBBQQhYJKwYBBAHaRw8BAQdAHJuofBrfqFh12uQu0Yi7mrl525F28eTmwUDflFNmdui0QlBo aWxpcCBLYWx1ZGVyY2ljIChnZW5lcmF0ZWQgYnkgYXV0b2NyeXB0LmVsKSA8cGhpbGlwa0Bwb3N0 ZW8ubmV0PoiWBBMWCAA+FiEEDg7HY17ghYlni8XN8xYDWXahwukFAmQQUEICGwMFCQHhM4AFCwkI BwIGFQoJCAsCBBYCAwECHgECF4AACgkQ8xYDWXahwulikAEA77hloUiSrXgFkUVJhlKBpLCHUjA0 mWZ9j9w5d08+jVwBAK6c4iGP7j+/PhbkxaEKa4V3MzIl7zJkcNNjHCXmvFcEuDgEZBBQQhIKKwYB BAGXVQEFAQEHQI5NLiLRjZy3OfSt1dhCmFyn+fN/QKELUYQetiaoe+MMAwEIB4h+BBgWCAAmFiEE Dg7HY17ghYlni8XN8xYDWXahwukFAmQQUEICGwwFCQHhM4AACgkQ8xYDWXahwukm+wEA8cml4JpK NeAu65rg+auKrPOP6TP/4YWRCTIvuYDm0joBALw98AMz7/qMHvSCeU/hw9PL6u6R2EScxtpKnWof z4oM Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306741 Archived-At: Jo=C3=A3o T=C3=A1vora writes: > On Mon, Jun 12, 2023 at 9:45=E2=80=AFAM Philip Kaludercic wrote: >> >> ram via "Emacs development discussions." writes: >> >> > thanks. did not know this existed. from a quick glance, it looks like >> > there=E2=80=99s no crossover in prefixes? that seems ok >> >> Yes, but it is pretty close and will probably cause confusion. That >> being said, Jo=C3=A3o 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.=20=20 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 poi= nt, > 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=C3=A3o > > [1]: https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-10/msg01027.ht= ml --=20 Philip Kaludercic