From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: slyfox@gentoo.org, tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/configure.ac: add --enable-source-highlight
Date: Mon, 18 Mar 2019 17:10:00 -0000 [thread overview]
Message-ID: <875zsgp0ra.fsf@redhat.com> (raw)
In-Reply-To: <834l80w2r6.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 18 Mar 2019 18:45:01 +0200")
On Monday, March 18 2019, Eli Zaretskii wrote:
>> From: Sergio Durigan Junior <sergiodj@redhat.com>
>> Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
>> Date: Sun, 17 Mar 2019 23:52:51 -0400
>>
>> Something Keith and I were talking about the other day is adding a
>> command line switch to enable/disable source highlight, so the user can
>> do:
>>
>> gdb --disable-source-highlight ...
>>
>> (or some such)
>
> We already have a variable, which you can set from your ~/.gdbinit,
> isn't that enough?
In my experience as a GDB user, it is. But I'm thinking about people
who, for some reason, wouldn't like to keep (or don't know about) a
~/.gdbinit, and would like to disable the feature from the start. It's
more convenient for the user to do:
gdb --disable-source-highlight ...
(The parameter could be named in a different, more concise way, of
course)
than to do:
echo 'set style source off' >> ~/.gdbinit
gdb ...
or:
gdb -ex 'set style source off' ...
(IME, it's common for a user to not know about -ex)
But anyway, I don't want to bikeshed over this. If it's a hard thing to
do, I'm totally fine with keeping things as is.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-03-18 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 21:50 Sergei Trofimovich
2019-03-15 14:18 ` Tom Tromey
2019-03-17 22:47 ` Sergei Trofimovich
2019-03-17 22:48 ` [PATCH v2] " Sergei Trofimovich
2019-04-19 20:09 ` Tom Tromey
2019-03-18 3:52 ` [PATCH] " Sergio Durigan Junior
2019-03-18 16:02 ` Tom Tromey
2019-03-18 16:45 ` Eli Zaretskii
2019-03-18 17:10 ` Sergio Durigan Junior [this message]
2019-03-18 17:56 ` Eli Zaretskii
2019-03-18 16:01 ` 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=875zsgp0ra.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=slyfox@gentoo.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