From: "João Távora" <joaotavora@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Daniel Pettersson <daniel@dpettersson.net>,
Dmitry Gutov <dmitry@gutov.dev>,
John Yates <john@yates-sheets.org>,
Krister Schuchardt <krister.schuchardt@gmail.com>,
Adam Porter <adam@alphapapa.net>,
emacs-devel@gnu.org
Subject: Re: [ELPA] New package: dape
Date: Tue, 5 Dec 2023 09:18:45 +0000 [thread overview]
Message-ID: <CALDnm50AzHGCcHT-RkbMDzjd4NLPtietKm=4D67yWRhF+1PPMw@mail.gmail.com> (raw)
In-Reply-To: <87bkb5jb1q.fsf@posteo.net>
On Tue, Dec 5, 2023 at 8:41 AM Philip Kaludercic <philipk@posteo.net> wrote:
> I have resolved the issue directly with Daniel. The package has been
> added to GNU ELPA.
>
> Depending on how it is received, it would be nice to see the package be
> added to the core in some form or another.
Yes to this. I'm working to make it as well received as possible.
In fact, I've been working on dape.el (slightly late unfortunately,
but hope to pick up on that soon) and these enhancements need
`jsonrpc.el` changes too, so I've been working on a branch of Emacs
where dape.el lives alongside eglot.el in core. Of course this was
just for practical reasons, I'll take it out if there when I'm done,
unless someone tells me to _not_ take it out ;-).
> By my book, the naming issue
> could be resolved by adding a `start-dap' command (a `start-lsp' alias
> for Eglot would also be nice).
There is no real naming issue, but I'm not opposed to adding those
aliases if M-x dape and M-x eglot both stay)
next prev parent reply other threads:[~2023-12-05 9:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 10:35 [ELPA] New package: dape Daniel Pettersson
2023-10-13 12:24 ` Philip Kaludercic
2023-10-14 12:28 ` Daniel Pettersson
2023-10-14 14:54 ` Philip Kaludercic
2023-10-15 13:50 ` James Thomas
2023-10-15 14:12 ` Philip Kaludercic
2023-10-15 17:24 ` John Yates
2023-10-18 21:54 ` Daniel Pettersson
2023-10-19 2:08 ` Adam Porter
2023-10-19 10:52 ` Krister Schuchardt
2023-10-19 11:06 ` Dmitry Gutov
2023-10-20 14:53 ` John Yates
2023-11-01 19:13 ` Dmitry Gutov
2023-11-02 14:42 ` João Távora
2023-11-04 9:51 ` Daniel Pettersson
2023-11-04 10:00 ` Philip Kaludercic
2023-11-23 6:10 ` Philip Kaludercic
2023-12-05 8:41 ` Philip Kaludercic
2023-12-05 9:18 ` João Távora [this message]
2023-12-05 10:59 ` Philip Kaludercic
2023-12-05 11:29 ` João Távora
2023-12-06 3:57 ` Richard Stallman
2023-12-06 10:09 ` Daniel Pettersson
2023-12-06 12:30 ` Eli Zaretskii
2023-12-06 12:56 ` João Távora
2023-12-06 13:08 ` Eli Zaretskii
2023-12-06 13:38 ` João Távora
2023-12-06 17:00 ` Eli Zaretskii
2023-12-06 23:03 ` João Távora
2023-12-06 23:55 ` Daniel Pettersson
2023-12-07 7:13 ` Eli Zaretskii
2023-11-04 13:46 ` Adam Porter
2023-11-04 14:01 ` Eli Zaretskii
2023-11-04 14:24 ` Philip Kaludercic
2023-11-04 15:06 ` Adam Porter
2023-11-04 15:27 ` Philip Kaludercic
2023-11-04 14:53 ` Adam Porter
2023-11-04 15:14 ` Eli Zaretskii
2023-11-04 19:15 ` Adam Porter
2023-11-04 23:21 ` João Távora
2023-11-07 10:19 ` Daniel Pettersson
2023-11-07 10:40 ` João Távora
2023-11-08 8:31 ` Daniel Pettersson
2023-10-19 15:12 ` Philip Kaludercic
2023-10-19 17:50 ` Björn Bidar
2023-11-01 16:50 ` Philip Kaludercic
2023-10-15 13:55 ` Mauro Aranda
2023-10-17 20:39 ` Daniel Pettersson
2023-10-20 5:49 ` Milan Glacier
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='CALDnm50AzHGCcHT-RkbMDzjd4NLPtietKm=4D67yWRhF+1PPMw@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=adam@alphapapa.net \
--cc=daniel@dpettersson.net \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=krister.schuchardt@gmail.com \
--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).