<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Editors on</title><link>http://salopst.yearl.us/tags/editors/</link><description>Recent content in Editors on</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Sun, 10 Oct 2021 04:48:57 +0100</lastBuildDate><atom:link href="http://salopst.yearl.us/tags/editors/index.xml" rel="self" type="application/rss+xml"/><item><title>VS Code / VSCodium Extensions</title><link>http://salopst.yearl.us/vs-code-vscodium-extensions/</link><pubDate>Thu, 30 Sep 2021 15:20:32 +0100</pubDate><guid>http://salopst.yearl.us/vs-code-vscodium-extensions/</guid><description>&lt;p&gt;Some extensions for VS Code are not available when you search for them from within VSCodium. I have no idea why this is the case. Licensing issues?&lt;/p&gt;&#10;&lt;p&gt;quokka.js &lt;a href="https://marketplace.visualstudio.com/items?itemName=WallabyJs.quokka-vscode"&gt;https://marketplace.visualstudio.com/items?itemName=WallabyJs.quokka-vscode&lt;/a&gt; is one of those. Fortunately you can download the &lt;code&gt;*.visx&lt;/code&gt; file listed under &amp;ldquo;Rescouces&amp;rdquo;, and install that from VsCodium.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Listed (with a flatpak install) for me at:&#10;&lt;code&gt;~/.var/app/com.vscodium.codium/data/codium/extensions&lt;/code&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="my-installed-extensions"&gt;my installed extensions:&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ls ~/.var/app/com.vscodium.codium/data/codium/extensions | awk &lt;span style="color:#e6db74"&gt;&amp;#39;{print $8}&amp;#39;&lt;/span&gt;;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;abusaidm.html-snippets-0.2.1&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;arcticicestudio.nord-visual-studio-code-0.15.0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;artisanbytecrafter.poptheme-1.0.3&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;bierner.markdown-mermaid-1.12.1&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;budparr.language-hugo-vscode-1.2.0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;coenraads.bracket-pair-colorizer-2-0.1.4&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;davidanson.vscode-markdownlint-0.44.0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;dbaeumer.vscode-eslint-2.1.20&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;donjayamanne.githistory-0.6.18&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;dracula-theme.theme-dracula-2.24.0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;esbenp.prettier-vscode-8.1.0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;firefox-devtools.vscode-firefox-debug-2.9.1&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;goodbaikin.org-preview-1.1.0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;josee9988.minifyall-2.9.3&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;mhutchie.git-graph-1.30.0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ms-azuretools.vscode-docker-1.16.1&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ms-python.python-2021.9.1246542782&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ms-toolsai.jupyter-2021.8.12&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ms-vscode.theme-tomorrowkit-0.1.4&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;msjsdiag.debugger-for-chrome-4.12.6&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;mushan.vscode-paste-image-1.0.4&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;patbenatar.advanced-new-file-1.2.2&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;redhat.vscode-xml-0.18.0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ritwickdey.liveserver-5.6.1&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;robole.marky-edit-0.5.1&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;wallabyjs.quokka-vscode-1.0.402&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;wesbos.theme-cobalt2-2.1.6&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Or &lt;code&gt;vscodium --list-extensions | xargs -L 1 echo vscodium --install-extension&lt;/code&gt; will do the same thing.&lt;/p&gt;</description></item><item><title>Vscodium modifying Emmet snippets</title><link>http://salopst.yearl.us/vs-code-vscodium-modifying-emmet-snippets/</link><pubDate>Thu, 30 Sep 2021 13:20:32 +0100</pubDate><guid>http://salopst.yearl.us/vs-code-vscodium-modifying-emmet-snippets/</guid><description>&lt;p&gt;&lt;a href="https://emmet.io/"&gt;Emmet&lt;/a&gt; is an HTML/CSS code completion extension to VS Code (or the more libre version, Vscodium) editor/ half-an-IDE. Snippets of code are stored locally in a &lt;code&gt;snippets.json&lt;/code&gt; file, and these snippets are called into being after being triggered by a certain sequence of key-strokes.&lt;/p&gt;&#10;&lt;p&gt;By default, in a blank HTML document, upon using the trigger &lt;code&gt;!+TAB&lt;/code&gt;, Emmet will insert the following boilerplate/skeleton HTML:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-html" data-lang="html"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#75715e"&gt;&amp;lt;!DOCTYPE html&amp;gt;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&amp;lt;&lt;span style="color:#f92672"&gt;html&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;lang&lt;/span&gt;&lt;span style="color:#f92672"&gt;=&lt;/span&gt;&lt;span style="color:#e6db74"&gt;&amp;#34;en&amp;#34;&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&amp;lt;&lt;span style="color:#f92672"&gt;head&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &amp;lt;&lt;span style="color:#f92672"&gt;meta&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;charset&lt;/span&gt;&lt;span style="color:#f92672"&gt;=&lt;/span&gt;&lt;span style="color:#e6db74"&gt;&amp;#34;UTF-8&amp;#34;&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &amp;lt;&lt;span style="color:#f92672"&gt;meta&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;http-equiv&lt;/span&gt;&lt;span style="color:#f92672"&gt;=&lt;/span&gt;&lt;span style="color:#e6db74"&gt;&amp;#34;X-UA-Compatible&amp;#34;&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;content&lt;/span&gt;&lt;span style="color:#f92672"&gt;=&lt;/span&gt;&lt;span style="color:#e6db74"&gt;&amp;#34;IE=edge&amp;#34;&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &amp;lt;&lt;span style="color:#f92672"&gt;meta&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;name&lt;/span&gt;&lt;span style="color:#f92672"&gt;=&lt;/span&gt;&lt;span style="color:#e6db74"&gt;&amp;#34;viewport&amp;#34;&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;content&lt;/span&gt;&lt;span style="color:#f92672"&gt;=&lt;/span&gt;&lt;span style="color:#e6db74"&gt;&amp;#34;width=device-width, initial-scale=1.0&amp;#34;&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &amp;lt;&lt;span style="color:#f92672"&gt;title&lt;/span&gt;&amp;gt;Document&amp;lt;/&lt;span style="color:#f92672"&gt;title&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&amp;lt;/&lt;span style="color:#f92672"&gt;head&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&amp;lt;&lt;span style="color:#f92672"&gt;body&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&amp;lt;/&lt;span style="color:#f92672"&gt;body&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&amp;lt;/&lt;span style="color:#f92672"&gt;html&lt;/span&gt;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Which is cool and all, but might lack a couple of things you commonly use on all you pages. So let&amp;rsquo;s modify this default template, the snippet code of which looks like:&lt;/p&gt;</description></item><item><title>Vscodium Shortcuts, Debugging, and the Terminal</title><link>http://salopst.yearl.us/vs-code-vscodium-shortcuts-debugging-and-the-terminal/</link><pubDate>Thu, 30 Sep 2021 09:13:11 +0100</pubDate><guid>http://salopst.yearl.us/vs-code-vscodium-shortcuts-debugging-and-the-terminal/</guid><description>&lt;p&gt;After going ahead and updating Emacs, I thought I&amp;rsquo;d try the thing that all the kids are talking about&amp;ndash; VS Code. Or, if you are anything like me and remember the hoary days of the Browser Wars, &lt;a href="https://vscodium.com/"&gt;&lt;strong&gt;VSCodium&lt;/strong&gt;&lt;/a&gt;, the telemtry-disabled version of the editor.&lt;/p&gt;&#10;&lt;h2 id="debugging"&gt;Debugging&lt;/h2&gt;&#10;&lt;p&gt;Since the primary objective is to learn some JSessy things, the first I need to be doing is figuring out debugging.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=tC91t9OvVHA"&gt;The New Way To Debug JavaScript in VS Code - No Extension Required &amp;ndash; YT, July 2021&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Image file locations in Hugo</title><link>http://salopst.yearl.us/image-flie-locations-in-hugo-static-site-generator/</link><pubDate>Mon, 27 Sep 2021 14:50:23 +0100</pubDate><guid>http://salopst.yearl.us/image-flie-locations-in-hugo-static-site-generator/</guid><description>&lt;p&gt;The images referenced from from the posts here currently live in three locations, based at Hugo&amp;rsquo;s root, ie. relative to &lt;code&gt;config.toml&lt;/code&gt;:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;├── archetypes&#10;├── config.toml&#10;├── static&#10;| └── wp-uploads&#10;| ├── whatever-historic-filename.png&#10;| ├── 2000-01-01-kinda-like-the-alt-text.png&#10;├── content&#10;| └── img&#10;| ├── uploads&#10;| | ├── 2000-01-01-kinda-like-the-alt-text.png&#10;| └── post&#10;| ├── 2000-01-01-the-filename-is-the-slug-kinda.md&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;```/static/wp-uploads&lt;code&gt; &lt;/code&gt;/content/img/uploads/1&lt;/p&gt;&#10;&lt;h2 id="i-put-images-inside-a-folder-called-images-under-contentpost-this-is-the-file-structure-for-the-hugo-project"&gt;I put images inside a folder called images under content/post/. This is the file structure for the Hugo project:&lt;/h2&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;├── archetypes&#10;├── config.toml&#10;├── content&#10;| └── post&#10;| ├── your-post.md&#10;| ├── images&#10;| | ├── your-image.png&#10;&lt;/code&gt;&lt;/pre&gt;&lt;hr&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="everything-you-put-on-static-folder-will-be-served-at-the-root-of-your-webiste-ex"&gt;Everything you put on static folder will be served at the root of your webiste, ex:&lt;/h2&gt;&#10;&lt;p&gt;/static&#10;/cover.jpg&#10;/img/&#10;/cover2.jpg&#10;/foo&#10;/cover3.png&lt;/p&gt;</description></item><item><title>Installing Emacs 28.0.50 from source on Ubuntu 21.04</title><link>http://salopst.yearl.us/installing-emacs-28-0-50-from-source-on-ubuntu-21-04/</link><pubDate>Tue, 28 Sep 2021 05:30:00 +0100</pubDate><guid>http://salopst.yearl.us/installing-emacs-28-0-50-from-source-on-ubuntu-21-04/</guid><description>&lt;h2 id="latest-emacs-28050"&gt;Latest Emacs (28.0.50)&lt;/h2&gt;&#10;&lt;p&gt;There has been much discussion in various Emacs fora about the speed increase brought about by the inclusion of nativecomp, that is the build option &lt;code&gt;--with-native-compilation&lt;/code&gt;. This essentially means that support has been added for compiling EmacsLisp to native code using &lt;code&gt;libgccjit&lt;/code&gt;. Now all Elisp packages shipped with Emacs are compiled to native code, providing a noticeable out-of-the-box performance improvement.&lt;/p&gt;&#10;&lt;p&gt;My previously installed version of 26.3 that is still current with the base install of Pop!_OS (and that available from the &lt;code&gt;apt&lt;/code&gt; repositories) does not have this feature.&lt;/p&gt;</description></item><item><title>Exploring Typora... and now Hugo</title><link>http://salopst.yearl.us/exploring-the-typora-markdown-editor/</link><pubDate>Tue, 17 Jul 2018 13:00:00 +0000</pubDate><guid>http://salopst.yearl.us/exploring-the-typora-markdown-editor/</guid><description>&lt;p&gt;This wee MD file was created back on &lt;code&gt;date: 2018-07-17 &lt;/code&gt; to explore a new x-platform markdown editor I had heard about called Typora, &lt;a href="https://typora.io/"&gt;https://typora.io/&lt;/a&gt;. I was using a Mac then, a mid-2012 MPB, that had at that point done sterling service for 6 years and 13 days.&lt;/p&gt;&#10;&lt;p&gt;The below is just a bunch of BS written back then to try out some of the splendid features it seemed to offer. Now the challenge is to see if some of the non-markdown features render under Hugo.&lt;/p&gt;</description></item><item><title>Posting from IA Writer to Wordpress (Coleman)</title><link>http://salopst.yearl.us/blog-post-ia-writer-to-wordpress-with-ruby/</link><pubDate>Sun, 24 Apr 2016 00:01:57 +0000</pubDate><guid>http://salopst.yearl.us/blog-post-ia-writer-to-wordpress-with-ruby/</guid><description>&lt;h2 id="0-wha"&gt;0. Wha?&lt;/h2&gt;&#10;&lt;p&gt;With the coming of the new &lt;a href="http://stephen.yearl.us/rescue-doggie-diary/"&gt;doggie into the house&lt;/a&gt;, perhaps I will again add more content to the &lt;a href="http://stephen.yearl.us"&gt;bloggy thing&lt;/a&gt; that I have kinda sorta not really been keeping over the last little while.&lt;/p&gt;&#10;&lt;p&gt;Probably this has been done by someone else on the Intertubz, but ach, why not. I have some time on my hands, so here are running notes in &lt;a href="https://ia.net/writer"&gt;IA Writer&lt;/a&gt; that will make its way to a &lt;a href="https://www.wordpress.com"&gt;Wordpress&lt;/a&gt; post by some means or other. There’s nothing special about IA writer, by the way. Well, there &lt;strong&gt;is&lt;/strong&gt;, but not for the purposes of the Wordpress posting. The same code should work with any plain-ish text file coming from any editor.&lt;/p&gt;</description></item><item><title>Atom themes and packages; note to self</title><link>http://salopst.yearl.us/atom-themes-and-packages-note-to-self/</link><pubDate>Mon, 30 Mar 2015 11:09:10 +0000</pubDate><guid>http://salopst.yearl.us/atom-themes-and-packages-note-to-self/</guid><description>&lt;p&gt;I never really did manage to get into the swing of things with &lt;a href="http://www.sublimetext.com/"&gt;Sublime Text&lt;/a&gt; everyone&amp;rsquo;s favourite general-purpose editor since, well &lt;a href="https://macromates.com/"&gt;TextMate&lt;/a&gt; fell out of favour ca. 2009-ish, and generally stuck to TextMate. Sure there&amp;rsquo;s &lt;a href="http://www.vim.org/"&gt;VIM&lt;/a&gt; (and it is awesome), but really? Life &lt;em&gt;is&lt;/em&gt; better with a pretty and functional editor.&lt;/p&gt;&#10;&lt;p&gt;And then along came &lt;a href="https://atom.io/"&gt;Atom&lt;/a&gt;&amp;hellip; as well as a few others: Brackets and Light Table to name the other two newbies, all better described at &lt;a href="http://www.sitepoint.com/sitepoint-smackdown-atom-vs-brackets-vs-light-table-vs-sublime-text/"&gt;SitePoint&lt;/a&gt;. Suffice to say that Atom won for me. Despite it being very Sublime-like, I felt comfortable with it. So here, culled from .zsh_history, those Themes and Packages that I have installed and not uninstalled over the last eight months or so:&lt;/p&gt;</description></item><item><title>Online LaTeX editing tools</title><link>http://salopst.yearl.us/online-latex-editing-tools/</link><pubDate>Sun, 17 Feb 2013 13:12:07 +0000</pubDate><guid>http://salopst.yearl.us/online-latex-editing-tools/</guid><description>&lt;p&gt;For whatever reason, I&amp;rsquo;ve bumped into a number of in-browser &lt;code&gt;\LaTeX&lt;/code&gt; editing tools recently. I guess these are mostly useful for collaborative efforts, and I can see a reason why one would not want to use Subversion or Git. I mean Eldest is just coming of an age where he&amp;rsquo;s seeing computers as tools for his own use rather than just vectors of games/educational materials/movies. Because I am a benevolent father-dictator, he&amp;rsquo;s already familiar with &lt;code&gt;\LaTeX&lt;/code&gt; (and actually loves Computer Modern), and has decided to set all his writings in &lt;code&gt;\LaTeX&lt;/code&gt; prior to submission. Good for him. I love the fact that he was complaining about fonts on the MacBook Airs at school, and the pain of writing in MS Word. Good boy!&lt;/p&gt;</description></item></channel></rss>