From: "Maciej W. Rozycki" <macro@wdc.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Tom Tromey <tom@tromey.com>, Tom Tromey <tromey@sourceware.org>,
gdb-patches@sourceware.org
Subject: Re: [binutils-gdb] Style the gdb welcome message
Date: Sat, 19 Oct 2019 11:21:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.21.1910191203350.2438@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <20191015083234.GT4962@embecosm.com>
On Tue, 15 Oct 2019, Andrew Burgess wrote:
> > I'm curious to hear what others think. In the absence of comments I'll
> > remove it sometime before 9.1, I think. Or I'll approve a patch to
> > do so.
>
> What this might mean is that if ~/.gdbinit contains only (or starts
> with) commands that produce no output, for example 'set style enabled
> off' then these would be processed before GDB printed the welcome
> message.
Thank you all who responded for your input.
As this is a matter of a human interface I realise that personal
perception will be very different among various people, from positive,
through neutral to disturbing. The classic single-colour interface is
uniform and does not, in my personal experience, cause any disturbance
or distraction to me. Other people may appreciate the highlighting.
I think a way to move forward might be to borrow from other GNU
projects, such as GCC and coreutils, and have an environment variable
defined called GDB_COLORS, analogously to GCC_COLORS or LS_COLORS, and
make GDB interpret it ahead of its usual initialisation files (which
could optionally override the environment settings).
Thoughts?
Maciej
prev parent reply other threads:[~2019-10-19 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181228210008.91892.qmail@sourceware.org>
2019-10-04 22:15 ` Maciej W. Rozycki
2019-10-14 22:45 ` Tom Tromey
2019-10-15 6:32 ` Eli Zaretskii
2019-10-15 8:32 ` Andrew Burgess
2019-10-19 11:21 ` Maciej W. Rozycki [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=alpine.LFD.2.21.1910191203350.2438@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
--cc=tromey@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).