From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] Suppress repeated annotations until GDB is ready to accept input.
Date: Tue, 27 Nov 2012 18:48:00 -0000 [thread overview]
Message-ID: <87sj7udgrj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <50B3B4BC.2010108@redhat.com> (Pedro Alves's message of "Mon, 26 Nov 2012 18:28:12 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Hmm. There's potential for making it worse. The patch
Pedro> suppresses duplicate annotations until the next prompt is
Pedro> displayed. With background commands, events can be reported
Pedro> without re-displaying a prompt [*]. In that case, emacs might
Pedro> miss annotations.
FWIW, I am not sure this is so very bad.
Async is still an advanced user thing.
And, if Emacs gets out of sync it is simple to do "up;down" or the like
to get back in sync.
Pedro> With this version, we don't do annotation suppression if a background
Pedro> command is in progress. This means that
Pedro> define twobreaks
Pedro> b foo
Pedro> b bar
Pedro> end
Pedro> twobreaks
Pedro> triggers two annotations in async mode if the target is not
Pedro> running, or isn't running the foreground, while always just one
Pedro> in sync mode. I don't think that's a real problem.
Me neither. It isn't even clear Emacs does anything with those
annotations at all.
Pedro> [*] - though that could itself be considered a bug, the CLI
Pedro> output is less than ideal here. We should be able to keep the
Pedro> bottom line reserved for the prompt, and scroll the rest of the
Pedro> output without visually interfering with the prompt line. E.g.,
Pedro> we could be able to unwind the cursor to column 0, print whatever
Pedro> while handling the event, and then redisplay the prompt as it
Pedro> was, without the user noticing. Or perhaps there's cleaner ways
Pedro> even.
Do you mean, do this in Emacs or for the CLI itself?
Either way I think it would be nice. I've often wished we could replace
the "Reading..." messages, which are often illegible, with some kind of
nicer hash progress meter thing ...
Pedro> Is there any way to force emacs 24 to do full annotations? It actually
Pedro> hadn't realized that "--fullname" was annotate=1, not 2, so my previous
Pedro> emacs testing was useless, as these notifications only happen with
Pedro> annotate=2...
I don't think there is. When I tried just editing the gdb command line
I ended up with a lot of "^Z^Z" in the gud buffer. I guess you could
dig up Emacs 23 (still in F16...) or try to downgrade the gud code.
Tom
next prev parent reply other threads:[~2012-11-27 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50ACF672.7060607@redhat.com>
2012-11-21 20:14 ` [PATCH 0/4] Misc annotations changes Pedro Alves
2012-11-21 20:14 ` [PATCH 1/4] Remove (alleged) "breakpoints-changed" annotation suppression on ignore count changes Pedro Alves
2012-11-21 20:14 ` [PATCH 2/4] Suppress repeated annotations until GDB is ready to accept input Pedro Alves
2012-11-26 15:50 ` Tom Tromey
2012-11-26 18:28 ` Pedro Alves
2012-11-27 18:48 ` Tom Tromey [this message]
2012-11-27 23:53 ` Pedro Alves
2013-01-22 19:59 ` Pedro Alves
2012-11-27 18:56 ` Eli Zaretskii
2012-11-21 20:14 ` [PATCH 4/4] Skip breakpoints-invalid annotations for internal|momentary breakpoints Pedro Alves
2012-11-21 20:14 ` [PATCH 3/4] Fully move the breakpoints-invalid annotation to observers Pedro Alves
2012-11-26 15:23 ` Tom Tromey
2012-11-26 15:42 ` [PATCH 0/4] Misc annotations changes Tom Tromey
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=87sj7udgrj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox