From: umbraticus@prosimetrum.com
To: 9front@9front.org
Subject: Re: [9front] Bounties
Date: Fri, 17 Jan 2020 13:57:52 +1300 [thread overview]
Message-ID: <81FF1F0AB1BC43FA64ED870FED44E188@prosimetrum.com> (raw)
In-Reply-To: <FEFDF1EDDEF96554EC8D099B3EFFBCE2@ewsd.inri.net>
indeed, and /dev/text is writeable.
while(){date >/dev/text; sleep 60}
replace date with whatever and run in a rio window with your favourite dimensions
umbraticus
next parent reply other threads:[~2020-01-17 0:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FEFDF1EDDEF96554EC8D099B3EFFBCE2@ewsd.inri.net>
2020-01-17 0:57 ` umbraticus [this message]
[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
2020-01-21 8:37 ` Ethan Gardener
2020-01-22 17:04 ` Ori Bernstein
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=81FF1F0AB1BC43FA64ED870FED44E188@prosimetrum.com \
--to=umbraticus@prosimetrum.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).