From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 66604@debbugs.gnu.org
Subject: bug#66604: [PATCH] Gud LLDB completions
Date: Fri, 20 Oct 2023 08:04:51 +0200 [thread overview]
Message-ID: <m2ttqlq16k.fsf@Pro.fritz.box> (raw)
In-Reply-To: <22B5EBE2-945E-413F-BCC6-8693AB90988C@gmail.com> ("Mattias Engdegård"'s message of "Thu, 19 Oct 2023 15:22:34 +0200")
Mattias Engdegård <mattias.engdegard@gmail.com> writes:
> 19 okt. 2023 kl. 15.08 skrev Gerd Möllmann <gerd.moellmann@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.
next prev parent reply other threads:[~2023-10-20 6:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 11:25 bug#66604: [PATCH] Gud LLDB completions Gerd Möllmann
2023-10-18 13:37 ` Mattias Engdegård
2023-10-18 14:42 ` Gerd Möllmann
2023-10-18 15:14 ` Mattias Engdegård
2023-10-18 15:23 ` Gerd Möllmann
2023-10-18 16:05 ` Mattias Engdegård
2023-10-18 16:57 ` Gerd Möllmann
2023-10-18 18:55 ` Gerd Möllmann
2023-10-19 10:34 ` Mattias Engdegård
2023-10-19 10:48 ` Gerd Möllmann
2023-10-19 11:36 ` Mattias Engdegård
2023-10-19 11:50 ` Gerd Möllmann
2023-10-19 12:29 ` Mattias Engdegård
2023-10-19 13:08 ` Gerd Möllmann
2023-10-19 13:22 ` Mattias Engdegård
2023-10-20 6:04 ` Gerd Möllmann [this message]
2023-10-20 10:42 ` Mattias Engdegård
2023-10-20 11:12 ` Gerd Möllmann
2023-10-20 11:50 ` Mattias Engdegård
2023-10-20 11:59 ` Gerd Möllmann
2023-10-20 17:28 ` Gerd Möllmann
2023-10-20 17:47 ` Gerd Möllmann
2023-10-21 10:32 ` Gerd Möllmann
2023-10-21 10:51 ` Mattias Engdegård
2023-10-21 12:33 ` Gerd Möllmann
2023-10-21 10:37 ` Mattias Engdegård
2023-10-21 10:50 ` Gerd Möllmann
2023-10-23 5:31 ` Gerd Möllmann
2023-10-23 17:18 ` Mattias Engdegård
2023-10-23 17:57 ` Gerd Möllmann
2023-10-23 20:51 ` Mattias Engdegård
2023-10-24 4:35 ` Gerd Möllmann
2023-10-24 8:47 ` Mattias Engdegård
2023-10-24 8:52 ` Gerd Möllmann
2023-10-24 10:00 ` Mattias Engdegård
2023-10-24 10:27 ` Gerd Möllmann
2023-10-24 18:12 ` Mattias Engdegård
2023-10-25 4:29 ` Gerd Möllmann
2023-10-18 15:24 ` Gerd Möllmann
2023-10-19 6:31 ` Visuwesh
2023-10-19 6:56 ` Gerd Möllmann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ttqlq16k.fsf@Pro.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=66604@debbugs.gnu.org \
--cc=mattias.engdegard@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).