From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Use less horizontal space in source window
Date: Tue, 20 Aug 2019 22:28:00 -0000 [thread overview]
Message-ID: <87mug3iidt.fsf@tromey.com> (raw)
In-Reply-To: <b28959b8-e248-17b2-5669-b21ae81f5725@redhat.com> (Pedro Alves's message of "Fri, 16 Aug 2019 14:55:09 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> I tried this out a bit, and IMHO the experience is worse than before, given
Pedro> the left/right shifting when stepping as you move between source files.
Thanks for giving it a try.
BTW, normally I remember to push branches to github, so it's often easy
to try them by fetching and checking out the appropriate branch. At
least, I find this simpler than applying patches from email.
Pedro> I'd probably be fine with reducing the width if we still had a reasonable
Pedro> minimum that is enough to fit reasonably-sized source files. I think that
Pedro> if we change this, we should also have more than one space between the line
Pedro> number and the source though. One single space as in your patch makes it harder
Pedro> to distinguish between what is a line and the source IMO. More so with
Pedro> styling disabled.
Good points. And about the styling -- I try never to have it off any
more, so I didn't notice that.
Pedro> I have to say that I find it a bit odd to be optimizing the horizontal space,
Pedro> since the sources I debug (gdb!) mostly wrap around 80 cols, and my terminal
Pedro> is usually much larger than that, so I always have tons of empty space
Pedro> on the right side of the source window.
I often (but not always) have an 80 column terminal, so when I have
debugged gdb, it's still made a bit of difference sometimes.
Tom
prev parent reply other threads:[~2019-08-20 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 2:36 Tom Tromey
2019-08-16 13:55 ` Pedro Alves
2019-08-19 12:09 ` Ruslan Kabatsayev
2019-08-20 22:27 ` Tom Tromey
2019-08-20 22:28 ` Tom Tromey [this message]
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=87mug3iidt.fsf@tromey.com \
--to=tom@tromey.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