Unix Tutorial

[Oliver Elliott has a pithily written introduction to the Unix command line][i]. It occasionally serves as my cheatsheet when I need to remember how to use a command that I don’t use very often, but it can also serve as a primer on how to do things on the command line. And one of the greatest things about it, in this era of page views, is that it is all on one page. *Nice.*

[i]: http://www.oliverelliott.org/article/computing/tut_unix

Re-inVIgorated

[Speaking of Vi/Vim][], there has been a re-newed conversation about Vi on _The Humanist_ discussion list, including some useful links:

* Jonathan Reeve has a nice [workshop proposal][] to teach Vim to humanists.
* He also linked to a post on _The Programming Historian_ on [“Sustainable Authorship in Plain Text using Pandoc and Markdown”][ph].

[Speaking of Vi/Vim]: http://johnlaudun.org/20150118-virtual-vim/
[workshop proposal]: http://jonreeve.com/2013/11/workshop-proposal-vim-for-humanists/
[ph]: http://programminghistorian.org/lessons/sustainable-authorship-in-plain-text-using-pandoc-and-markdown

Speaking from the Command Line

One of eight tips from [Mitchell Cohen][] points out that you can not only use Mac OS X’s built-in *Text to Speech* engine from the command line (`say “some text”`), but, even more usefully, you can save the results to an audio file–again, all from the command line:

say -f mytext.txt -o myaudio.aiff

[Mitchell Cohen]: http://www.mitchchn.me/2014/os-x-terminal/

I am finally making progress on learning to code. I don’t know that I am ready to do any complicated natural language processing in Python just yet, but the basics are finally making sense to me. A lot of my education comes in ten minutes I grab here or twenty minutes I grab there to learn about `while` loops or what a `method` is. I am keeping all my notes and my code in a sub-sub-subdirectory. It’s long to type. Thank goodness `bash` is so customizable:

alias Learn=’cd Dropbox/personal/programming/learn’

Much easier.

I decided to use an initial capital as a way to distinguish my alias from a regular bash command. The alias depends upon being in the home (~) directory to work, which is usually where I begin, but if my work in the `jstor` directory begins to pick up, I can easily add a `~/` to the beginning of the directory structure above to make it possible to use the command from wherever I am.