unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: rms@gnu.org
Cc: brickviking@gmail.com, eliz@gnu.org, emacs-devel@gnu.org,
	philipk@posteo.net
Subject: Re: ELPA submission: plz-see
Date: Sat, 4 Nov 2023 00:08:52 -0500	[thread overview]
Message-ID: <3e406a2c-712d-4fee-877a-2376517619a8@alphapapa.net> (raw)
In-Reply-To: <E1qz67h-0000iK-D8@fencepost.gnu.org>

>   > > > I have it listed here in my elpa packages listing. A very short summary
>   > > > from
>   > > > the package itself is as follows:
>   > > >
>   > > > `plz' is an HTTP library for Emacs.
> 
> Does having this in ELPA add something significant to Emacs?
> 
>          It uses `curl' as a backend, which
>   > > > avoids some of the issues with using Emacs's built-in `url' library.
> 
> Would it be feasible to improve the `url' library to make `plz' unnecessary?
> Would it be feasible to change `url' compatibly to do its work using `plz'?
> Either way, we would have just one package for this job, and that would
> be simpler than having two.

As you may remember, we had this discussion at the time plz.el was added 
to GNU ELPA.  plz.el is not even the only HTTP client library on ELPA. 
It was developed after years of consideration of the shortcomings of the 
existing alternatives, and submitted to GNU ELPA after years of careful 
development.  Since then, it has matured and become a reliable, 
performant, easy-to-use (if I do say so myself) library that solves 
several problems in the alternatives, and is used by other ELPA and 
non-ELPA packages, some of which are widely used.

As has been said on emacs-devel several times over the years, the next 
significant step in this field would most likely be for Emacs to 
integrate libcurl directly.  Maybe someday that will happen...



  reply	other threads:[~2023-11-04  5:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  7:17 ELPA submission: plz-see Augusto Stoffel
2023-10-30 11:56 ` Eli Zaretskii
2023-10-31  8:09   ` Augusto Stoffel
2023-10-31  8:43   ` Philip Kaludercic
2023-10-31 20:17     ` Augusto Stoffel
2023-11-01  9:14       ` Philip Kaludercic
2023-11-01 18:36         ` Augusto Stoffel
2023-11-01 20:21           ` brickviking
2023-11-03  2:31             ` Richard Stallman
2023-11-03  6:32               ` brickviking
2023-11-03  7:50                 ` Philip Kaludercic
2023-11-03  8:06                   ` Eli Zaretskii
2023-11-03 14:46                     ` Adam Porter
2023-11-04  1:10                       ` Stefan Kangas
2023-11-04  2:10                     ` Richard Stallman
2023-11-04  5:08                       ` Adam Porter [this message]
2023-11-04  6:49                         ` Eli Zaretskii
2023-11-04  8:51                           ` tomas
2023-11-04  9:07                             ` Eli Zaretskii
2023-11-04  9:34                               ` tomas
2023-11-04 13:30                               ` Adam Porter
2023-11-04 13:56                                 ` Eli Zaretskii
2023-11-04 14:38                                   ` Adam Porter
     [not found]                               ` <877cmx4wgd.fsf@dick>
2023-11-04 13:37                                 ` tomas
     [not found]                                   ` <8734xlmwsm.fsf@dick>
2023-11-04 14:24                                     ` tomas
2023-11-04 10:38                             ` Stefan Kangas
2023-11-04 12:28                               ` Visuwesh
2023-11-04 13:17                                 ` tomas
2023-11-04 13:13                               ` tomas
2023-11-04  6:47                       ` Eli Zaretskii
2023-10-30 22:33 ` Stefan Kangas
2023-10-31  8:09   ` Augusto Stoffel
2023-11-01  0:37     ` Stefan Kangas
2023-11-01  7:29       ` Augusto Stoffel
2023-11-01 20:23         ` Stefan Kangas
2023-10-31  9:33 ` Mauro Aranda
2023-10-31 20:19   ` Augusto Stoffel

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=3e406a2c-712d-4fee-877a-2376517619a8@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=brickviking@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rms@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).