From: Eli Zaretskii <eliz@gnu.org>
To: Diancheng Wang <diancheng_wang@163.com>
Cc: 74642@debbugs.gnu.org
Subject: bug#74642: 31.0.50; [Patch] Turn off current source line indicator when gdb buffer is killed
Date: Tue, 03 Dec 2024 14:32:57 +0200 [thread overview]
Message-ID: <86ed2p2bgm.fsf@gnu.org> (raw)
In-Reply-To: <87ldwxy11t.fsf@163.com> (message from Diancheng Wang on Tue, 03 Dec 2024 10:04:30 +0800)
> From: Diancheng Wang <diancheng_wang@163.com>
> Cc: 74642@debbugs.gnu.org
> Date: Tue, 03 Dec 2024 10:04:30 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks, but can you please describe the scenario in which the
> > indicator is not removed? I guess I don't really understand what you
> > mean by "gdb buffer is killed": what I tried is simply end the
> > debugging session by typing "q RET" at the GDB prompt. And that
> > removed the indicator.
>
> Hi,
>
> Sorry for confusing. I mean killing GDB interactive buffer directly by
> typing "C-k RET" when gdb is stopped on a source line. The indicator is
> not removed.
I guess you mean "C-x k RET"?
When I do that, Emacs asks me whether to kill the process associated
with the buffer, and if I say YES, the indicator does disappear
(sometimes after a second, which I guess is needed for Emacs to kill
the process). Isn't that what you see?
next prev parent reply other threads:[~2024-12-03 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 7:04 bug#74642: 31.0.50; [Patch] Turn off current source line indicator when gdb buffer is killed Diancheng Wang
2024-12-02 13:17 ` Eli Zaretskii
2024-12-03 2:04 ` Diancheng Wang
2024-12-03 12:32 ` Eli Zaretskii [this message]
2024-12-04 8:22 ` Diancheng Wang
2024-12-04 13:41 ` Eli Zaretskii
2024-12-04 19:11 ` Eli Zaretskii
2024-12-05 7:34 ` Diancheng Wang
2024-12-05 7:55 ` Eli Zaretskii
2024-12-05 8:37 ` Diancheng Wang
2024-12-07 13:25 ` Eli Zaretskii
2024-12-09 1:27 ` bug#74642: " diancheng_wang
2024-12-12 10:47 ` Eli Zaretskii
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=86ed2p2bgm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74642@debbugs.gnu.org \
--cc=diancheng_wang@163.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.