toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

277
active users

#commandline

4 posts4 participants0 posts today

Well, I finally found something for which a normal person will need to use the command line.

I was trying to play the Amnesia: The Dark Descent, and it complained that it couldn't find /usr/lib/libtheora.so.0

The solution was to make a symlink:

sudo ln /usr/lib/libtheora.so /usr/lib/libtheora.so.0

It's a simple fix, but not at all easy to figure out if you're not comfortable with the command line.

How-To Geek: Microsoft’s New Text Editor Is a Vim and Nano Alternative. “Microsoft just released ‘Edit’ as a new command-line text editor, which will soon be a built-in Windows application. It’s inspired by the MS-DOS Edit program from the 1990s, and it’s already open-source software.”

https://rbfirehose.com/2025/05/20/how-to-geek-microsofts-new-text-editor-is-a-vim-and-nano-alternative/

ResearchBuzz: Firehose | Individual posts from ResearchBuzz · How-To Geek: Microsoft’s New Text Editor Is a Vim and Nano Alternative | ResearchBuzz: Firehose
More from ResearchBuzz: Firehose

Notes from the PyCon open space session about dotfiles

Commonly-mentioned shells: fish, conch, zsh

Starship: Universal prompt written in rust starship.rs/

Chezmoi: dotfile manager - can also generate dotfiles based on a template chezmoi.io/user-guide/command-

Dotbot: another dotfile manager
github.com/anishathalye/dotbot

Atuin: magical shell history atuin.sh/

Direnv: activate venvs on entering a directory
Hammerspoon: automate MacOS UI actions with Lua code

Mise: replaces tools like pyenv, nvm, etc.
mise.jdx.dev/

Just: a command runner, similar to Make but only for triggering sequence of command github.com/casey/just

Simon Willison's llm for command-line access to LLMS: github.com/simonw/llm

Lazygit: CLI tool for git to do stuff github.com/jesseduffield/lazyg

Distrobox: run different Linux distributions in containers, but merge them with your host disk and dotfiles distrobox.it/

UV run: use it to run Python scripts in different venvs. Combine with command-line packages like Click or cyclopts to write and run your own scripts

thefuck: corrects weeks in the previous command in the history. Could alias it to 'wat' if you want to avoid the profanity
github.com/nvbn/thefuck

Article: How to train your keyboard tighten.com/insights/how-to-tr

Idea: put aliases in a separate file and then write an alias to edit that file and then source the newly-edited alias file.

Idea: start all your command name with a comma, so it's like a namespace for your customizations. Then you can hit comma-tab to get a list of your commands.

Overmind: process manager for running multiple processes inside a tmux session
github.com/DarthSim/overmind
Tmuxinator is similar: github.com/tmuxinator/tmuxinat

Offby1.website: Chris R's blog

terminaltrove.com/ - index of terminal apps that also will send emails about new tools

starship.rsStarship: Cross-Shell PromptStarship is the minimal, blazing fast, and extremely customizable prompt for any shell! Shows the information you need, while staying sleek and minimal. Quick installation available for Bash, Fish, ZSH, Ion, Tcsh, Elvish, Nu, Xonsh, Cmd, and Powershell.
Replied in thread

What brought you to #Emacs?

@myTerminal I was using Tmux, Vim, Bash, AWK, and FZF, and I kept trying to write scripts for all of these programs that would allow me more coordination between them. For example, I once wanted to launch a process from Vim in a second terminal in a Tmux split-screen, capture it’s output into a temporary file, then when the process exited, use AWK to select symbols from the file that I could later feed into FZF. Or I would write a little wrapper Bash script that would run a build process and send a notification and trigger Tmux to automatically switch to the shell when the process completed.

I was always thinking to myself how I wished all of these separate tools, which were all doing one just thing and doing it well (the Unix philosophy), could be connected together without needing to use pipes or complicated message passing through temporary files or through DBus. And I also wished they were all written in the same programming language, instead of having a different language for Bash, AWK, VimScript, and the config languages for Tmux, or using long chains of CLI options stored into partial script files.

Then it hit me one day that this thing that I was wishing for, which coordinated between the terminal multiplexer, command shell, editor, and auto-completion framework and was all scripted with just one programming language, this thing already existed and it was called Emacs.

Then I finally understood what all the fuss was about, and switched to Emacs forever.

#tech#software#lisp

POSIX people, I need a tool recommendation:

I want a tool that will listen on stdin for a tar file and run a commandline for every file encountered, with the file being piped to it.

Ideally, I don't want things to touch the disk, because the tar file and files within it are likely to be big.

Is there a POSIX-style tool for this?