From: Michael Matz <matz@suse.de>
To: Allan Sandfeld Jensen <linux@carewolf.com>
Cc: Florian Weimer <fw@deneb.enyo.de>,
gcc@gcc.gnu.org, Jonathan Wakely <jwakely@redhat.com>,
libstdc++@gcc.gnu.org
Subject: Re: [RFC] Increase libstdc++ line length to 100(?) columns
Date: Mon, 30 Nov 2020 16:44:09 +0000 (UTC) [thread overview]
Message-ID: <alpine.LSU.2.20.2011301635050.26979@wotan.suse.de> (raw)
In-Reply-To: <3085848.aeNJFYEL58@twilight>
Hello,
On Mon, 30 Nov 2020, Allan Sandfeld Jensen wrote:
> > > On Sonntag, 29. November 2020 18:38:15 CET 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.
> > >
> > > Using a standard condensed monospace font of 9px, it has a width of 7px,
> > > 120
> > A char width of 7px implies a cell width of at least 8px (so 960px for 120
> > chars), more often of 9px. With your cell width of 7px your characters
> > will be max 6px, symmetric characters will be 5px, which is really small.
> >
> I was talking about the full cell width. I tested it before commenting,
> measuring the width in pixels of a line of text.
Yes, and I was saying that a cell width of 7px is very narrow because the
characters itself will only be using 5px or 6px max (to leave room for
inter-character spacing in normal words). You might be fine with such
narrow characters, but not everyone will be.
Ciao,
Michael.
next prev parent reply other threads:[~2020-11-30 16:44 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 [this message]
2020-12-03 12:11 ` Richard Earnshaw
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=alpine.LSU.2.20.2011301635050.26979@wotan.suse.de \
--to=matz@suse.de \
--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).