zsh-workers
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: "Axel Beckert" <abe@deuxchevaux.org>,
	"David Wales" <daviewales@disroot.org>,
	zsh-workers@zsh.org
Subject: Re: CSS for Zsh website?
Date: Thu, 03 Mar 2022 21:44:48 -0500	[thread overview]
Message-ID: <6587c04f-215b-40c0-a7b9-cb92a27bc354@www.fastmail.com> (raw)
In-Reply-To: <CAH+w=7ZXPHpaix9yEa-auWniNESPTsbYxSSyronXN7N6Ndu1Nw@mail.gmail.com>

On Thu, Mar 3, 2022, at 7:12 PM, Bart Schaefer wrote:
> On Thu, Mar 3, 2022 at 3:31 PM Lawrence Velázquez <larryv@zsh.org> wrote:
>>
>> On Thu, Mar 3, 2022, at 5:37 PM, Axel Beckert wrote:
>> >
>> > On Thu, Mar 03, 2022 at 12:08:11AM +1100, David Wales wrote:
>> >>     max-width: 80ch;
>> >
>> > Please don't artificially restrict the width of text on websites
>>
>> Hard disagree.  Legibility decreases with line length.
>
> Soft disagree.  Setting width to 80 characters is no more necessary
> than allowing it to be 100% of the viewport.  The only time to use
> character widths is with fixed-width fonts.  Set margins, not widths.

Agreed!  I didn't mean to defend the specific CSS that was proffered.
Frankly, before this thread I didn't know that "ch" was a CSS unit.

-- 
vq


  reply	other threads:[~2022-03-04  2:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 13:08 David Wales
2022-03-02 14:26 ` Peter Stephenson
2022-03-03 11:19 ` Daniel Shahaf
2022-03-03 22:15   ` David Wales
2022-03-04 13:12     ` Daniel Shahaf
2022-03-05  8:47       ` David Wales
2022-03-10 15:37         ` Vincent Lefevre
2022-03-10 16:23           ` Vin Shelton
2022-03-10 16:31             ` Peter Stephenson
2022-03-10 17:17               ` Clinton Bunch
2022-03-10 21:12                 ` Lawrence Velázquez
2022-03-10 21:30                   ` Clinton Bunch
2022-03-10 21:39                     ` Bart Schaefer
2022-03-10 22:43                     ` Vin Shelton
2022-03-10 23:26                     ` Lawrence Velázquez
2022-03-10 19:20               ` Vin Shelton
2022-03-03 23:27   ` Lawrence Velázquez
2022-03-03 22:37 ` Axel Beckert
2022-03-03 23:23   ` Lawrence Velázquez
2022-03-04  0:12     ` Bart Schaefer
2022-03-04  2:44       ` Lawrence Velázquez [this message]
2022-03-04 13:26         ` Daniel Shahaf
2022-03-05  6:34           ` Lawrence Velázquez

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=6587c04f-215b-40c0-a7b9-cb92a27bc354@www.fastmail.com \
    --to=larryv@zsh.org \
    --cc=abe@deuxchevaux.org \
    --cc=daviewales@disroot.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).