From: Akseli Lahtinen <akselmo@akselmo.dev>
To: Tom Tromey <tom@tromey.com>
Cc: Tom Tromey <tom@tromey.com>, gdb@sourceware.org
Subject: Re: Help with setting up DAP for Kate text editor
Date: Mon, 22 Jan 2024 23:07:28 +0200 [thread overview]
Message-ID: <4890568.09ZEJKoR3W@fedora-desktop> (raw)
In-Reply-To: <871qa9tci8.fsf@tromey.com>
It ended up being a very simple fix, you can see the merge request I made
here: https://invent.kde.org/utilities/kate/-/merge_requests/1391
Basically Kate was sending QJsonValue that defaults to "null" but
changing that to QJsonObject fixed the issue.
- Akseli
On Monday 22 January 2024 21:05:19 EET Tom Tromey wrote:
> > Thanks for your help!
> > I will create bugreport to Kate and ask around.
>
> Let us know what you find out. I'm happy to discuss the situation,
> though coordinating via the DAP specification github might be best.
>
> Tom
prev parent reply other threads:[~2024-01-22 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 9:24 Akseli Lahtinen
2024-01-17 15:15 ` Tom Tromey
2024-01-21 17:03 ` Akseli Lahtinen
2024-01-22 13:45 ` Tom Tromey
2024-01-22 17:21 ` Tom Tromey
2024-01-22 17:28 ` Akseli Lahtinen
2024-01-22 19:05 ` Tom Tromey
2024-01-22 21:07 ` Akseli Lahtinen [this message]
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=4890568.09ZEJKoR3W@fedora-desktop \
--to=akselmo@akselmo.dev \
--cc=gdb@sourceware.org \
--cc=tom@tromey.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.
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).