unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gustaf Waldemarson <gustaf.waldemarson@gmail.com>
To: 34589@debbugs.gnu.org
Subject: bug#34589: 26.1.91; GDB-MI Display Complex Data Types
Date: Tue, 5 Nov 2019 11:05:48 +0100	[thread overview]
Message-ID: <CABehr5eX5KDVNcV9cXMNdzdW7t5U3QpcRghAXJ8J_j_dmT1sXg@mail.gmail.com> (raw)
In-Reply-To: <83va0tag67.fsf@gnu.org>

Hello,

After quite some time here, I have finally been able to get the proper
legal confirmation from Arm to submit patches. As far as I understand
things, any patch that I submit for Emacs will now have the copyright
correctly reassigned and should now be usable without any issues.

That said, during these months I've been rethinking the variable GDB
window somewhat, and would like to see what people thinks of a rework of
the following kind:

- Instead of displaying variables as | 'type' | 'name' | 'value' |,
  display them as | 'name' | 'short-type' | 'value' |, where
  'short-type' is the first `X' characters of the type name.

  I personally find this to be more useful, especially for C++ template
  types which can easily occupy the whole window otherwise.

- Possibly add a new tab 'behind' the variable window which contains the
  /full/ type name. (This part may also have to interface with the new
  tabbing interface, something I'll have to look into when I've got some
  time.)

(Also, if interesting, should this kind of rework be submitted as a
separate ticket?)

Den fre 8 mars 2019 kl 10:07 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > From: Gustaf Waldemarson <gustaf.waldemarson@gmail.com>
> > Date: Mon, 4 Mar 2019 09:05:26 +0100
> > Cc: 34589@debbugs.gnu.org, "Andrew W. Nosenko" <andrew.w.nosenko@gmail.com>,
> >       Robert Pluim <rpluim@gmail.com>, rms@gnu.org
> >
> > >Yes.  I asked about the first patch because it's small enough to be
> > > accepted even without legal paperwork.  The second one exceeds the
> > > limits of that.
> >
> > Ah, got it. Feel free to review and include it if you find it useful.
>
> Thanks.  Unfortunately, it turns out that the first patch makes little
> sense without the second, as most of the code modified by the former
> is introduced in the latter.  So I didn't apply any of your changes
> for now; hopefully, you will be able to overcome the legal obstacles
> at some point.





  reply	other threads:[~2019-11-05 10:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 10:08 bug#34589: 26.1.91; GDB-MI Display Complex Data Types Gustaf Waldemarson
2019-02-20 17:16 ` Eli Zaretskii
2019-02-21 13:42   ` Gustaf Waldemarson
2019-02-23  9:40     ` Eli Zaretskii
2019-02-23 10:01       ` Gustaf Waldemarson
2019-02-23 10:36         ` Eli Zaretskii
2019-02-28 16:05           ` Gustaf Waldemarson
2019-02-28 17:24             ` Andrew W. Nosenko
2019-02-28 17:58             ` Eli Zaretskii
2019-03-01  3:57             ` Richard Stallman
2019-03-02  3:28             ` Richard Stallman
2019-03-03 20:32               ` Gustaf Waldemarson
2019-03-04  3:30                 ` Eli Zaretskii
2019-03-04  8:05                   ` Gustaf Waldemarson
2019-03-08  9:06                     ` Eli Zaretskii
2019-11-05 10:05                       ` Gustaf Waldemarson [this message]
2020-09-30 18:08                         ` Lars Ingebrigtsen
2020-09-30 18:30                           ` Eli Zaretskii
2020-04-15 14:54 ` Yuan Fu
2020-04-15 15:05   ` Eli Zaretskii
2022-03-06 20:39 ` William Xu
2022-03-06 20:44 ` William Xu
2022-03-06 20:46 ` Weilin Xu
2022-03-06 21:56   ` Lars Ingebrigtsen
2022-03-06 22:33     ` William Xu
2022-03-06 23:02       ` Lars Ingebrigtsen
2022-03-07  9:27         ` William Xu

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=CABehr5eX5KDVNcV9cXMNdzdW7t5U3QpcRghAXJ8J_j_dmT1sXg@mail.gmail.com \
    --to=gustaf.waldemarson@gmail.com \
    --cc=34589@debbugs.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).