From: Michael Misch <michaelmisch1985@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] How to get into plan9
Date: Wed, 20 Nov 2019 23:59:25 -0800 [thread overview]
Message-ID: <DEA05ABE-7FE9-4932-A76C-A0C1EFBEB6A3@gmail.com> (raw)
In-Reply-To: <20191121171516.35278139@alpha.localdomain>
I use it for my main code editor. It provides me with minimal opportunity for distractions, and a very clean and fluid user experience doesn’t hurt one bit. The ease of integration with other systems is unmatched, into and out of plan9 (I have Unix systems happily running factotum using my 9 secstore, plumbing going everywhere, etc). The best way to figure it all out is to just use the bloody thing for as much as you can.
> On Nov 20, 2019, at 10:16 PM, Jared Henley <jared@henley.id.au> wrote:
>
> Hi,
>
> Against all recommendations on the 9front website I installed 9front
> into a VM and lurked on this list for a while. But since I don't have a
> lot of time to play I haven't really learned much yet. I need to
> actually use it, but I'm not sure where to start. What kind of work is
> plan9 good at, or what are you people using it for?
>
> Jared.
>
> 💬
>
> Stop telling me how to use my computer.
> I will configure it how I want,
> get updates when I want,
> and run whatever _I_ want.
> - Robots
>
> What do you mean, “classified”?
> You don't keep a secret from the user.
> - Wall-E
next prev parent reply other threads:[~2019-11-21 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 6:15 Jared Henley
2019-11-21 7:59 ` Michael Misch [this message]
2019-11-21 15:37 ` [9front] " 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=DEA05ABE-7FE9-4932-A76C-A0C1EFBEB6A3@gmail.com \
--to=michaelmisch1985@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).