We recently logged jqq (an interactive wrapper around jq), but Ruby means installing it can be a burden. jqp wraps gojq, so it compiles to a universal binary and the UI is pretty compelling as well.

Here’s the motivation behind this Rust-based TUI:

I do most of my git work in a terminal but I frequently found myself using git GUIs for some use-cases like: index, commit, diff, stash, blame and log.

Unfortunately popular git GUIs all fail on giant repositories or become unresponsive and unusable.

GitUI provides you with the user experience and comfort of a git GUI but right in your terminal while being portable, fast, free and open source.

So you got tired of AI just suggesting code edits, and now you want it to help you run code, too. Silly human, you have come to the right place. This will take five steps.

This gets an A+ for creativity. Fire up your shell, then launch Neovim. Then shell out with :VimShell to get back to where you started, but with Copilot suggestions.

My guess is the ergonomics of this are… bad. But a cool hack, regardless!

Carlos Becker shares some SSH tips he’s learned over the years, including YubiKey integration. Did you know you can SSH straight into tmux?!

Pulls data from many sources. Built with Go. Demo video here.

Rewind like video, see output in a pager, Vim-like keymaps, and more. “Viddy well, gopher. Viddy well.”

Brandon Rhodes’s solution to conflicts between his ~/bin scripts and system binaries: the humble comma

I heartily recommend this technique to anyone with their own ~/bin/ directory who wants their command names kept clean, tidy, and completely orthogonal to any commands that the future might bring to your system. The approach has worked for me for something like a decade, so you should find it immensely robust. And, finally, it’s just plain fun.

Cheeky title, but they’re talking about cheat, which is different than man and info in that it’s entirely example based and community maintained.

The cheat system cuts to the chase. You don’t have to piece together clues about how to use a command. You just follow the examples. Of course, for complex commands, it’s not a shortcut for a thorough study of the actual documentation, but for quick reference, it’s as fast as it gets.

Highly customizable, easy-to-use, and minimal terminal styled website template.

Building a simple website with LiveTerm only takes minutes, and you only need to work with one file: config.json. After you cloned this repository, simply run yarn install && yarn dev and start editing config.json to build your website!

Powered by Next.js.

A searchable, templated catalog of popular terminal commands curated from across the internet.

Pretty sweet resource from our friends at Warp. Contribute your own commands on GitHub.

Currently supports SQLite and CSV. MySQL and Postgres are on the roadmap. Built with Bubble Tea.

This guide by Josh Comeau is Josh doing what Josh does so well: taking complex/arcane/technical topics and making them approachable & fun for his audience.

It takes years of practice to become a terminal guru, but here’s the good news: we can take a shortcut. We don’t really need to know 98% of the stuff you can do with a terminal. If we focus on the most-important critical fundamentals, we should be able to become comfortable with the command line in a remarkably short amount of time. ✨

That’s what this blog post is all about.

This week we’re bringing The Changelog to Go Time — we had an awesome conversation with Toby Padilla, Co-Founder at Charm where they’re building tools to make the command line glamorous. Toby and the team at Charm have gone “all in” on Go — all of Charm is written in Go. They moved to Go from other languages, saying “Go is the answer to building these type of tools.” And even on this episode Toby says “I love Rust, it’s really cool, it’s a super-exciting language, but I jumped ship. I wanna be more productive, I wanna use all the fun toys, and so I started doing Go.” Clearly this episode will be in good company here on Go Time.

We talk about the state of the art, the next big thing happening on the command line and in ssh-land. They have an array of open source tooling to build great apps for the terminal and Charm Cloud to power a new generation of CLI apps. We talk through all their tooling, where things are headed for CLI apps, the focus and attention of their team, and what’s to come in bringing glamor to the command line.

This week we’re talking to Toby Padilla, Co-Founder at Charm — where they build tools to make the command line glamorous. We talk about the state of the art, the next big thing happening on the command line and in ssh-land. They have an array of open source tooling to build great apps for the terminal and Charm Cloud to power a new generation of CLI apps. We talk through all their tooling, where things are headed for CLI apps, the focus and attention of their team, and what’s to come in bringing glamor to the command line.

If you ssh a lot, you may get some serious value out of this suite of (currently 8) related tools and shortcuts. ssh-ping checks if a host is reachable using ssh_config, ssh-diff diffs a file over SSH, etc.

Your first thought when reading that headline might’ve been _WebAssembly. Mine was! But no, that is not how Browsix does its thing:

Browsix is a framework that bridges the considerable gap between conventional operating systems and the browser, enabling unmodified programs expecting a Unix-like environment to run directly in the browser. Browsix does this by mapping low-level Unix primitives, like processes and system calls, onto existing browser APIs, like Web Workers and postMessage.

They have examples of this tech enabling a terminal in the browser, a Latex editor, and even a client/server-based meme generator written in JS and Go.

Turns out the pass command on your local Linux box can be used for a bunch of encryption-related things in addition to what most of us use it for: managing a user’s password.

One cool example is you can hide API keys from shoulder surfers (and history’s memory) by storing the key encrypted on disk and using pass to access it at runtime:

curl -H "API-Key: $(pass provider/api_key)" ...

Run ping, DNS, TLS & HTTP test against any URL or host with a single command.

One-liners with explanations, a short tutorial, and links to other resources.

What was I doing the last time I was here?

We’re linking to the repo, but the idea is where it’s at. The code is a one-liner (if you’re using zsh)

grep -v "jog" ~/.zsh_history_ext | grep -a --color=never "${PWD}   " | cut -f1 -d"|" | tail

Then you add this to your .zshrc

function zshaddhistory() {
	echo "${1%%$'\n'}|${PWD}   " >> ~/.zsh_history_ext
}

Now you’re all set for the next time you need to jog your memory!

This is a fun post about the inner workings of terminal emulators. In it you’ll find:

1. Animations demonstrating how ANSI escape codes are interpreted
2. Some small Rust programs to show the terminal’s capabilities
3. How to cause mischief with this knowledge

A list of places where you can get the weather, your IP Address, recent news, word translations, and other useful things straight from curl and other hacker-friendly terminal tools.

I’m sharing this because I’m watching this course, so learn with me as I learn from Colt Steele. It’s awesome because it has chapters so you can easily jump to the sections that interest you most.

Touch cat tail. Find man head. Who?

The previous seven words are common Linux commands. If you are a programmer, you are likely going to need to use Linux and terminal commands at some point.

All these commands work on Linux, macOS, WSL, and anywhere you have a UNIX environment.

Pairs well with Modern Unix tools and Oh my! Zsh. 🍷

Martin Tournoij lays out a bunch of ways he finds zsh more compelling than bash.

There are many more things. I’m not going to list them all here. None of this is new; much (if not all?) of this has around for 20 years, if not longer. I don’t know why bash is the de-facto default, or why people spend time on complex solutions to work around bash problems when zsh solves them. I guess because Linux used a lot of GNU stuff and bash was came with it, and GNU stuff was (and is) using bash. Not a very good reason, certainly not one 30 years later.

I’ve never gone full mouseless (nor do I necessarily recommend it), but there’s extreme productivity wins to be mined by keeping your hands on the home row as much as possible.

Building a development environment with the shell as a keystone offers multiple benefits. You can use tools that fit nicely with each other, you can customize everything depending on your own needs, and the biggest of all, you can control your entire development environment with your keyboard. This can save a lot of cognitive energy as well as deliver a pleasant user experience.

This is an excellent walk-through on Smashing Mag for those ready to level up their terminal game:

Today, I’d like to share with you these tools so that you too can increase your efficiency and your comfort in your daily job. They work well together — shaping what I call my Mouseless Development Environment. More precisely, we’ll discuss:

• Why using the Linux shell can be very powerful when working with plain text (including code);
• Why using the dreaded Arch Linux;
• The advantage of a tiling window manager;
• How to have a great terminal experience with URxvt, tmux, and tmuxp;
• Why Vim can become your best friend.