From: Nicolas Pitre <nico@fluxnic.net>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Laight <David.Laight@aculab.com>,
Casey Schaufler <casey@schaufler-ca.com>,
David Howells <dhowells@redhat.com>,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
Ian Kent <raven@themaw.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
NetFilter <netfilter-devel@vger.kernel.org>,
Joe Perches <joe@perches.com>
Subject: Re: clean up kernel_{read,write} & friends v2
Date: Fri, 5 Jun 2020 11:00:59 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YSQ.7.77.849.2006051039350.1353413@knanqh.ubzr> (raw)
In-Reply-To: <d67deb88-73a8-4c57-6b37-c62190422d65@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Fri, 5 Jun 2020, Philippe Mathieu-Daudé wrote:
> Unfortunately refreshable braille displays have that "hardware
> limitations". 80 cells displays are very expensive.
> Visual impairments is rarely a "choice".
> Relaxing the 80-char limit make it harder for blind developers
> to contribute.
Well, not really.
It is true that 80-cells displays are awfully expensive. IMHO they are
also unwieldy due to their size: they are hardly portable, and they
require your hands to move twice as far which may sometimes impair
reading efficiency. So I never liked them.
My braille display has 40 cells only. So even with a 80-cells limit I
always had to pan the display to see the whole line anyway.
My text console is set to 160x128. The trick here is to have the number
of columns be a multiple of the braille display's width to avoid dead
areas when panning to the right.
So if you ask me, I'm not against relaxing the 80 columns limit for
code. What really matters to me is that I can stay clear of any GUI.
Nicolas
next prev parent reply other threads:[~2020-06-05 15:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 5:40 clean up kernel_{read,write} & friends v2 Christoph Hellwig
2020-05-28 5:40 ` [PATCH 01/14] cachefiles: switch to kernel_write Christoph Hellwig
2020-05-28 5:40 ` [PATCH 02/14] autofs: " Christoph Hellwig
2020-05-28 5:40 ` [PATCH 03/14] bpfilter: " Christoph Hellwig
2020-05-28 5:40 ` [PATCH 04/14] fs: unexport __kernel_write Christoph Hellwig
2020-05-28 5:40 ` [PATCH 05/14] fs: check FMODE_WRITE in __kernel_write Christoph Hellwig
2020-05-28 5:40 ` [PATCH 06/14] fs: remove the call_{read,write}_iter functions Christoph Hellwig
2020-05-28 18:56 ` Al Viro
2020-05-29 5:51 ` Christoph Hellwig
2020-05-28 5:40 ` [PATCH 07/14] fs: implement kernel_write using __kernel_write Christoph Hellwig
2020-05-28 5:40 ` [PATCH 08/14] fs: remove __vfs_write Christoph Hellwig
2020-05-28 5:40 ` [PATCH 09/14] fs: don't change the address limit for ->write_iter in __kernel_write Christoph Hellwig
2020-05-28 18:43 ` Linus Torvalds
2020-05-29 12:32 ` Christoph Hellwig
2020-05-31 23:59 ` Logan Gunthorpe
2020-05-28 19:00 ` Al Viro
2020-05-29 5:57 ` Christoph Hellwig
2020-05-29 13:37 ` Christoph Hellwig
2020-05-28 5:40 ` [PATCH 10/14] fs: add a __kernel_read helper Christoph Hellwig
2020-05-28 5:40 ` [PATCH 11/14] integrity/ima: switch to using __kernel_read Christoph Hellwig
2020-05-28 5:40 ` [PATCH 12/14] fs: implement kernel_read " Christoph Hellwig
2020-05-28 5:40 ` [PATCH 13/14] fs: remove __vfs_read Christoph Hellwig
2020-05-28 5:40 ` [PATCH 14/14] fs: don't change the address limit for ->read_iter in __kernel_read Christoph Hellwig
2020-05-28 19:03 ` Al Viro
2020-05-28 18:51 ` clean up kernel_{read,write} & friends v2 Linus Torvalds
2020-05-28 18:57 ` Sedat Dilek
2020-05-28 19:22 ` Joe Perches
2020-05-28 19:33 ` Al Viro
2020-05-28 19:44 ` Matthew Wilcox
2020-05-28 20:06 ` Al Viro
2020-05-28 20:14 ` Deucher, Alexander
2020-05-28 20:18 ` Joe Perches
2020-05-28 20:29 ` Dave Airlie
2020-05-28 21:03 ` Joe Perches
2020-05-28 20:17 ` David Howells
2020-05-28 21:20 ` Casey Schaufler
2020-05-29 13:08 ` David Laight
2020-05-29 19:19 ` Linus Torvalds
2020-05-29 22:02 ` Casey Schaufler
2020-05-29 23:12 ` [PATCH] checkpatch/coding-style: Allow 100 column lines Joe Perches
2020-05-30 22:14 ` Andreas Dilger
2020-05-30 23:15 ` Joe Perches
2020-06-05 6:36 ` clean up kernel_{read,write} & friends v2 Philippe Mathieu-Daudé
2020-06-05 15:00 ` Nicolas Pitre [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-13 6:56 Christoph Hellwig
2020-05-20 15:59 ` Christoph Hellwig
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=nycvar.YSQ.7.77.849.2006051039350.1353413@knanqh.ubzr \
--to=nico@fluxnic.net \
--cc=David.Laight@aculab.com \
--cc=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=f4bug@amsat.org \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).