<?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>Cli on Technical Notes</title><link>http://luispa.com/en/tags/cli/</link><description>Recent content in Cli on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Sat, 19 Jul 2025 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Cross-platform CLI Tools</title><link>http://luispa.com/en/posts/2025-07-18-cli-multiplataforma/</link><pubDate>Sat, 19 Jul 2025 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2025-07-18-cli-multiplataforma/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-cli-multi.svg" alt="Cross-platform logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I share a selection of &lt;strong>cross-platform&lt;/strong> command-line tools that you can use interchangeably on &lt;strong>PowerShell, CMD, WSL2, macOS and Linux&lt;/strong>. These are modern, fast and lightweight utilities that replace or greatly improve classic tools like &lt;code>ls&lt;/code>, &lt;code>cd&lt;/code>, &lt;code>find&lt;/code> or even command history.&lt;/p>
&lt;p>They not only speed up everyday tasks, but also offer a more consistent user experience across systems. They don&amp;rsquo;t depend on specific shells like Bash or Zsh, and work the same whether you use PowerShell, Terminal, Alacritty, VSCode or any modern environment. As I discover new CLI utilities that fit this cross-platform, no-heavy-dependencies approach, I&amp;rsquo;ll keep adding them.&lt;/p></description></item><item><title>Windows for Development</title><link>http://luispa.com/en/posts/2024-08-25-win-desarrollo/</link><pubDate>Sun, 25 Aug 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-08-25-win-desarrollo/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-win-desarrollo.svg" alt="Windows for development logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe the steps to set up a Windows 11 machine as a development workstation for a cross-platform environment — Linux, macOS, and Windows. This is not oriented towards &lt;em>Microsoft/Windows-only&lt;/em> software development, but rather for those who like to develop on and for multiple platforms and environments.&lt;/p>
&lt;p>I start from a clean Windows installation (in English), with nothing installed. I took advantage of needing to set up a &lt;a href="http://luispa.com/en/posts/2024-08-23-dual-linux-win/">dual boot&lt;/a> and configured the operating system in a &lt;a href="http://luispa.com/en/posts/2024-08-24-win-decente-obsoleto/">lightweight&lt;/a> manner. The post starts with the CLI and WSL2, and in the second part I cover the tools and programming languages.&lt;/p>
&lt;br clear="left"/>
&lt;style>
table {
font-size: 0.8em;
}
&lt;/style></description></item></channel></rss>