[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ELPA] New package: dape
|
From: |
João Távora |
|
Subject: |
Re: [ELPA] New package: dape |
|
Date: |
Thu, 2 Nov 2023 14:42:38 +0000 |
On Wed, Nov 1, 2023 at 7:14 PM Dmitry Gutov <dmitry@gutov.dev> wrote:
>
> On 20/10/2023 17:53, John Yates wrote:
> > On Thu, Oct 19, 2023 at 7:07 AM Dmitry Gutov<dmitry@gutov.dev> wrote:
> >> On 19/10/2023 13:52, Krister Schuchardt wrote:
> >>> Has `dapper` been suggested?
> >> I wanted to suggest 'dapper' too. XD
> >>
> >> That could be interpreted as a subtle dig at dap-mode, though. Like,
> >> you're dap, and I'm dapper. 😉 Which is probably not the intention.
> > If we want to avoid the suggestion of a dig, how about dappel?
>
> I do like the "dapper" option (it could some with stylized image or
> whatever). "dappel" isn't bad, though there is no noun by that name.
>
> Anyway, it's all up to the author, whether he wants to rename or not.
Just found out about this initiative, great stuff.
I especially like the fact that like Eglot, it seems to be completely
language agnostic and doesn't require little dape-<language>.el
add-ons.
But shouldn't it be using jsonrpc.el? It seems to implement
that base protocol all over again, much like eglot.el did
in its early days. Was this intentional, is there a limitation
in jsonrpc.el that should be addressed?
As to the name, I think "dape" is fine.
- Re: [ELPA] New package: dape, Philip Kaludercic, 2023/11/01
- Re: [ELPA] New package: dape, Dmitry Gutov, 2023/11/01
- Re: [ELPA] New package: dape,
João Távora <=
- Re: [ELPA] New package: dape, Adam Porter, 2023/11/04
- Re: [ELPA] New package: dape, Eli Zaretskii, 2023/11/04
- Re: [ELPA] New package: dape, Philip Kaludercic, 2023/11/04
- Re: [ELPA] New package: dape, Adam Porter, 2023/11/04
- Re: [ELPA] New package: dape, Philip Kaludercic, 2023/11/04
- Re: [ELPA] New package: dape, Adam Porter, 2023/11/04
- Re: [ELPA] New package: dape, Eli Zaretskii, 2023/11/04