From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] graphics tools
Date: Thu, 22 Sep 2022 22:24:43 -0400 [thread overview]
Message-ID: <5F9D2886-A295-426E-B2D2-CC3819150B21@stanleylieber.com> (raw)
In-Reply-To: <5B92F9C29AF4BD28334E6EF01A686EED@thinktankworkspaces.com>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
this will also run on 9front:
http://plan9.stanleylieber.com/uxn/
sl
> On Sep 22, 2022, at 10:12 PM, william@thinktankworkspaces.com wrote:
>
> I'm happy with pic(1). I got some of it working.
>
> Just tired of open/close file for every little thing or constantly pasting
> pic test.ms | troff | page.
>
> I would like to have it open in acme and click put or sam and :w or and see it change quickly.
>
> Its juust slower
>
> Quoth ori@eigenstate.org:
>> Quoth william@thinktankworkspaces.com:
>>> wow. No way to become lazy in plan9 for sure. Thanks. I will explore
>>>
>>
>> pic(1) is quite nice for these kinds of diagrams, in my experience.
>>
>> There are also things like pico (https://github.com/qwx9/pico), but
>> they're also textual.
>>
>> I'm not aware of anyone writing anything much more advanced
>> than paint for interactive drawing. Programs welcome.
>>
>>
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2258 bytes --]
next prev parent reply other threads:[~2022-09-23 2:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 0:58 william
2022-09-23 1:06 ` ori
2022-09-23 1:15 ` william
2022-09-23 1:15 ` william
2022-09-23 2:04 ` ori
2022-09-23 2:12 ` william
2022-09-23 2:24 ` Stanley Lieber [this message]
2022-09-23 2:38 ` william
2022-09-23 2:44 ` Stanley Lieber
2022-09-23 4:21 ` umbraticus
2022-09-23 6:55 ` Steve Simon
2022-09-23 7:15 ` kvik
2022-09-23 21:16 ` william
2022-09-23 21:53 ` Stanley Lieber
2022-09-23 22:02 ` william
2022-09-23 22:35 ` Stanley Lieber
2022-09-25 1:57 ` sl
2022-09-25 2:37 ` william
2022-09-23 21:16 ` william
2022-11-25 21:37 ` noam
2022-11-26 1:15 ` umbraticus
2022-11-27 20:46 ` umbraticus
2022-09-23 20:45 ` Stuart Morrow
2022-09-23 10:54 ` tlaronde
2022-09-23 18:17 ` Csepp
2022-09-23 22:33 ` umbraticus
2022-09-24 18:29 ` Csepp
2022-09-27 9:56 ` umbraticus
2022-09-27 15:43 ` Kurt H Maier
2022-09-27 15:59 ` Sigrid Solveig Haflínudóttir
2022-09-28 9:39 ` tlaronde
2022-09-30 6:39 ` william
2022-09-30 6:39 ` william
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=5F9D2886-A295-426E-B2D2-CC3819150B21@stanleylieber.com \
--to=sl@stanleylieber.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).