all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Thomas Fitzsimmons <fitzsim@fitzsim.org>,
	 emacs-devel <emacs-devel@gnu.org>
Subject: Re: [GNU ELPA] New package: url-http-oauth
Date: Mon, 08 May 2023 07:22:27 -0700	[thread overview]
Message-ID: <p91r0rqvr6k.fsf@google.com> (raw)
In-Reply-To: <CALDnm50G3cbOnxHUBdUCVHn0T=1apBcpiy5hgohikA60GOUyZQ@mail.gmail.com> ("João Távora"'s message of "Mon, 8 May 2023 08:50:06 +0100")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 681 bytes --]


url.el is definitely outdated and  likely one of the bottlenecks that
holds back EWW; the other is of course JS.

I looked at plz.el when it came out and it is nice; by  depending on
Curl, it immediately brings Emacs up-to-date with various URL bits that
have languished in url.el. That said, for Emacs to be able to move on
from url.el, I suspect we'll need an 80/20 plz wrapper that if loaded by
the user causes calls to the url library to be overridden by plz so that
one can then use EWW to validate the effectiveness and completeness of
plz.

Any Takers?


-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8



  parent reply	other threads:[~2023-05-08 14:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06  5:07 [GNU ELPA] New package: url-http-oauth Thomas Fitzsimmons
2023-05-07 15:55 ` Philip Kaludercic
2023-05-08  7:50 ` João Távora
2023-05-08 10:30   ` Philip Kaludercic
2023-05-08 14:22   ` T.V Raman [this message]
2023-05-08 16:19     ` João Távora
2023-05-08 16:26       ` Eli Zaretskii
2023-05-08 16:44       ` T.V Raman
2023-05-08 15:27   ` Thomas Fitzsimmons
2023-05-08 17:03     ` João Távora

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=p91r0rqvr6k.fsf@google.com \
    --to=raman@google.com \
    --cc=emacs-devel@gnu.org \
    --cc=fitzsim@fitzsim.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.