From: Keith Seitz <keiths@redhat.com>
To: Simon Sobisch <simonsobisch@web.de>, insight@sourceware.org
Subject: Re: Insight and syntax highlighting
Date: Fri, 29 Jul 2022 13:33:16 -0700 [thread overview]
Message-ID: <223eee35-8da0-ca77-6fe6-617aab23c390@redhat.com> (raw)
In-Reply-To: <90d025b9-ab15-b1cc-b573-beaf6ab3ca62@web.de>
On 7/28/22 07:01, Simon Sobisch via Insight wrote:
> GDB has quite nice syntax highlighting on the command line, either (very
> seldom used) via GNU Source-highlight or via python pygments now.
>
> Given the Insight documentation [1] it looks there isn't any feature
> like that yet in Insight - is it?
No, there isn't. All of the CLI-like functionality is independently
implemented in Insight. It does not (AFAIK) use a terminal to provide
CLI support.
> It would be nice to have diassembler and source output highlighted.
It would indeed! IIRC, someone submitted a patch to do source highlighting,
but they reneged when asked to "sign" the license agreement. [This isn't
required by Red Hat legal anymore.] Man, that must have been over ten
years ago. [about when I really stopped working on Insight]
Keith
prev parent reply other threads:[~2022-07-29 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 14:01 Simon Sobisch
2022-07-29 20:33 ` Keith Seitz [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=223eee35-8da0-ca77-6fe6-617aab23c390@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=simonsobisch@web.de \
/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).