<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Mac on Andres Marrugo</title>
    <link>https://andresmarrugo.net/blog/categories/mac/</link>
    <description>Recent content in Mac on Andres Marrugo</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 22 Oct 2012 00:11:00 -0500</lastBuildDate>
    <atom:link href="https://andresmarrugo.net/blog/categories/mac/atom.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Always Late to The Party</title>
      <link>https://andresmarrugo.net/blog/2012/10/22/always-late-to-the-party/</link>
      <pubDate>Mon, 22 Oct 2012 00:11:00 -0500</pubDate>
      <guid>https://andresmarrugo.net/blog/2012/10/22/always-late-to-the-party/</guid>
      <description>&lt;h2 id=&#34;to-tweet-or-not-to-tweet&#34;&gt;To Tweet or Not to Tweet&lt;/h2&gt;
&lt;p&gt;It always seems I&amp;rsquo;m late to the party. For several years I pondered on the idea of joining &lt;a href=&#34;https://twitter.com/&#34; title=&#34;Twitter&#34;&gt;Twitter&lt;/a&gt;, but it never really made much sense to me &amp;ndash; at least at the time &amp;ndash; to join a social network where there were hardly any friends of mine&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;. Big mistake, that actually &lt;em&gt;is&lt;/em&gt; one of the cool things about twitter. Unlike Facebook, it &lt;em&gt;does&lt;/em&gt; provides an open space suitable for engaging in discussions, albeit short, of all sorts with interesting people who don&amp;rsquo;t really have to be your &amp;ldquo;friend.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;It turns out that shortly after joining twitter most people&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt; were already considering abandoning it in favor of &lt;a href=&#34;https://join.app.net/&#34; title=&#34;Join the Movement - App.net&#34;&gt;App.net&lt;/a&gt;. For the time being &lt;a href=&#34;https://join.app.net/&#34; title=&#34;Join the Movement - App.net&#34;&gt;App.net&lt;/a&gt; seems like a &lt;em&gt;niche&lt;/em&gt; thing, and most people seem to continue on twitter. Whether that stays that way for the next year or so depends on twitter and their recent policy changes that could well endanger the platform as we know it today.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Convert Image to PDF with Automator and Imagemagick</title>
      <link>https://andresmarrugo.net/blog/2012/10/18/image-to-pdf-with-automator-and-imagemagick/</link>
      <pubDate>Thu, 18 Oct 2012 22:30:00 -0500</pubDate>
      <guid>https://andresmarrugo.net/blog/2012/10/18/image-to-pdf-with-automator-and-imagemagick/</guid>
      <description>&lt;p&gt;I often use &lt;a href=&#34;http://www.imagemagick.org/script/index.php&#34;&gt;Imagemagick&lt;/a&gt; for image manipulation&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;. However, for simple conversion of an image to another format or similar things I have to go to the terminal and type something like the following&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;convert somefile.png somefile.pdf
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Which is quite simple, and much better than opening preview -&amp;gt; export&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;-&amp;gt;select pdf-&amp;gt; and hit save. But typing that for more than one image is &lt;em&gt;also&lt;/em&gt; tedious. So, I decided I&amp;rsquo;d better create a service that would essentially do the following.&lt;/p&gt;
&lt;p&gt;It would take the selected finder items, mainly images in &lt;code&gt;png&lt;/code&gt;, &lt;code&gt;jpeg&lt;/code&gt;, or whatever, and convert all of them to &lt;code&gt;pdf&lt;/code&gt;. Simple.&lt;/p&gt;</description>
    </item>
    <item>
      <title>My blog post writing workflow with Dropbox and Hazel</title>
      <link>https://andresmarrugo.net/blog/2012/10/15/blog-post-writing-workflow-dropbox-hazel/</link>
      <pubDate>Mon, 15 Oct 2012 23:44:00 -0500</pubDate>
      <guid>https://andresmarrugo.net/blog/2012/10/15/blog-post-writing-workflow-dropbox-hazel/</guid>
      <description>&lt;p&gt;It may seem that, for the most part, I&amp;rsquo;ve been blogging about blogging. No matter how pointless it seems, I &lt;em&gt;do&lt;/em&gt; think that this could prove useful to someone, in the same way I have benefited from others while setting up this site&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
&lt;p&gt;One of the things I like about having an &lt;a href=&#34;http://octopress.org/&#34; title=&#34;Octopress&#34;&gt;Octopress&lt;/a&gt; driven &lt;code&gt;txt&lt;/code&gt;-only blog is that I have the liberty to set things my way. The topic I am addressing here is that of writing blog posts on different devices&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt; with the help of Dropbox&lt;sup id=&#34;fnref:3&#34;&gt;&lt;a href=&#34;#fn:3&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;3&lt;/a&gt;&lt;/sup&gt; and &lt;a href=&#34;http://www.noodlesoft.com/hazel.php&#34; title=&#34;Noodlesoft | Hazel&#34;&gt;Hazel&lt;/a&gt;. I&amp;rsquo;m still working out the whole remote blogging thing, this is but the first stage of a soon-to-be remote blogging workflow with Octopress.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Spanish keyboard and Aperture</title>
      <link>https://andresmarrugo.net/blog/2012/10/07/spanish-keyboard-and-aperture/</link>
      <pubDate>Sun, 07 Oct 2012 00:36:00 -0500</pubDate>
      <guid>https://andresmarrugo.net/blog/2012/10/07/spanish-keyboard-and-aperture/</guid>
      <description>&lt;div class=&#34;aic&#34; style=&#34;width:320px&#34;&gt;&lt;a href=&#34;http://www.flickr.com/photos/copiancestral/8060866808/&#34; title=&#34;Mac keyboard by copiancestral, on Flickr&#34;&gt;&lt;img src=&#34;https://farm9.staticflickr.com/8030/8060866808_dc3b5dc915_n.jpg&#34; width=&#34;320&#34; height=&#34;240&#34; alt=&#34;20121007-PA077266&#34;&gt;&lt;/a&gt;&lt;br&gt;
My new keyboard.&lt;/div&gt;
It&#39;s been quite a while since I&#39;ve grown accustomed to switching back and forth between an english keyboard at home and a spanish keyboard at work. Like anything, at first it takes a while to get fully accustomed, but all in all it isn&#39;t too bad. This week my English keyboard at home died, so I bought a new one this time in Spanish, because that was what they had at the store. 
&lt;p&gt;One of the things I don&amp;rsquo;t like of the spanish keyboard &lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; is that most (if not all) applications design the shortcuts assuming an English keyboard. Therefore, what could be single key shortcut in the English keyboard becomes a double key shortcut in the  Spanish keyboard. And that&amp;rsquo;s not all.&lt;/p&gt;</description>
    </item>
    <item>
      <title>a service for writing day one footnotes inline</title>
      <link>https://andresmarrugo.net/blog/2012/10/01/a-service-for-writing-day-one-footnotes-inline/</link>
      <pubDate>Mon, 01 Oct 2012 22:31:00 -0500</pubDate>
      <guid>https://andresmarrugo.net/blog/2012/10/01/a-service-for-writing-day-one-footnotes-inline/</guid>
      <description>&lt;p&gt;I recently wrote about &lt;a href=&#34;http://andresmarrugo.net/blog/2012/09/29/footnotes-in-dayone/&#34;&gt;inserting footnotes in Day One&lt;/a&gt; and how it could be achieved with the new markdown support. I realize that ideally Day One should support multimarkdown footnotes, but this has not arrived yet. It could well be planned for a future release, but I&amp;rsquo;ll stick to my solution for the mean time.&lt;/p&gt;
&lt;p&gt;One of the tedious things about my solution to footnotes in &lt;a href=&#34;http://dayoneapp.com/&#34;&gt;Day One&lt;/a&gt; is that you have to &lt;em&gt;do&lt;/em&gt; everything manually. The insertion of the footnotes &lt;em&gt;plus&lt;/em&gt; the formatting, not to mention keeping count of the number of footnotes. For one or two footnotes this doesn&amp;rsquo;t seem like a big issue. But for several more it gets complicated.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; You have to put the superscript (&lt;code&gt;^&lt;/code&gt;), the number of the footnote, the horizontal line (which I think necessary) and the footnote itself. Therefore, I thought I could automate this&amp;ndash;somewhat.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Footnotes in Day One</title>
      <link>https://andresmarrugo.net/blog/2012/09/29/footnotes-in-dayone/</link>
      <pubDate>Sat, 29 Sep 2012 22:51:00 -0500</pubDate>
      <guid>https://andresmarrugo.net/blog/2012/09/29/footnotes-in-dayone/</guid>
      <description>&lt;p&gt;My favorite journaling app, &lt;a href=&#34;http://dayoneapp.com/&#34;&gt;Day One&lt;/a&gt;, just got updated to &lt;a href=&#34;http://dayoneapp.com/about/release-notes-mac/&#34;&gt;version 1.7.2, and it includes some really great new features&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It now includes more &lt;a href=&#34;http://fletcherpenney.net/multimarkdown/&#34;&gt;multimarkdown&lt;/a&gt; syntax like strike through, fenced code, and other nifty things. However one of the things I still find missing in Day One is multimarkdown footnotes. I&amp;rsquo;ve grown so accustomed to footnotes, that I don&amp;rsquo;t think I could live without them anymore.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
