From: brickviking <brickviking@gmail.com>
To: emacs-devel@gnu.org, Augusto Stoffel <arstoffel@gmail.com>
Cc: Philip Kaludercic <philipk@posteo.net>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: ELPA submission: plz-see
Date: Thu, 2 Nov 2023 09:21:54 +1300 [thread overview]
Message-ID: <CAHWye87JObJ1mV0aFG3C08u36rnHwF+91gAsPC85oREkK0V1PQ@mail.gmail.com> (raw)
In-Reply-To: <87o7gd9v8u.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
Before this package reached my radar, I'd never even heard of plz. :-)
Regards, brickviking
On Thu, 2 Nov 2023 at 07:36, Augusto Stoffel <arstoffel@gmail.com> wrote:
> On Wed, 1 Nov 2023 at 09:14, Philip Kaludercic wrote:
>
> >>> I agree, from what I see this is just an implementation detail. Plz is
> >>> a peculiar enough name as it is, it shouldn't be inherited by packages
> >>> that depend on it. Or is there any reason why the package couldn't
> also
> >>> use url.el?
> >>
> >> The packages is really closely tied to plz's API, which by the way is a
> >> very nice one.
> >
> > But is this fact exposed to the user?
>
> Totally. Perhaps if you had a look into plz you would appreciate this
> fact :-).
>
>
[-- Attachment #2: Type: text/html, Size: 1148 bytes --]
next prev parent reply other threads:[~2023-11-01 20:21 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 [this message]
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
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=CAHWye87JObJ1mV0aFG3C08u36rnHwF+91gAsPC85oREkK0V1PQ@mail.gmail.com \
--to=brickviking@gmail.com \
--cc=arstoffel@gmail.com \
--cc=eliz@gnu.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).