From: Ergus <spacibba@aol.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32597@debbugs.gnu.org
Subject: bug#32597: gdb gud-watch speedbar no visible actions
Date: Sat, 01 Sep 2018 16:09:44 +0200 [thread overview]
Message-ID: <0d29df09-26e9-455e-96c4-ae6eda8fbdaa@aol.com> (raw)
In-Reply-To: <83sh2t1g09.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
Yes it happens also with -Q.
When it doesnt happen is in gui mode.
Sent from BlueMail
On 1 Sep 2018, 15:53, at 15:53, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 31 Aug 2018 03:20:24 +0200
>> From: Ergus <spacibba@aol.com>
>>
>>
>> 1) "M-x speedbar" requires to be called twice for the first speedbar
>open. If
>> this is not a bug, it is very weird.
>>
>> 2) Debugging with gdb in emacs a C program I added a gud-watch for a
>struct
>> variable. Going to the speedbar I try to open the struct tree [+]
>with <SPC> but
>> it does nothing (i don't try mouse click because I am in a terminal
>session).
>>
>> - It requires to quit (q) and open the "M-x speedbar" again to show
>the
>> speedbar updated with the tree opened. It opens depends if I pressed
>> <SPC> odd or even times before q.
>>
>> - The opposite (close the tree) works properly without exit needed,
>but I can't
>> open it again (previous explained behavior).
>>
>> - I tried this with -Q option to check that it was not a mistake in
>my
>> configuration.
>>
>> - The speedbar in: "emacs -Q -f speedbar" works fine without this
>issue.
>>
>> - With emacs in gui there is not problem either.
>
>Not sure I understand you correctly: does the last part of your report
>mean that the problem does not happen in "emacs -Q"?
[-- Attachment #2: Type: text/html, Size: 2020 bytes --]
next prev parent reply other threads:[~2018-09-01 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 1:20 bug#32597: gdb gud-watch speedbar no visible actions Ergus
2018-09-01 13:52 ` Eli Zaretskii
2018-09-01 14:09 ` Ergus [this message]
2018-09-01 15:05 ` Eli Zaretskii
2018-09-01 15:08 ` Ergus
2018-09-05 18:12 ` Glenn Morris
2018-09-05 18:22 ` Eli Zaretskii
2022-01-23 13:47 ` Lars Ingebrigtsen
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=0d29df09-26e9-455e-96c4-ae6eda8fbdaa@aol.com \
--to=spacibba@aol.com \
--cc=32597@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).