Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedro@codesourcery.com (Pedro Alves)
Cc: gdb-patches@sourceware.org, bauerman@br.ibm.com (Thiago Jung Bauermann)
Subject: Re: [rfc] More intelligent indenting of multi-line table entries (Re: [RFA] Implement support for PowerPC BookE ranged breakpoin
Date: Mon, 28 Feb 2011 15:33:00 -0000	[thread overview]
Message-ID: <201102281523.p1SFNDdE022526@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <201102251444.17070.pedro@codesourcery.com> from "Pedro Alves" at Feb 25, 2011 02:44:16 PM

Pedro Alves wrote:
> On Thursday 24 February 2011 20:41:12, Ulrich Weigand wrote:
> > My thought was to remove that redundancy completely, and simply
> > ask the UI table layer for the correct position.  It turns out
> > that this needs some new functionality exported from that layer,
> > but a simply query for the field information you originally
> > passed to that layer suffices.
> >=20
> > The following patch implements this suggestion; it fixes the currently
> > broken indentation and gets rid of the silly arguments to the
> > print_breakpoint_location function.
> >=20
> > Tested on i386-linux and by manual inspection of line wrapping.
> >=20
> > Any comments?
> 
> Looks great to me.

Thanks for the review!  I've checked this in now.
 
> I've mentioned this before, but I think it'd really be nice
> that the table layout support was reworked to be able to auto
> wrap (and size perhaps) columns nicely, =E0 la emacs' org-mode,
> vis:
> 
>  | Num | Name         | What     | Other column |
>  |-----+--------------+----------+--------------|
>  |   1 | foo bar      | foo      | another      |
>  |     |              | bar what | broken       |
>  |     |              |          | sentence     |
>  |-----+--------------+----------+--------------|
>  |   2 | the other    | what?    | yummy        |
> 
> so that all colums would line-break nicely without
> messing their rightmost columns.  (without the guide
> lines, of course).

Yes, ideally the UI table mode should really automatically
lay out the full table.  But right now it seems to be used
interspersed with regular output commands, so getting there
would probably require major changes to the current output
generators ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2011-02-28 15:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28  1:54 [RFA] Implement support for PowerPC BookE ranged breakpoints Thiago Jung Bauermann
2011-01-28  9:39 ` Eli Zaretskii
2011-01-31 19:07   ` Thiago Jung Bauermann
2011-01-31 20:39     ` Eli Zaretskii
2011-02-17 15:49 ` Ulrich Weigand
2011-02-23 20:50   ` Thiago Jung Bauermann
2011-02-24 20:45     ` [rfc] More intelligent indenting of multi-line table entries (Re: [RFA] Implement support for PowerPC BookE ranged breakpoints) Ulrich Weigand
2011-02-25 14:46       ` Pedro Alves
2011-02-28 15:33         ` Ulrich Weigand [this message]
2011-02-28 16:34           ` [commit] Remove unused parameter (Re: [rfc] More intelligent indenting of multi-line table entries) Ulrich Weigand
2011-02-25 15:33       ` [rfc] More intelligent indenting of multi-line table entries (Re: [RFA] Implement support for PowerPC BookE ranged breakpoints) Thiago Jung Bauermann
2011-02-28 17:08     ` [RFA] Implement support for PowerPC BookE ranged breakpoints Ulrich Weigand
2011-03-12  2:03       ` Thiago Jung Bauermann
2011-03-12 16:44         ` Thiago Jung Bauermann
2011-03-14 20:50           ` Ulrich Weigand
2011-03-16  6:07             ` Thiago Jung Bauermann
2011-03-16 18:00               ` Ulrich Weigand
2011-03-14 21:02         ` Ulrich Weigand
2011-03-28 16:50           ` Thiago Jung Bauermann
2011-03-29 13:10             ` Ulrich Weigand
2011-03-31 15:41               ` Thiago Jung Bauermann
2011-03-31 16:04                 ` Thiago Jung Bauermann

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=201102281523.p1SFNDdE022526@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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