9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stuart Morrow <morrow.stuart@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] "Touching the Artwork" strikes again
Date: Fri, 11 Aug 2023 13:31:32 +0100	[thread overview]
Message-ID: <CABB-WO-eVDZCZp_tJ=KizF-W1Vvpkf8vGgzguJbTzhbWHk_GHA@mail.gmail.com> (raw)
In-Reply-To: <2fc2844e-5950-8cfc-ad08-74785d77bef5@posixcafe.org>

> Hear hear.

This is in response to it being laughable, "a gem", to comment on two
pairs of mutually-incompatible things appearing in the same software
distribution.

I truly don't get why that's a hear-hear moment.

> I particularly like Stuart's part about refusing to write
> the code.

I'm not a programmer (like the vast majority of people that ever used
a Unix-like operating system), and to the extent that I _can_ be
called one (is a hunt-and-peck typist "a typist"), I don't enjoy the
process.

And I'm not keen on touching what I think is one of the biggest programs.

And quasimodal typing seems like it would be outside of what you can
directly do with the libraries, kind of like if you wanted a stats(1)
that draws its (massive)menu outside of its (usually small)window.

> Sorry Stuart, people are not writing code for you, no matter how
> much you bitch on the mailing list. I don't know how you got it in to your
> head that we are here to serve you or your opinions. If you think you know
> what the priorities should be, and how to best solve these problems then
> just like fucking do it.

Really not seeing how you got it in your head(s?) that that's in my head.

I had an idea between posts(which is why it's not in the first post,
or the subject line)(ditto for switching on $service) about an
intellectually-satisfying design seeming to solve three known problems
that don't obviously have anything to do with each other.

Given that I know both how to close a window and how to exit rio, and
don't have a need for directing focus of keyboard commands in a way
that's elegant (because I don't use keyboard commands), I'm more
interested in the idea than in having it.

And now have I spend almost all of this thread dealing with either
strawmen or misreadings.

  reply	other threads:[~2023-08-11 12:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 23:18 Stuart Morrow
2023-08-09 23:41 ` Sigrid Solveig Haflínudóttir
2023-08-10  0:00   ` unobe
2023-08-10 11:35     ` Stuart Morrow
2023-08-10 14:13       ` qwx
2023-08-10 18:17         ` Stuart Morrow
2023-08-10 15:04       ` Sigrid Solveig Haflínudóttir
2023-08-10 18:24         ` Stuart Morrow
2023-08-10 19:33           ` Sigrid Solveig Haflínudóttir
2023-08-10 19:42             ` Sigrid Solveig Haflínudóttir
2023-08-11  0:08               ` Stuart Morrow
2023-08-11  0:07             ` Stuart Morrow
2023-08-11  0:17               ` Sigrid Solveig Haflínudóttir
2023-08-11  0:30                 ` Jacob Moody
2023-08-11 12:31                   ` Stuart Morrow [this message]
2023-08-11 13:12                     ` Jacob Moody
2023-08-11 20:38                       ` Stuart Morrow
2023-08-11 21:56                         ` Jacob Moody
2023-08-11 22:11                         ` hiro
2023-08-11 14:40                     ` hiro
2023-08-11 15:10                       ` Johnpaul Humphrey
2023-08-11 15:19                         ` hiro
2023-08-11 20:31                       ` Stuart Morrow
2023-08-11  0:26               ` Stanley Lieber
2023-08-10 18:29         ` Nathan Gorvett
2023-08-11  7:08           ` hiro
2023-08-11 12:32             ` Stuart Morrow
2023-08-10  0:08 ` Jacob Moody
2023-08-10  2:03   ` Stanley Lieber

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='CABB-WO-eVDZCZp_tJ=KizF-W1Vvpkf8vGgzguJbTzhbWHk_GHA@mail.gmail.com' \
    --to=morrow.stuart@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).