From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] PATCH: click-to-focus in fgui
Date: Sun, 15 Aug 2021 21:03:50 +0200 [thread overview]
Message-ID: <CAFSF3XPHHW=+tX90w=dbfk=PB4AoMiXuJTdvaH8xXL1Bvz0_8g@mail.gmail.com> (raw)
In-Reply-To: <A2A7D88AFD9784CB82D5447E61ACD98A@qak>
Kvik, with more documentation about our religion won't it become too
hard for the zealous batch of our new users to break those same strict
rules?
I highly approve the urge of learning to be an idiot.
"matters trivial and complex"
I think there is just one trivial matter here, a choice between 2 or 3
options: either you use click to focus, or not.
You might claim there's a third choice, to use both. I pointed out
that this is inconsistent. Maybe you have a complex reason why it is
not?
Looking from the other direction: Is there anybody who disagrees that
consistency is more important than which of the 2 options are
selected? I might have been quick to assume no.
Sorry if my opinion wasn't clear all along. Thanks for your patience.
On 8/15/21, kvik@a-b.xyz <kvik@a-b.xyz> wrote:
> Quoth Eckard Brauer <eckard.brauer@gmx.de>:
>> If the topic is that dogmatically overloaded, it _needs_ to be
>> documented in somewhere strictly before all user guides and the like.
>
> It is somewhat of a pattern in this community to assume that everyone
> is on the same page for a choice of matters trivial and complex. You
> are supposed to pick up on this by either being unlucky enough to have
> similar prior experiences as "us" and can read between the lines very
> well, or will learn from hiro that you're an idiot and are better off
> installing Linux for not having the community insight accumulated over
> the years.
>
> Documentation explaining broad goals and reasoning behind them would
> be helpful for the community, and not just newcomers or people who
> don't religiously follow #cat-v. But writing and maintaining such
> documentation and often times even following your own advice is much
> harder than blasting people.
>
>
next prev parent reply other threads:[~2021-08-15 19:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 22:59 Silas McCroskey
2021-08-10 14:19 ` ori
2021-08-11 5:28 ` rgl
2021-08-11 20:49 ` Philip Silva
2021-08-11 21:09 ` Steve Simon
2021-08-11 22:37 ` Xiao-Yong Jin
2021-08-12 9:05 ` hiro
2021-08-12 14:36 ` Eckard Brauer
2021-08-13 6:44 ` unobe
2021-08-13 7:10 ` hiro
2021-08-14 10:20 ` Eckard Brauer
2021-08-14 13:09 ` qwx
2021-08-14 15:03 ` Stuart Morrow
2021-08-14 13:17 ` José Miguel Sánchez García
2021-08-14 20:57 ` Patch-keeping (Was Re: [9front] PATCH: click-to-focus in fgui) unobe
2021-08-14 15:04 ` [9front] PATCH: click-to-focus in fgui Stuart Morrow
2021-08-14 18:08 ` hiro
2021-08-14 21:43 ` unobe
2021-08-15 6:47 ` hiro
2021-08-14 21:46 ` unobe
2021-08-15 13:36 ` Eckard Brauer
2021-08-15 19:16 ` hiro
2021-08-15 17:31 ` kvik
2021-08-15 18:34 ` Kurt H Maier
2021-08-15 18:48 ` Stanley Lieber
2021-08-15 20:18 ` Eckard Brauer
2021-08-15 22:35 ` Stanley Lieber
2021-08-16 5:14 ` Stanley Lieber
2021-08-16 15:46 ` Skylar Bleed
2021-08-15 19:03 ` hiro [this message]
2021-08-16 16:40 ` kvik
2021-08-16 19:25 ` Stuart Morrow
2021-08-16 19:40 ` Kurt H Maier
2021-08-17 2:05 ` Stanley Lieber
2021-08-16 20:04 ` hiro
2021-08-16 20:13 ` hiro
2021-08-17 1:10 ` Xiao-Yong Jin
2021-08-17 8:11 ` hiro
2021-08-12 0:12 ` hiro
2021-08-15 4:29 ` ori
2021-08-16 19:40 ` ori
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='CAFSF3XPHHW=+tX90w=dbfk=PB4AoMiXuJTdvaH8xXL1Bvz0_8g@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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 NNTP newsgroup(s).