9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Silas McCroskey <inkswinc@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Bounties
Date: Fri, 17 Jan 2020 13:55:16 -0800	[thread overview]
Message-ID: <CAHjwAuz4a-+om6cXazWhQnVLHjCuh5rY73zN2Y0SsStgHojZgQ@mail.gmail.com> (raw)
In-Reply-To: <EFC0BF3379A3C032D5568E0E5CB5D3A1@a-b.xyz>

> The proverbial shortcut machine needs to have a target rio -- actually a
> current window -- bound in its namespace if it is to boss one around.

The quick-and-dirty way to do workspaces is sub-rios anyways, with the
"status bar" outside them, so that doesn't seem like a problem to me
for this case.

> rio is scriptable

http://sam-d.org/win/

contains a couple scripts I use for ad-hoc window management;
conspicuously missing is win/fill to tell a window to expand to fill
any empty space left by a recently-closed window, but that should
be doable as well by iterating through all the windows in the current
rio to determine what's empty space (though relative coordinates
in sub-rios -- the bane of rio scripting -- may trip you up here).

- sam-d


  reply	other threads:[~2020-01-17 21:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <134490038A9377D966659F986F257F34@ewsd.inri.net>
2020-01-17 14:43 ` Ethan Gardener
2020-01-17 16:05   ` kvik
2020-01-17 21:55     ` Silas McCroskey [this message]
2020-01-18  0:23       ` rio wishlists Lyndon Nerenberg
2020-01-18  0:40         ` [9front] " Stanley Lieber
     [not found]           ` <CAFSF3XNfdhb+ViOBmVMQ+5+PnSjCeD+9a9p9e4Ug0EX9==aZvw@mail.gmail.com>
2020-01-18  8:19             ` hiro
2020-01-18  9:53               ` Steve Simon
2020-01-18 10:19                 ` hiro
2020-01-21  8:54               ` Ethan Gardener
2020-01-21  8:57         ` Ethan Gardener
2020-01-21  9:49           ` hiro
2020-01-22 16:30             ` Ethan Gardener
2020-01-22 16:47               ` hiro
2020-01-23 15:09                 ` Ethan Gardener
     [not found]                   ` <CAK0pxsHVpyae1+teTSOAFp=nBoq_r7-aKexh_X=hEDe7hUcReA@mail.gmail.com>
     [not found]                     ` <CAK0pxsFDk=C_+37tKzU=U-TMQLTPcW6MOQ1sgKNBrYhWrj4Bwg@mail.gmail.com>
2020-01-23 18:12                       ` Marshall Conover
2020-01-23 21:23                         ` hiro
2020-01-23 22:42                           ` Julius Schmidt
2020-01-24  0:39                             ` Ethan Gardener
2020-01-24  0:44                               ` Ethan Gardener
2020-01-23 23:50                         ` Ethan Gardener
2020-01-24  0:59                           ` Jeremy Jackins
2020-01-24 10:04                             ` hiro
2020-01-21  8:37     ` [9front] Bounties Ethan Gardener
2020-01-22 17:04     ` Ori Bernstein
     [not found] <FEFDF1EDDEF96554EC8D099B3EFFBCE2@ewsd.inri.net>
2020-01-17  0:57 ` umbraticus
2020-01-05  7:06 Bounties Jens Staal
2020-01-16 18:05 ` [9front] Bounties Ethan Gardener
2020-01-17  0:47   ` sl
2020-01-16 18:51 ` Calvin Morrison
2020-01-16 19:35 ` Calvin Morrison
2020-01-16 23:03   ` Ethan Gardener

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=CAHjwAuz4a-+om6cXazWhQnVLHjCuh5rY73zN2Y0SsStgHojZgQ@mail.gmail.com \
    --to=inkswinc@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).