From: Tom Tromey <tom@tromey.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH htdocs] tighten up margins on smaller devices
Date: Fri, 22 Dec 2023 08:50:41 -0700 [thread overview]
Message-ID: <87a5q22q3y.fsf@tromey.com> (raw)
In-Reply-To: <20231216021029.22184-1-vapier@gentoo.org> (Mike Frysinger's message of "Fri, 15 Dec 2023 21:10:29 -0500")
>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
Mike> Scale down the font size and margins on headers on smaller devices.
Mike> The defaults cause the GDB title to take up most of the screen, and
Mike> then the links & page intro take up the rest. Scale down the font
Mike> so that it's still relatively larger, and tighten up the margins.
Mike> The content is still comfortably readable.
Mike> Similarly, tighten the spacing on lists -- the default can quickly
Mike> suck up horizontal space. The result is still clear how things are
Mike> broken up, but given more space for reading content.
Seems fine to me fwiw.
Tom
prev parent reply other threads:[~2023-12-22 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 2:10 Mike Frysinger
2023-12-22 15:50 ` 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=87a5q22q3y.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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).