News for hackers. Stuff that matters.

alzee

Re:Start all of your commands with a comma on Sunday February 08, 2026 @02:37AM (#46932184)
> most of the examples OP gave are usually available as short options

Yes, but a lot of commands behave differently for -h and --help.

> aliasing ,s to sudo is certainly possible

Sure, but my ,s key sequence doesn’t just expand to sudo. It actually moves the cursor to the start of the current line, prefixes the command with sudo, and then moves the cursor to the end of the line. The idea is when you type a command which requires root privileges but forget to use sudo, you can just hit ctrl+p ,s to fetch the previous command and prefix it with sudo. This is what it looks like in ~/.inputrc: ",s":"^Asudo ^E"

Re:Start all of your commands with a comma on Sunday February 08, 2026 @02:15AM (#46932039)
Yes, I meant ~/.inputrc .
Re:Start all of your commands with a comma on Saturday February 07, 2026 @07:22AM (#46923274)
Using commas in filenames feels kind of weird to me, but I do use a comma as the initiator for my Bash key sequences. For example: ,, expands to $ ,h expands to --help ,v expands to --version ,s prefixes sudo

You put keyseqs in ~/.inputc, set a keyseq-timeout, and it just works.

You shouldn’t start filenames or identifiers with digits.