A handful of people expressed interest in having a LaTeX workshop next
Tuesday, so I guess that's going to be a thing. If you'd like to
participate but don't have LaTeX installed yet, do that:

   - Windows
      - Install MikTeX <https://miktex.org/howto/install-miktex>
      - Install a PDF reader (you probably already have one installed)​
      - Install Texmaker <http://www.xm1math.net/texmaker/> or some other
      LaTeX editor <https://en.wikipedia.org/wiki/Comparison_of_TeX_editors>
      (*optional but recommended*, you should already have TeXworks
      <https://www.tug.org/texworks/> through MikTeX)
   - Mac and Linux
      - Install TeX Live
      <https://www.tug.org/texlive/acquire-netinstall.html> (impatient
      version <https://www.tug.org/texlive/quickinstall.html>)
      - Install a PDF reader (you probably already have one installed)
      - Install Texmaker <http://www.xm1math.net/texmaker/> (probably
      available through your favorite package manager) or some other LaTeX
      editor <https://en.wikipedia.org/wiki/Comparison_of_TeX_editors>
      but recommended*, you should already have TeXworks
      <https://www.tug.org/texworks/> through TeX Live)

Don't worry if you have problems installing stuff. That will be the first
thing we go over. If you want to be way ahead of the game, play around with
these resources: 1
<ftp://www.ctan.org/tex-archive/macros/latex/base/small2e.tex> 2
<http://detexify.kirelabs.org/classify.html> 3
<https://www.tug.org/begin.html> 4 <https://en.wikibooks.org/wiki/LaTeX> 5

If you're unsure why you'd want to learn LaTeX:

It's a typesetting language that's used *a lot* in academia. If you've used
HTML, it's kind of like that in that you write code describing what you
want to see. This is very different to what most of us are used to with
word processors. In a word processor, you define the *extent* of the
document. In LaTeX you define the *intent*. It's also older than most of
us, so most other languages have some way of interfacing with it or
mimicking its syntax. You've probably already used some common LaTeX
control sequences in an equation editor without realizing it. It's also
pretty good for scalable and automated documents. Plus, it plays nice with
Git, since the source document is just text. My favorite part is that it
also imbues you with a smug sense of superiority whenever you see someone
using a word processor to write complicated math, cite references, or
control formatting over multiple large documents.


Also, I'm gonna do some ​composite-y
<https://github.com/psas/lv3.0-airframe/issues/11> things
<https://github.com/psas/lv3.0-airframe/issues/12> Friday (and possibly
other days?), if anyone wants to join. I'll be in the LID project space
and/or EB 480 (one at a time, hopefully).

-- Joe Shields <https://joedang.github.io/>
psas-team mailing list

This list's membership is automatically generated from the memberships of the 
psas-airframe, psas-avionics, and psas-general mail lists. Visit 
http://lists.psas.pdx.edu to individually subscribe/unsubscribe yourself from 
these lists.

Reply via email to