<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>KHE (Posts about OS-X)</title><link>https://east.fm/</link><description></description><atom:link href="https://east.fm/categories/os-x.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Fri, 26 Oct 2018 22:16:53 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Web Development Setup on macOS</title><link>https://east.fm/posts/dns-masq/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div class="section" id="a-flexible-web-development-setup-on-macos"&gt;
&lt;h2&gt;A Flexible Web Development Setup on macOS&lt;/h2&gt;
&lt;p&gt;This is a simple way to configure a macOS system for web development.  It
allows one to develop multiple sites locally, without reconfiguring anything
when changing sites/customers.&lt;/p&gt;
&lt;p&gt;There are two key components to the strategy: &lt;tt class="docutils literal"&gt;dnsmasq&lt;/tt&gt; and the
httpd daemon's configuration.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/dns-masq/index.html"&gt;Read more…&lt;/a&gt; (8 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>django</category><category>dns</category><category>dnsmasq</category><category>httpd</category><category>macos</category><category>OS-X</category><guid>https://east.fm/posts/dns-masq/index.html</guid><pubDate>Sun, 10 Jun 2018 05:00:00 GMT</pubDate></item><item><title>Dotfiles Reloaded</title><link>https://east.fm/posts/dotfiles-reloaded/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;About a year and a half ago, I converted to using &lt;tt class="docutils literal"&gt;GNU stow&lt;/tt&gt; and &lt;tt class="docutils literal"&gt;git&lt;/tt&gt; for
managing my dotfiles.  The most recent version of that effort is available
&lt;a class="reference external" href="https://bitbucket.org/MaDeuce/dotfiles"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The scheme worked well but the OCD part of me grew tired of seeing symbolic
links to files instead of the actual files themselves.  The symlinks weren't
unexpected, after all, the whole point of &lt;tt class="docutils literal"&gt;stow&lt;/tt&gt; is easily managing lots of
links.  Then I ran across a post on Hacker News about using a bare git repo to
manage dotfiles in place. I very much liked the idea and settled on using
&lt;a class="reference external" href="https://github.com/RichiH/vcsh"&gt;&lt;tt class="docutils literal"&gt;vcsh&lt;/tt&gt;&lt;/a&gt; and &lt;a class="reference external" href="http://myrepos.branchable.com"&gt;&lt;tt class="docutils literal"&gt;myrepos&lt;/tt&gt;&lt;/a&gt; to manage my dotfiles going forward.&lt;/p&gt;
&lt;p&gt;I should mention that I've known about &lt;tt class="docutils literal"&gt;vcsh&lt;/tt&gt; for a good while.  My impression
had been that it was more complicated than necessary for my purposes.  I've
since changed my mind completely; it's as simple as what I ended up doing with
&lt;tt class="docutils literal"&gt;stow&lt;/tt&gt;, if not simpler.  Minor tweaks to dotfiles are a pleasure when using
&lt;tt class="docutils literal"&gt;myrepos&lt;/tt&gt;.&lt;/p&gt;
&lt;p&gt;These are my brief notes about the process.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/dotfiles-reloaded/index.html"&gt;Read more…&lt;/a&gt; (5 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>dotfiles</category><category>OS-X</category><category>unix</category><guid>https://east.fm/posts/dotfiles-reloaded/index.html</guid><pubDate>Sat, 04 Feb 2017 00:57:14 GMT</pubDate></item><item><title>Installing nodejs and npm on OS-X</title><link>https://east.fm/posts/installing-nodejs-and-npm-on-os-x/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;How to install &lt;tt class="docutils literal"&gt;nodejs&lt;/tt&gt; and &lt;tt class="docutils literal"&gt;npm&lt;/tt&gt; on OS-X.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/installing-nodejs-and-npm-on-os-x/index.html"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>nodejs</category><category>OS-X</category><guid>https://east.fm/posts/installing-nodejs-and-npm-on-os-x/index.html</guid><pubDate>Fri, 13 May 2016 14:24:52 GMT</pubDate></item><item><title>OS-X, 'Open With', and emacsclient</title><link>https://east.fm/posts/open-with-emacsclient/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;Because I've configured my GNU emacs to &lt;a class="reference external" href="https://east.fm/posts/gnu-emacs-setup-for-os-x/index.html"&gt;automatically run in daemon mode&lt;/a&gt; I wish to 'use' emacs by running
&lt;tt class="docutils literal"&gt;emacsclient&lt;/tt&gt; exclusively.  But emacsclient isn't an OS-X 'app' which means
that I can't double click on a file to open it with emacsclient.  It also
means that I can't use the 'Open With' menu to edit a file via emacsclient.
Here is how to resolve those issues.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/open-with-emacsclient/index.html"&gt;Read more…&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>emacs</category><category>OS-X</category><category>plist</category><category>python</category><guid>https://east.fm/posts/open-with-emacsclient/index.html</guid><pubDate>Tue, 15 Dec 2015 01:57:02 GMT</pubDate></item><item><title>Gnu Emacs With Server Mode on OS-X</title><link>https://east.fm/posts/gnu-emacs-setup-for-os-x/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;I have used the &lt;a class="reference external" href="http://emacsformacosx.com"&gt;Emacs for Mac OS-X&lt;/a&gt; distribution
of Gnu Emacs for years and have been quite pleased with it.  Emacs'
&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;server-mode&lt;/span&gt;&lt;/tt&gt; is great in that it makes for very fast load times and it
allows sharing buffer contents, kill rings, etc., between windows. However, I
found it a little tricky to get it working perfectly on OS-X.  These are my
notes on how to install and configure it so that &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;server-mode&lt;/span&gt;&lt;/tt&gt; works
correctly on OS-X.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/gnu-emacs-setup-for-os-x/index.html"&gt;Read more…&lt;/a&gt; (4 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>emacs</category><category>OS-X</category><guid>https://east.fm/posts/gnu-emacs-setup-for-os-x/index.html</guid><pubDate>Wed, 09 Dec 2015 20:18:18 GMT</pubDate></item><item><title>Print an Agenda from the OS-X Calendar</title><link>https://east.fm/posts/print-agenda-from-os-x-calendar/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;I have no idea what Apple has to make it so difficult to simply print a list
of scheduled appointments from a calendar.  Do some googling - you'll quickly
figure out that a simple and acceptable way really doesn't exist.  For
example, if one simply does a &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;Print-&amp;gt;Scheduled&lt;/span&gt; Events&lt;/tt&gt; for the next six months,
Apple kindly prints an entry for every single day over the next six months,
whether or not the day has an appointment.  I don't want to print ten pages
simply to get a list of the five appointments in the next six months that I
have on a particular calendar.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/print-agenda-from-os-x-calendar/index.html"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>OS-X</category><guid>https://east.fm/posts/print-agenda-from-os-x-calendar/index.html</guid><pubDate>Tue, 12 May 2015 17:18:36 GMT</pubDate></item><item><title>Adding Fonts to enscript</title><link>https://east.fm/posts/adding-fonts-to-enscript/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;Installing new fonts for use with &lt;tt class="docutils literal"&gt;enscript&lt;/tt&gt; on OS-X&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/adding-fonts-to-enscript/index.html"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>enscript</category><category>font</category><category>OS-X</category><guid>https://east.fm/posts/adding-fonts-to-enscript/index.html</guid><pubDate>Mon, 11 May 2015 05:00:00 GMT</pubDate></item><item><title>email via the command line on OS-X</title><link>https://east.fm/posts/sending-email-via-the-command-line-on-os-x/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;I needed to email cron job output from my OS-X machine to off-site recipients.
To do this, I had to configure the OS-X Mail Transfer Agent (MTA),
&lt;tt class="docutils literal"&gt;postfix&lt;/tt&gt;, to route outgoing mail through a working SMTP server, in this
case, GMail.  These are my notes about how to configure this on OS-X Yosemite
10.10.3.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/sending-email-via-the-command-line-on-os-x/index.html"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>mail</category><category>OS-X</category><category>SMTP</category><category>sysadmin</category><guid>https://east.fm/posts/sending-email-via-the-command-line-on-os-x/index.html</guid><pubDate>Sun, 10 May 2015 21:55:05 GMT</pubDate></item><item><title>Restoring 'Save As' to OS-X Yosemite</title><link>https://east.fm/posts/restoring-save-as/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;So, Yosemite caused most OS-X apps to loose &lt;tt class="docutils literal"&gt;Save &lt;span class="pre"&gt;As...&lt;/span&gt;&lt;/tt&gt; in favor of
&lt;tt class="docutils literal"&gt;Duplicate&lt;/tt&gt; or whatever.  Here is how to get &lt;tt class="docutils literal"&gt;Save &lt;span class="pre"&gt;As...&lt;/span&gt;&lt;/tt&gt; back.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/restoring-save-as/index.html"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>OS-X</category><guid>https://east.fm/posts/restoring-save-as/index.html</guid><pubDate>Sun, 04 Jan 2015 06:00:00 GMT</pubDate></item><item><title>Extending the Filetypes Supported by Quicklook</title><link>https://east.fm/posts/extending-the-filetypes-supported-by-quicklook/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;Apple's QuickLook is a great service.  I have grown to rely upon it a great deal
during my daily work.  Strangely, Apple seems to have reduced the number of
content types that QL can render in Mavericks (e.g., flv), but that's another
topic.  This note describes how to get QuickLook to display the contents of
unknown files as text.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/extending-the-filetypes-supported-by-quicklook/index.html"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>OS-X</category><guid>https://east.fm/posts/extending-the-filetypes-supported-by-quicklook/index.html</guid><pubDate>Tue, 03 Dec 2013 06:00:00 GMT</pubDate></item></channel></rss>