From: "Niteesh G. S." <email@example.com>
To: Stefan Hajnoczi <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org, email@example.com,
John Snow <firstname.lastname@example.org>
Subject: Re: Fwd: GSoC Intro - TUI interface for QMP
Date: Wed, 26 May 2021 21:05:43 +0530 [thread overview]
Message-ID: <CAN6ztm8rpDARg786+yq2S58T2wQ7TWSQ+H_3xgfUnRTbgc0k+A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Mon, May 24, 2021 at 7:02 PM Stefan Hajnoczi <email@example.com> wrote:
> On Sat, May 22, 2021 at 12:32:00AM +0530, Niteesh G. S. wrote:
> > By end of this summer, I would like to get a basic TUI with some
> > features working. Some of the features I would like to get working are
> > 1) Syntax checking
> > 2) Syntax highlighting
> > 3) Code completion
> > 4) Logging
> > I would like to hear some of the features you would like to have and also
> > your
> > advice's on implementation.
> Welcome Niteesh!
> It would be great to have an QMP API documentation viewer built into the
> TUI. When you enter a command like 'migrate' it would automatically
> display the associated QMP command documentation from qapi/*.json.
That's a great idea.
Do you want the documentation as a popup or in a separate tab?
By separate tab what I mean is a full window dedicated to documentation
with some kind of search functionality.
[-- Attachment #2: Type: text/html, Size: 1993 bytes --]
next prev parent reply other threads:[~2021-05-26 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN6ztm-J2GoQKkLb=Az0H2Q8UKK4oE3PgXg7g14=T53sQAUyDg@mail.gmail.com>
2021-05-21 19:02 ` Fwd: GSoC Intro - TUI interface for QMP Niteesh G. S.
2021-05-24 13:32 ` Stefan Hajnoczi
2021-05-24 17:34 ` John Snow
2021-06-02 11:08 ` Bruno Piazera Larsen
2021-06-11 14:06 ` Vladimir Sementsov-Ogievskiy via
2021-05-26 15:35 ` Niteesh G. S. [this message]
2021-06-01 23:47 ` John Snow
2021-06-08 15:01 ` Markus Armbruster
2021-06-08 15:49 ` John Snow
2021-06-09 11:56 ` Markus Armbruster
2021-06-09 17:06 ` John Snow
2021-06-10 7:19 ` Markus Armbruster
2021-06-09 12:07 ` Daniel P. Berrangé
2021-06-10 14:35 ` John Snow
2021-06-09 12:03 ` Daniel P. Berrangé
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.