Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Make startup message more user friendly
Date: Wed, 15 Oct 2025 12:17:33 -0300	[thread overview]
Message-ID: <72f878e9-0f10-480c-b32b-28171bf8e7a4@redhat.com> (raw)
In-Reply-To: <87y0piwmbr.fsf@tromey.com>

On 10/10/25 5:09 PM, Tom Tromey wrote:
>>>>>> "Guinevere" == Guinevere Larsen <guinevere@redhat.com> writes:
> Guinevere> This commit attempts to make the startup message more friendly to new
> Guinevere> users by using ascii art separators.  If there is enough space availabe,
> Guinevere> an ascii art box is printed containing the hints, otherwise a simple
> Guinevere> separator is printed.  The code deems "enough space available" when
> Guinevere> there is enough space to print the documentation URL inside the box,
> Guinevere> since the other hints will be broken into multiple lines if necessary.
> Guinevere> Here are examples of the 2 possible startups, with enough space:
>
> If emojis_ok() then it seems like this could use Unicode line drawing
> instead.

I just tested this out and after I managed to get it working, I tested 
by adding "set style emoji off", and turns out this is printed before 
gdbinit is read, meaning a user can't disable it themselves. I 
personally think this is a really good improvement, but I can see this 
being a nuisance for users in terminals that support UTF-8 but the user 
themself doesn't like it.

What do you think? Should I add it anyway?

-- 
Cheers,
Guinevere Larsen
It/she


  parent reply	other threads:[~2025-10-15 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 16:39 Guinevere Larsen
2025-10-10 20:09 ` Tom Tromey
2025-10-13 20:30   ` Guinevere Larsen
2025-10-15 15:17   ` Guinevere Larsen [this message]
2025-10-15 16:54     ` Tom Tromey
2025-10-15 17:07       ` Guinevere Larsen
2025-10-15 20:30         ` Tom Tromey
2025-10-17 14:10         ` Andrew Burgess

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=72f878e9-0f10-480c-b32b-28171bf8e7a4@redhat.com \
    --to=guinevere@redhat.com \
    --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