9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Re: TeX
Date: Tue, 20 Feb 2018 13:22:59 +0000	[thread overview]
Message-ID: <1519132979.611437.1276972552.2B94C77D@webmail.messagingengine.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1802200947210.15422@phi>

On Tue, Feb 20, 2018, at 9:04 AM, Julius Schmidt wrote:
> I have a feeling this is becoming the largest thread in the history of 
> this list, illustrating the principle that the importance of a change is 
> inversely proportional to the amount of discussion it creates.

I very very nearly added my bit yesterday. Glad I didn't.
Oh wait, I'm doing it now.

> 
> To hypocritically add my two cents:
> 
> To me the cryptic references to tex(1) have been one of those Plan 9 
> things you stumble upon when you first play with the OS, like the fact 
> that copying is called "snarf". It's confusing as hell but eventually you 
> just accept it as it is.

I briefly wanted to jump on the bandwagon of zealously removing all 
unnecessary confusion, "because necessary things are confusing 
enough already", but then I remembered that neither of these things 
ever confused me for very long at all. I don't see the problem.

These days, I try to fight urges to tidy up all the little things like this, 
because a lot of the tidying up does no real good and some of it is 
actually harmful.

> 
> Hence I'm opposed to removing the references.
> 
> If this issue had *any* technical relevance behind it, I might reconsider,
> but it does not.
> 
> Maybe we should just copy over emacs(1).
> 
> aiju
> 
> On Mon, 19 Feb 2018, sl@stanleylieber.com wrote:
> 
> >> do i need some form of entitlement to think?
> >
> > This has been debated in academia for decades.  To some extent,
> > privilege is the time and space to think.
> >
> > sl
> >


-- 
The lyf so short, the craft so long to lerne. -- Chaucer


  reply	other threads:[~2018-02-20 13:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 23:26 sl
2018-02-20  9:04 ` Julius Schmidt
2018-02-20 13:22   ` Ethan Grammatikidis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-14  2:23 sl
2018-02-14  1:59 TeX Lyndon Nerenberg
2018-02-14  9:15 ` [9front] TeX Steve Simon
2018-02-18  6:55   ` Matthew Veety
2018-02-18 12:04     ` Steve Simon
2018-02-18 19:56       ` Sean Hinchee
2018-02-19  4:32       ` Matthew Veety
2018-02-18 14:12     ` hiro
2018-02-18 17:18       ` Steve Simon

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=1519132979.611437.1276972552.2B94C77D@webmail.messagingengine.com \
    --to=eekee57@fastmail.fm \
    --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).