<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Paul</title>
    <description>The latest articles on Forem by Paul (@elvezpablo).</description>
    <link>https://forem.com/elvezpablo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F267809%2F86bc41c0-c9f2-4c7a-bbe6-e705aaf8960e.jpeg</url>
      <title>Forem: Paul</title>
      <link>https://forem.com/elvezpablo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/elvezpablo"/>
    <language>en</language>
    <item>
      <title>Quick OSX brew migration</title>
      <dc:creator>Paul</dc:creator>
      <pubDate>Fri, 11 Aug 2023 14:46:41 +0000</pubDate>
      <link>https://forem.com/elvezpablo/quick-osx-brew-migration-43ec</link>
      <guid>https://forem.com/elvezpablo/quick-osx-brew-migration-43ec</guid>
      <description>&lt;p&gt;Looking for a quick way to migrate your &lt;code&gt;brew&lt;/code&gt; installed packages? Well look no further. Homebrew (&lt;a href="https://brew.sh/"&gt;https://brew.sh/&lt;/a&gt;) has a quick command to export a &lt;code&gt;Brewfile&lt;/code&gt; which can then be used to restore your packages on a new machine. &lt;/p&gt;

&lt;p&gt;Run the following to make the &lt;code&gt;Brewfile&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew bundle dump
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;and&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew bundle &lt;span class="nb"&gt;install&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;to install on a new machine. Thanks to &lt;a href="https://news.ycombinator.com/item?id=37084904"&gt;https://news.ycombinator.com/item?id=37084904&lt;/a&gt; for the tip!&lt;/p&gt;

</description>
      <category>brew</category>
      <category>homebrew</category>
      <category>osx</category>
      <category>cli</category>
    </item>
    <item>
      <title>Using git with Glitch</title>
      <dc:creator>Paul</dc:creator>
      <pubDate>Wed, 11 Nov 2020 15:27:27 +0000</pubDate>
      <link>https://forem.com/elvezpablo/using-git-with-glitch-5832</link>
      <guid>https://forem.com/elvezpablo/using-git-with-glitch-5832</guid>
      <description>&lt;p&gt;&lt;a href="https://glitch.com/" rel="noopener noreferrer"&gt;Glitch&lt;/a&gt; is a great place to host code samples for blogging and sketching out projects. My goal is to have a single source of truth for that code. Glitch has all the parts to do this with 1 gotcha. &lt;/p&gt;

&lt;h2&gt;
  
  
  Finding the Git url to clone the project.
&lt;/h2&gt;

&lt;p&gt;The key here is each project is a git repository. Glitch pulls this code from the &lt;code&gt;master&lt;/code&gt; branch on an interval to update the web project. &lt;/p&gt;

&lt;p&gt;Either create a project or open an existing project in glitch. &lt;/p&gt;

&lt;p&gt;Once open navigate to &lt;em&gt;Tools -&amp;gt; Import and Export -&amp;gt; Your project's Git URL&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Click the copy button.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Frepg7vmj1ta7szlyrrze.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Frepg7vmj1ta7szlyrrze.gif" alt="Git URL in Glitch"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Clone the repository on your computer and start committing! &lt;/p&gt;

&lt;h2&gt;
  
  
  Push to Master Workflow
&lt;/h2&gt;

&lt;p&gt;After making some changes it's time to commit and push to master. Turns out Glitch doesn't allow this by default but it can be overridden via the Terminal inside Glitch with the following command. &lt;/p&gt;

&lt;p&gt;&lt;code&gt;git config receive.denyCurrentBranch updateInstead&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Pushing will update and will change the output in a few minutes (non-scientific observation) but it doesn't sync up the IDE. For me this isn't a big deal as I would rather code locally.&lt;/p&gt;

&lt;p&gt;To get the IDE in sync run the following command. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fgulkxb05v7lrswyx8ln3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fgulkxb05v7lrswyx8ln3.png" alt="Resetting"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hope this helps someone!&lt;/p&gt;

</description>
      <category>git</category>
      <category>glitch</category>
    </item>
    <item>
      <title>A better code Quick Look</title>
      <dc:creator>Paul</dc:creator>
      <pubDate>Wed, 28 Oct 2020 14:39:51 +0000</pubDate>
      <link>https://forem.com/elvezpablo/a-better-code-quick-look-4flf</link>
      <guid>https://forem.com/elvezpablo/a-better-code-quick-look-4flf</guid>
      <description>&lt;p&gt;While trying to figure out how to get &lt;a href="https://en.wikipedia.org/wiki/Quick_Look"&gt;Quick Look&lt;/a&gt; working in &lt;em&gt;Catalina&lt;/em&gt; (&lt;em&gt;still working on that one&lt;/em&gt;). I found some great tips on installing plugins for additional features here &lt;a href="https://github.com/sindresorhus/quick-look-plugins"&gt;sindresorhus/quick-look-plugins&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;Here's the 3 simple steps for getting code to render and check out the above repo for more. &lt;/p&gt;

&lt;h2&gt;
  
  
  One Prerequisite
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;brew&lt;/code&gt; is suggested to install the plugins and is required for this guide. &lt;/p&gt;

&lt;h2&gt;
  
  
  Three Steps for Catalina
&lt;/h2&gt;

&lt;p&gt;Step 1: Install the plugin(s). There are &lt;a href="https://www.quicklookplugins.com/"&gt;many more&lt;/a&gt; if you poke around. &lt;/p&gt;

&lt;p&gt;&lt;code&gt;brew cask install qlcolorcode&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Additional removal of quarantine attributes steps for &lt;em&gt;Catalina&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Step 2: List the attributes you will be removing with&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;&lt;code&gt;xattr -r ~/Library/QuickLook&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;Step 3: Remove the attributes&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;&lt;code&gt;xattr -d -r com.apple.quarantine ~/Library/QuickLook&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it out by clicking a file and hitting the spacebar.
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--Bhl7q7dA--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/buvgdr5p8vrt6gd3semn.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--Bhl7q7dA--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/buvgdr5p8vrt6gd3semn.gif" alt="Quick Look Preview"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>osx</category>
      <category>quicklook</category>
      <category>mac</category>
    </item>
    <item>
      <title>Great Figma Plugin Article</title>
      <dc:creator>Paul</dc:creator>
      <pubDate>Fri, 29 May 2020 13:07:32 +0000</pubDate>
      <link>https://forem.com/elvezpablo/great-figma-plugin-article-10</link>
      <guid>https://forem.com/elvezpablo/great-figma-plugin-article-10</guid>
      <description>&lt;p&gt;Great article about building Figma plugins from Varun Vachhar. He covers the concepts and has some great suggestions about tools.  &lt;/p&gt;

&lt;p&gt;&lt;a href="https://varun.ca/figma-plugins/"&gt;https://varun.ca/figma-plugins/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>figma</category>
      <category>react</category>
      <category>design</category>
    </item>
    <item>
      <title>How to keep those darn tabs open</title>
      <dc:creator>Paul</dc:creator>
      <pubDate>Fri, 08 Nov 2019 21:13:40 +0000</pubDate>
      <link>https://forem.com/elvezpablo/how-to-keep-those-darn-tabs-open-5aha</link>
      <guid>https://forem.com/elvezpablo/how-to-keep-those-darn-tabs-open-5aha</guid>
      <description>&lt;p&gt;I know you have done it. You're spelunking through the code trying to find that one function with that one bug and you find it! VSCode shows you the file of interest in &lt;em&gt;preview mode&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Of course, it's so simple and if I just check to make sure it works with what I'm working on. . &lt;/p&gt;

&lt;p&gt;Then... gone. That file you spent so long trying to find was opened in preview mode and now you have to search again to find it. I know it's happened to you. Make it stop by setting both of these to false (or unchecking)&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;code&gt;workbench.editor.enablePreviewFromQuickOpen&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;workbench.editor.enablePreview&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Search and keep your context. Live long and prosper. &lt;/p&gt;

</description>
      <category>vscode</category>
    </item>
  </channel>
</rss>
