GNU bug report logs - #66604
[PATCH] Gud LLDB completions

Previous Next

Package: emacs;

Reported by: Gerd Möllmann <gerd.moellmann <at> gmail.com>

Date: Wed, 18 Oct 2023 11:27:02 UTC

Severity: normal

Tags: patch

Fixed in version 30.1

Done: Gerd Möllmann <gerd.moellmann <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Mattias Engdegård <mattias.engdegard <at> gmail.com>
Cc: 66604 <at> debbugs.gnu.org
Subject: bug#66604: [PATCH] Gud LLDB completions
Date: Wed, 18 Oct 2023 18:57:44 +0200
[Message part 1 (text/plain, inline)]
Mattias Engdegård <mattias.engdegard <at> gmail.com> writes:

> 18 okt. 2023 kl. 17.23 skrev Gerd Möllmann <gerd.moellmann <at> gmail.com>:
>
>> Does the attached also work?  It would have the advantage of being more
>> readable.  The Python part.
>
> Yes, it works.
> A minor request is that if there is only a single completion, then a space should be added after completing the word. For example,
>
>   (lldb) sett<TAB>
>
> should add the 5 characters "ings " to the input.

Yeah, that's right.

Could ypu please try the attached patch?  This of works for me, but a
bit unnerving its that Corfu pops up after tryping 3 character with a
single candidate, but that's something I can live with, I guess.  Maybe
it's even normal, now that i think of it.

What completion are you using?

[0001-Gud-LLDB-completions-bug-66604.patch (text/x-patch, attachment)]

This bug report was last modified 1 year and 211 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.