From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Florian Weimer <fw@deneb.enyo.de>,
Allan Sandfeld Jensen <linux@carewolf.com>
Cc: gcc@gcc.gnu.org, Jonathan Wakely <jwakely@redhat.com>,
libstdc++@gcc.gnu.org
Subject: Re: [RFC] Increase libstdc++ line length to 100(?) columns
Date: Thu, 3 Dec 2020 12:11:48 +0000 [thread overview]
Message-ID: <2e234320-108c-7784-df03-d5a2fc214b73@foss.arm.com> (raw)
In-Reply-To: <874kl8aws8.fsf@mid.deneb.enyo.de>
On 29/11/2020 17:38, Florian Weimer wrote:
> * Allan Sandfeld Jensen:
>
>> If you _do_ change it. I would suggest changing it to 120, which is next
>> common step for a lot of C++ projects.
>
> 120 can be problematic for a full HD screen in portrait mode. Nine
> pixels per character is not a lot (it's what VGA used), and you can't
> have any window decoration. With a good font and screen, it's doable.
> But if the screen isn't quite sharp, then I think you wouldn't be able
> to use portrait mode anymore.
>
Please remember that not everyone has 20:20 vision. Requiring a
terminal width that's so large that the text is wrapped (or, worse, you
get horizontal scroll bars) is not acceptable, IMO.
R.
next prev parent reply other threads:[~2020-12-03 12:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 23:50 Jonathan Wakely
2020-11-27 2:45 ` Liu Hao
2020-11-27 8:14 ` Richard Biener
2020-11-27 8:21 ` Ville Voutilainen
2020-11-27 9:49 ` Liu Hao
2020-11-27 10:13 ` Ville Voutilainen
2020-11-27 11:08 ` Allan Sandfeld Jensen
2020-11-29 17:38 ` Florian Weimer
2020-11-29 18:51 ` Allan Sandfeld Jensen
2020-11-30 15:47 ` Michael Matz
2020-11-30 16:28 ` Allan Sandfeld Jensen
2020-11-30 16:44 ` Michael Matz
2020-12-03 12:11 ` Richard Earnshaw [this message]
2020-11-27 21:46 ` Ed Smith-Rowland
2020-11-28 12:16 ` Thomas Koenig
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=2e234320-108c-7784-df03-d5a2fc214b73@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=linux@carewolf.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).