From: "João Pedro" <jpedrodeamorim@gmail.com>
To: Akib Azmain Turja <akib@disroot.org>,
Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New packages: popon, corfu-popup, flymake-popon
Date: Thu, 19 May 2022 15:26:54 -0300 [thread overview]
Message-ID: <87wneh9y4x.fsf@gmail.com> (raw)
In-Reply-To: <874k1l8ksp.fsf@disroot.org>
Hello Akib, just chiming in with some opinions as a user.
On Fri, May 20 2022 00:00, Akib Azmain Turja <akib@disroot.org> wrote:
> It is named corfu-popup because it's older than Popon. Actually Popon
> was extracted from corfu-popup to allow other packages to use it, as
> different popup implementation don't work together (and trying do so
> will break both, and the buffer contents will probably be at risk too).
> There is already a package named popup.el, so I named my package Popon,
> but I didn't change the name of corfu-popup. I wrote flymake-popon
> later, so I included "popon" in the name. I think this shouldn't be a
> problem for submission, but if it is a problem, I have no problem
> changing the name.
I don't think it would be a problem for submission, Philip was just
wondering why the name was different, mostly because, as you noted
yourself, it can be misleading, leading users to think it would be a
package to make Corfu use popup.el.
> But, now it seems to me that name is misleading, because child frame and
> Popon both are some type of popup. So I have changed the name to
> corfu-terminal (which Corfu author suggested me) to make it's purpose
> clear.
Now I must wonder -- and keep in mind that it is not a problem per-se at
all -- why you didn't rename it to corfu-popon, keeping it aligned with
the other packages...
Overall, great contributions to this package ecosystem, and I hope to
see it in ELPA in the near future!
Best regards,
--
João Pedro de Amorim Paula
IT undergraduate at Universidade Federal do Rio Grande do Norte (UFRN)
next prev parent reply other threads:[~2022-05-19 18:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 15:11 [NonGNU ELPA] New packages: popon, corfu-popup, flymake-popon Akib Azmain Turja
2022-05-18 18:44 ` Philip Kaludercic
2022-05-19 11:10 ` Akib Azmain Turja
2022-05-19 14:27 ` Philip Kaludercic
2022-05-19 18:00 ` Akib Azmain Turja
2022-05-19 18:26 ` João Pedro [this message]
2022-05-19 19:45 ` Akib Azmain Turja
2022-05-20 4:37 ` João Pedro
2022-05-20 4:40 ` João Pedro
2022-05-19 17:59 ` [NonGNU ELPA] New packages: popon, corfu-terminal, flymake-popon (Was: [NonGNU ELPA] New packages: popon, corfu-popup, flymake-popon) Akib Azmain Turja
2022-05-20 23:50 ` [NonGNU ELPA] New packages: popon, corfu-terminal, flymake-popon Philip Kaludercic
2022-05-21 7:33 ` Akib Azmain Turja
2022-05-21 8:05 ` Philip Kaludercic
2022-05-21 12:59 ` Akib Azmain Turja
2022-05-21 14:02 ` Philip Kaludercic
2022-05-22 11:17 ` Akib Azmain Turja
2022-05-22 11:31 ` Philip Kaludercic
2022-05-22 16:25 ` Philip Kaludercic
2022-05-23 7:12 ` Akib Azmain Turja
2022-05-23 8:11 ` Philip Kaludercic
2022-05-23 9:18 ` Akib Azmain Turja
2022-05-23 15:31 ` Philip Kaludercic
2022-05-20 22:31 ` [NonGNU ELPA] New packages: popon, corfu-popup, flymake-popon Richard Stallman
2022-05-21 7:36 ` Akib Azmain Turja
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=87wneh9y4x.fsf@gmail.com \
--to=jpedrodeamorim@gmail.com \
--cc=akib@disroot.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.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).