public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/30966] [gdb/cli] pygments finds language based on file name, source-highlight finds language based on debug info
Date: Wed, 18 Oct 2023 16:57:06 +0000 [thread overview]
Message-ID: <bug-30966-4717-ThiJbDHJTb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30966-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30966
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> (In reply to Tom de Vries from comment #0)
> > Conversely, if gdb can't decide what parser to use for source-highlight, it
> > gives up (and falls back to pygments), even though source-highlight might be
> > able to figure out which parser to use based on the file extension.
>
> See https://www.gnu.org/software/src-highlite/source-highlight-lib.html
> which shows the example ./lib/examples/source-highlight-console-main.cpp
> with this bit:
> ...
> // we have a file name so we detect the input source language
> srchilite::LangMap langMap(DATADIR, "lang.map");
> string lang = langMap.getMappedFileNameFromFileName(argv[1]);
> if (lang != "") {
> inputLang = lang;
> ...
https://sourceware.org/pipermail/gdb-patches/2023-October/203387.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-18 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 7:58 [Bug cli/30966] New: " vries at gcc dot gnu.org
2023-10-12 8:20 ` [Bug cli/30966] " vries at gcc dot gnu.org
2023-10-12 9:18 ` sam at gentoo dot org
2023-10-18 16:57 ` vries at gcc dot gnu.org [this message]
2023-10-20 20:22 ` cvs-commit at gcc dot gnu.org
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=bug-30966-4717-ThiJbDHJTb@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).