From: Tom Tromey <tom@tromey.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH htdocs] links: use to avoid breaking
Date: Mon, 11 Dec 2023 09:53:42 -0700 [thread overview]
Message-ID: <87ttooel49.fsf@tromey.com> (raw)
In-Reply-To: <20231211022903.20869-1-vapier@gentoo.org> (Mike Frysinger's message of "Sun, 10 Dec 2023 19:29:03 -0700")
>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
Mike> On wide screens this isn't noticable, but on smaller devices, the
Mike> line wrapping of links looks weird and is hard to read. Use nbsp
Mike> to make sure we never break a link across a line.
Makes sense, thank you.
Tom
prev parent reply other threads:[~2023-12-11 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 2:29 Mike Frysinger
2023-12-11 16:53 ` 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=87ttooel49.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).