9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] "Touching the Artwork" strikes again
Date: Thu, 10 Aug 2023 16:13:04 +0200	[thread overview]
Message-ID: <F1515E9FDF229DBFBD09AC231B810FCF@wopr.sciops.net> (raw)
In-Reply-To: <CABB-WO8yV41n5S_ao4SfmWDBS-dqUN_zfJP0A1ZO3MWEzH2dhw@mail.gmail.com>

> The discussion should have been should it be enabled at all.
> 
> I'm pretty against keyboard control in window management in
> particular, triply so on Plan 9, but keybindings could actually be
> tolerated if they were available only while the window management menu
> is quasimodally held open with button 3. It's better than the nested
> GNU Screen way of controlling where commands go.
> 
> And Exit is neither really "window management" anyway nor something
> anyone is actually missing if it's undiscoverable without a man page
> read.
> 
> And q to quit is a Plan 9 standard already.
> 
> Also, if checking for /env/wsys is too much magic (this was the real
> reason Exit was enabled - not that anyone actually *uses* it in the
> parent rio) you could check for service=cpu instead and get
> practically the same result.

The current state was generally agreed upon after plenty of
discussion, which occurred before, during and after the patches
surrounding rio Exit, and which anyone could look up if they cared to.
I don't think anything prevents anyone from just reverting or
modifying them if they're unsatisfied with them.

If you want GNU screen on plan9, go for it.  You can implement it
without even touching rio by using /dev/kbdtap.  You can also combine
that with riow and bar scripts.  There's literally nothing preventing
you from reimplementing your favorite unix terminal multiplexer or GNU
tool on plan9.  Of course, you probably already know all of this,
which is why you're reviving this discussion after someone failed to
quit sam or operate rio for a moment.  I didn't know about q being
standard though, I tried typing q in acme, but it doesn't work, what
gives?

qwx

  reply	other threads:[~2023-08-10 14:14 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 [this message]
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
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=F1515E9FDF229DBFBD09AC231B810FCF@wopr.sciops.net \
    --to=qwx@sciops.net \
    --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).