GNU bug report logs -
#66604
[PATCH] Gud LLDB completions
Previous Next
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
Mattias Engdegård <mattias.engdegard <at> gmail.com> writes:
> 19 okt. 2023 kl. 15.08 skrev Gerd Möllmann <gerd.moellmann <at> gmail.com>:
>
>> Could you
>> please set completion-at-point-functions to nil in the lldb buffer, and
>> see if that's also happening then?
>
> Yes, that does not seem to affect the output at all.
I don't seem to be able to reproduce this with emacs -Q.
Here is what I do:
cd emacs/master/src
,/emacs -Q # this is a build with -O0 -g
M-x lldb RET emacs RET
In gud-emacs:
b redisplay_internal
r -Q
then 'n', 'c' and so on. Does that look right?
That's on an M1 mac, BTW. Can't try on my x86_64 mac because lldb
doesn't work there after the OCLP update to maxOS 14. I'm mentioning
this because machine speed might matter in the communication emacs <->
lldb. What machine are you using?
Could you try with a newer lldb? (brew install llvm, for example).
P.S., just FYI, since you seem to be using this, and might see it:
- There is still a problem with things like Corfu + invoking
completion-at-point manually. This is interfering with comint
redirection, with the effect of printing completions to the gud buffer.
- There is a problem with the code in master if completion candidates
contain ')', like function names. I have fixed that here.
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.