Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add completion styling
Date: Sat, 16 May 2020 22:25:10 +0300	[thread overview]
Message-ID: <83367zd6nd.fsf@gnu.org> (raw)
In-Reply-To: <87y2pr663s.fsf@tromey.com> (message from Tom Tromey on Sat, 16 May 2020 13:18:47 -0600)

> From: Tom Tromey <tom@tromey.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  gdb-patches@sourceware.org
> Date: Sat, 16 May 2020 13:18:47 -0600
> 
> commit 0af816c447b989a47494b3b1ff970b463b100152
> Author: Tom Tromey <tom@tromey.com>
> Date:   Sat May 16 13:17:33 2020 -0600
> 
>     Add completion styling
>     
>     Readline has a styling feature for completion -- if it is enabled, the
>     common prefix of completions will be displayed in a different style.
>     This doesn't work in gdb, because gdb implements its own completer.
>     
>     This patch implements the feature.  However, it doesn't directly use
>     the Readline feature, because gdb can do a bit better: it can let the
>     user control the styling using the existing mechanisms.
>     
>     This version incorporates an Emacs idea, via Eli: style the prefix,
>     the "difference character", and the suffix differently.
>     
>     gdb/ChangeLog
>     2020-05-16  Tom Tromey  <tom@tromey.com>
>     
>             * NEWS: Add entry for completion styling.
>             * completer.c (_rl_completion_prefix_display_length): Move
>             declaration earlier.
>             (gdb_fnprint): Use completion_style.
>             (gdb_display_match_list_1): Likewise.
>             * cli/cli-style.c (completion_prefix_style)
>             (completion_difference_style, completion_suffix_style): New
>             globals.
>             (_initialize_cli_style): Register new globals.
>             * cli/cli-style.h (completion_prefix_style)
>             (completion_difference_style, completion_suffix_style): Declare.
>     
>     gdb/doc/ChangeLog
>     2020-05-16  Tom Tromey  <tom@tromey.com>
>     
>             * gdb.texinfo (Output Styling): Mention completion styling.
>             (Editing): Mention readline completion styling.
>     
>     gdb/testsuite/ChangeLog
>     2020-05-16  Tom Tromey  <tom@tromey.com>
>     
>             * gdb.base/style.exp: Add completion styling test.
>             * lib/gdb-utils.exp (style): Add completion styles.
> 

Thanks, the documentation parts are okay.


  reply	other threads:[~2020-05-16 19:25 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 [this message]
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
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=83367zd6nd.fsf@gnu.org \
    --to=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