The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] eqn
Date: Fri, 4 Oct 2019 15:12:43 +1000	[thread overview]
Message-ID: <CAKr6gn2RrsSiMSiHnG276zBsfK=AEN7tPCku8Ov3P-S-Gb=d5A@mail.gmail.com> (raw)
In-Reply-To: <20191004042034.GS13997@mcvoy.com>

I'm going to give a contrarian response. You may be wrong, and he
maybe should do LaTex.

Why?

because it's what his peer group, and professors, and other people
like markers and tutorial assisters will expect, and he can use things
like OverLeaf very probably on the Uni tab, which has shared edit, all
kinds of useful templates, and help communities.

You don't want to tie him to your apron strings, for help: He needs to
learn how to go out into the world and hassle other people for help
too!

My son, who is in the same kind-of cohort but perhaps 6years ahead,
wrote his thesis in OverLeaf and did very well in it.

The markup is XArchiV and journal friendly: His chances of getting
through peer review barriers which obsess with form, and not function
(sad) is better.

Sometimes, being the stand-out is not good. I was the only visible
Athiest in school and when I found a copy of the scots prayer book, it
was different page numbers and I couldn't find the hymn before they'd
finished singing it. I guess the example I am giving doesn't help my
own story because I am an essentially HAPPY athiest, but still: you
don't always want to be running against the stream.

If the maths is good, he's born to fly solo, and is heading into place
of excellence, none of this will matter. If he is looking to relate to
his community, it may.

On Fri, Oct 4, 2019 at 2:21 PM Larry McVoy <lm@mcvoy.com> wrote:
>
> So my kid is using LaTex and I'd like to show him what troff can do.
> For the record, back when he was born, 20 years ago, I was program
> chair for Linux Expo (which sounds like a big deal but all it meant
> was I had the job of formatting the proceedings).  LaTex was a big
> deal but I pushed people towards troff and the few people that took
> the push came back and said "holy crap is this easy".
>
> My kid is a math guy, does anyone have some eqn input and output
> that they can share?
>
> Thanks,
>
> --lm

  parent reply	other threads:[~2019-10-04  5:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04  4:20 Larry McVoy
2019-10-04  4:35 ` Dave Horsfall
2019-10-04  5:12 ` George Michaelson [this message]
2019-10-04 13:43   ` Nemo
2019-10-04 14:57 ` aksr
2019-10-04 15:52   ` U'll Be King of the Stars
2019-10-04 16:12     ` Jon Forrest
2019-10-04 17:24       ` Adam Thornton
2019-10-04 18:55         ` Kurt H Maier
2019-10-04 17:43       ` Steffen Nurpmeso
2019-10-06  8:03       ` arnold
2019-10-04 19:02     ` Larry McVoy
2019-10-07 17:26     ` Seth J. Morabito
2019-10-07 19:14       ` Adam Thornton
2019-10-08 21:11         ` Seth Morabito
2019-10-04 19:25 ` Fabio Scotoni
2019-10-05  1:59 Doug McIlroy

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='CAKr6gn2RrsSiMSiHnG276zBsfK=AEN7tPCku8Ov3P-S-Gb=d5A@mail.gmail.com' \
    --to=ggm@algebras.org \
    --cc=lm@mcvoy.com \
    --cc=tuhs@minnie.tuhs.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).