From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: static linking of gdb
Date: Sun, 5 Apr 2020 16:56:13 +0200 [thread overview]
Message-ID: <AM6PR03MB5170986D7836F817C13A9883E4C50@AM6PR03MB5170.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <83369it3p4.fsf@gnu.org>
On 4/5/20 4:19 PM, Eli Zaretskii wrote:
>> Cc: gdb-patches@sourceware.org, tom@tromey.com
>> From: Bernd Edlinger <bernd.edlinger@hotmail.de>
>> Date: Sun, 5 Apr 2020 15:48:09 +0200
>>
>> Can someone explain to me why gdbserver needs source highlight?
>
> It provides syntax highlighting of the source displayed by GDB.
>
Hmm,
from a pragmatic POV, may I ask, why we do not simply change the
default of
--with-static-standard-libraries --disable-source-highlight
I do not even miss a highlight in gdb and certainly not
in gdbserver, the software is just extremely good as is ;-)
... I just learned recently about backward step, wow ...
I mean the default should just work,
if someone wants some more highlight, then they should just
add --enable-source-highlight
and if that is necessary, do additionally
--without-static-standard-libraries
What do you think?
Bernd.
next prev parent reply other threads:[~2020-04-05 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 10:13 Bernd Edlinger
2020-04-05 13:17 ` Eli Zaretskii
2020-04-05 13:23 ` Bernd Edlinger
2020-04-05 13:48 ` Bernd Edlinger
2020-04-05 14:19 ` Eli Zaretskii
2020-04-05 14:56 ` Bernd Edlinger [this message]
2020-04-06 3:27 ` Bernd Edlinger
2020-04-06 7:14 ` Bernd Edlinger
2020-04-06 13:43 ` Tom Tromey
2020-04-06 13:42 ` Tom Tromey
2020-04-06 13:45 ` Bernd Edlinger
2020-04-06 14:11 ` Tom Tromey
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=AM6PR03MB5170986D7836F817C13A9883E4C50@AM6PR03MB5170.eurprd03.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=eliz@gnu.org \
--cc=gdb-patches@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