public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: gdb@sourceware.org
Subject: Annotations, level 2
Date: Fri, 13 Apr 2012 11:20:00 -0000	[thread overview]
Message-ID: <4F880BF3.1050405@redhat.com> (raw)


Hi all,

For the last while I have been working on bringing the concept of
Frame filters to the Python API.  This has been going super.  However
in "print_frame_info", annotations are attached to the printed frame
sub-sections -- but only if annotations are set to "2".

To my knowledge, emacs is the only user "I know about" that still uses
annotations, and it uses level "3".

Ordinarily, this would not be a problem, but the annotation call for
the beginning of frame printing requires a frame architecture.  This
spoils the abstract notion of Frame filters (frame filters can wrap a
frame, or just simulate one).  I could probably mock up a dummy-frame,
but I got to be thinking, is it worth that effort?  I don't think so.

These annotations are only exposed to level 2, and after (an
admittedly brief) search, I can no find no product or project that
uses annotations beyond emacs.  As the annotation calls for frames is
exclusively "2" (IE, == 2), and, as far as I can tell, emacs does not use
these markups.

So what's the approach here?  Do I have to support it just because it
is there?

Cheers,

Phil

             reply	other threads:[~2012-04-13 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 11:20 Phil Muldoon [this message]
2012-04-13 12:16 ` Pedro Alves
2012-04-13 12:56   ` Phil Muldoon
2012-04-13 12:46 ` Joel Brobecker

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=4F880BF3.1050405@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=gdb@sourceware.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.
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).