[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ELPA] New package: dape
From: |
Philip Kaludercic |
Subject: |
Re: [ELPA] New package: dape |
Date: |
Thu, 19 Oct 2023 15:12:30 +0000 |
Daniel Pettersson <daniel@dpettersson.net> writes:
> On Sat, Oct 14, 2023 at 4:54 PM Philip Kaludercic <philipk@posteo.net> wrote:
>
>> I have tried to try it out right now, but because I've never used DAP
>> before, I am not sure how to get it running properly. Nevertheless, I
>> think it would be useful to have something along these lines:
>
> Did you get working?
I haven't had the time to try since.
>> + (customize-variable 'dape-configs)
>
> Implemented
1+
>> Another interesting idea to pursue might be to have modular UIs.
>> Instead of splitting up the current Emacs frame, I think a minimalist,
>> more edebug-like interface would be nice, where variable values could be
>> displayed using overlays instead of having a separate buffer.
>
> Nice suggestion. I did try to implement a more minimalist interface with
> variable overlays.
>
> Which can be enabled with the following.
> (setq dape-inline-variables t)
> (setq dape-on-start-hooks nil)
This sounds great, I'll have to try it out at some point! It might be
nice to have this as a minor mode that you could enable with a hook or
as a global minor mode.
> Second screenshot in the README.org, it's more inline with edebug.
Just FYI these don't appear to be displayed on the GitHub page.
> But
> there is some issues with placement and variable lookup. The current
> implementation relies on regex and font lock to search for symbols.
> If that work could be offloaded to Eglot/lsp-mode via xref (*I don't
> know if lsp support it). But currently that is not possible because
> Eglot only supports looking up reference at point.
Have you contacted João?
>> Note that you don't need to add Compat just for `defvar-keymap', as you
>> could also just use the traditional method of defining a keymap instead:
>
> Fixed.
>
>> It just doesn't say that much, and I don't know if it is intended, but
>> the usual way I would read/pronounce it (rhyming with cape) wouldn't
>> immediately signal any relation to DAP. Note that you can use (elisp)
>> Shorthands to avoid writing out a longer name inside the file, in case a
>> longer name like debuger-adapter. It seems there is no package by the
>> name of "dbg"? If we are not interested in a self-descriptive and
>> memorable name, and would want to create a parallel to Eglot (IIRC Emacs
>> polyGLOT), perhaps something like based on "Emacs Debugger" (Egger?
>> Ebugger? Edebugger?) might be possible as well.
>
> "dbg" is nice and sweet, but I think it's a + for discoverability to have
> dap in the name of the package. How about eldap? If it should signify
> a connection to Eglot, maybe Ebug or even closer Dpoly? Or maybe a
> reference to Grace Hopper, hopper.
While I like eldap, note that this doesn't have a direct connection to
Eglot -- which is /not/ Elgot.
> Personally I like eldap, probably because it feels familiar.
- Re: [ELPA] New package: dape, (continued)
- Re: [ELPA] New package: dape, Daniel Pettersson, 2023/10/18
- Re: [ELPA] New package: dape, Adam Porter, 2023/10/18
- Re: [ELPA] New package: dape, Krister Schuchardt, 2023/10/19
- Re: [ELPA] New package: dape, Dmitry Gutov, 2023/10/19
- Re: [ELPA] New package: dape, John Yates, 2023/10/20
- Re: [ELPA] New package: dape,
Philip Kaludercic <=
- Re: [ELPA] New package: dape, Björn Bidar, 2023/10/19
Re: [ELPA] New package: dape, Mauro Aranda, 2023/10/15
Re: [ELPA] New package: dape, Milan Glacier, 2023/10/20