From: Rob Ote <0x1010111@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9's style(6) manual page
Date: Sun, 8 Apr 2018 00:38:28 -0400 [thread overview]
Message-ID: <CAEFT39EqpvLuGuHym1vkQiJYOsrdvyF-7dEaHMji3BjkM2=wTQ@mail.gmail.com> (raw)
In-Reply-To: <20180407131433.6819fa0c7eec6bac85da70c2@eigenstate.org>
> Ultimately, the goal is to write code that fits in with the
> other code around it and the system as a whole.
The Go released a very good idea, go fmt
imho, it is a better way
prev parent reply other threads:[~2018-04-08 4:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 16:00 8halfan
2018-04-07 17:47 ` Jules Merit
2018-04-07 17:59 ` Digby R.S. Tarvin
2018-04-07 19:11 ` hiro
2018-04-07 20:14 ` Ori Bernstein
2018-04-07 20:38 ` tlaronde
2018-04-07 20:42 ` Skip Tavakkolian
2018-04-08 4:38 ` Rob Ote [this message]
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='CAEFT39EqpvLuGuHym1vkQiJYOsrdvyF-7dEaHMji3BjkM2=wTQ@mail.gmail.com' \
--to=0x1010111@gmail.com \
--cc=9fans@9fans.net \
/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).