public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add completion styling
Date: Sun, 24 May 2020 17:42:46 +0300	[thread overview]
Message-ID: <83a71xxul5.fsf@gnu.org> (raw)
In-Reply-To: <4b370f83-3954-bbc4-50b5-1528e8b4fca5@redhat.com> (message from Pedro Alves on Sun, 24 May 2020 13:58:02 +0100)

> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Sun, 24 May 2020 13:58:02 +0100
> 
> Try "b main[TAB]" when debugging GDB, and you'll see that GDB
> highlights the "t" as the first different character here:
> 
> selftests::string_view::cons_1::main()
> selftests::string_view::cons_2::main()
> selftests::string_view::cons_3::main()
>     ^
> 
> while it should highlight here:
> 
> selftests::string_view::cons_1::main()
> selftests::string_view::cons_2::main()
> selftests::string_view::cons_3::main()
>                                     ^

Really? not here:

 selftests::string_view::cons_1::main()
                              ^

But I actually don't understand how did we get these candidates by
typing "main".  Don't we complete by looking for strings that begin
with what the user typed?  I'm probably missing something here.

  reply	other threads:[~2020-05-24 14:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09  2:41 Tom Tromey
2020-04-09  6:39 ` Eli Zaretskii
2020-04-24 19:51   ` Tom Tromey
2020-04-24 20:00     ` Eli Zaretskii
2020-04-24 20:37       ` Tom Tromey
2020-05-16 19:18     ` Tom Tromey
2020-05-16 19:25       ` Eli Zaretskii
2020-05-23 20:52       ` Tom Tromey
2020-05-23 21:48         ` Philippe Waroquiers
2020-05-24  0:26         ` Hannes Domani
2020-05-24 10:16         ` Tom de Vries
2020-05-25  8:06           ` Tom de Vries
2020-05-24 14:54         ` Tom Tromey
2020-05-24 12:58     ` Pedro Alves
2020-05-24 14:42       ` Eli Zaretskii [this message]
2020-05-24 15:30         ` Pedro Alves
2020-05-24 16:29           ` Eli Zaretskii
2020-05-24 16:44             ` Pedro Alves

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=83a71xxul5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).