From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] problem with acme on 9front
Date: Sat, 21 May 2016 10:36:44 -0700 [thread overview]
Message-ID: <94da399e3d511fd1c3eba711ce9692e0@lilly.quanstro.net> (raw)
In-Reply-To: <20160519215144.GG22691@wopr>
> This is tantamount to saying acme is superior because you are better at
> acme. [...]
c'mon man. you follow this with several paragraphs of opinion which appear
to say that acme is not better because you don't like it.
but then again, editors don't tend to lead to logical arguments. :-)
- erik
next prev parent reply other threads:[~2016-05-21 17:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 18:30 christophe DAMAS
2016-05-19 18:40 ` Siarhei Zirukin
2016-05-19 19:42 ` Charles Forsyth
2016-05-19 21:51 ` Kurt H Maier
2016-05-20 0:37 ` Lyndon Nerenberg
2016-05-20 1:23 ` Ethan Grammatikidis
2016-05-20 1:32 ` Lyndon Nerenberg
2016-05-20 2:02 ` Ethan Grammatikidis
2016-05-20 2:07 ` Lyndon Nerenberg
2016-05-20 11:58 ` hiro
2016-05-20 12:07 ` Mark van Atten
2016-05-20 15:49 ` Wes Kussmaul
2016-05-20 12:12 ` Brantley Coile
2016-05-20 20:01 ` Steve Simon
2016-05-21 21:52 ` Mark Lee Smith
2016-05-21 23:18 ` erik quanstrom
2016-05-22 7:36 ` Siarhei Zirukin
2016-05-22 17:28 ` Mark Lee Smith
2016-05-21 17:36 ` erik quanstrom [this message]
2016-05-21 18:16 ` Kurt H Maier
2016-05-21 18:28 ` Rob Pike
2016-05-21 19:21 ` Kurt H Maier
2016-05-21 23:14 ` Lyndon Nerenberg
2016-05-19 18:41 ` cinap_lenrek
2016-05-19 19:20 ` Mark Lee Smith
2016-05-19 19:36 ` cinap_lenrek
2016-05-19 20:26 ` Mark Lee Smith
2016-05-19 20:37 ` Lee Fallat
2016-05-19 20:40 ` Aram Hăvărneanu
2016-05-19 20:11 ` stanley lieber
2016-05-19 20:15 ` Charles Forsyth
2016-05-19 20:53 ` stanley lieber
2016-05-19 21:13 ` Mark van Atten
2016-05-19 21:18 ` Lee Fallat
2016-05-21 19:08 ` Mark van Atten
2016-05-21 19:23 trebol55555
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=94da399e3d511fd1c3eba711ce9692e0@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--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).