You could make randc display the images in-line as the w3m browser used to do with X11 xterm in the early 00s. :)
As someone who started using Linux in 1998 and has used a variety of command-line systems before and since, I find your command set interesting. :) If I hadn't known about the help command, it would have been the second thing I tried after repeated attempts at tab completion and maybe ls /bin too. (I'm sure even older Unix users would have been slightly disturbed by my use of tab completion. :p ) But help is a good command. I had to laugh when you declared your command list to be intuitive when the command to list file contents is called cat! ;) It certainly is intuitive for people familiar with the Unix command line and I can understand wanting to exclude others for certain purposes, but I lived through the era where everyone was talking about intuitive interfaces and so I had to laugh. :D
On a practical note, I see you mention glob patterns but cat doesn't support them. I used DOS heavily in the 90s and I use PowerShell a bit now, and I can tell you that inconsistencies in how different commands parse their command lines can be really uncomfortable. Unix systems have the shell handle pattern expansion, so it's always consistent. After years of DOS, I found that to be a relief. But why do I want cat to take patterns? I find typing unfamiliar words accurately to be hard, so whenever I'm stuck without tab completion, I use patterns. It's become a habit because sometimes, patterns are quicker.
This might be a bug:
In Firefox, open blog.md opens a complicated XML file with no style information. Browser info; (thanks for the handy command): anonymous@protiumx.dev:~$ uname
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:101.0) Gecko/20100101 Firefox/101.0
Outside the terminal, I'm sorry to say I find the blog pages hard to read. My eyes don't adjust well to low contrast, and when I try to read it anyway, I get unpleasantly dazzled by brighter bits. I had the same problem with DOS in the 90s; it's a good thing I never had to use it for work. In Linux, when I had too little disk space for both Emacs and X Windows, I chose X Windows because it had a configurable xterm. In both DOS and Linux, there were a lot of programs I just didn't use because I couldn't make their displays comfortable. But on the web in recent years, I used to use a contrast enhancer but the only good one of those turned out to include some really nasty spyware. I should look again to see if others have got good.
You could make randc display the images in-line as the w3m browser used to do with X11 xterm in the early 00s. :)
As someone who started using Linux in 1998 and has used a variety of command-line systems before and since, I find your command set interesting. :) If I hadn't known about the help command, it would have been the second thing I tried after repeated attempts at tab completion and maybe
ls /bintoo. (I'm sure even older Unix users would have been slightly disturbed by my use of tab completion. :p ) Buthelpis a good command. I had to laugh when you declared your command list to be intuitive when the command to list file contents is calledcat! ;) It certainly is intuitive for people familiar with the Unix command line and I can understand wanting to exclude others for certain purposes, but I lived through the era where everyone was talking about intuitive interfaces and so I had to laugh. :DOn a practical note, I see you mention glob patterns but cat doesn't support them. I used DOS heavily in the 90s and I use PowerShell a bit now, and I can tell you that inconsistencies in how different commands parse their command lines can be really uncomfortable. Unix systems have the shell handle pattern expansion, so it's always consistent. After years of DOS, I found that to be a relief. But why do I want cat to take patterns? I find typing unfamiliar words accurately to be hard, so whenever I'm stuck without tab completion, I use patterns. It's become a habit because sometimes, patterns are quicker.
This might be a bug:
In Firefox,
open blog.mdopens a complicated XML file with no style information. Browser info; (thanks for the handy command):anonymous@protiumx.dev:~$ uname
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:101.0) Gecko/20100101 Firefox/101.0
Outside the terminal, I'm sorry to say I find the blog pages hard to read. My eyes don't adjust well to low contrast, and when I try to read it anyway, I get unpleasantly dazzled by brighter bits. I had the same problem with DOS in the 90s; it's a good thing I never had to use it for work. In Linux, when I had too little disk space for both Emacs and X Windows, I chose X Windows because it had a configurable xterm. In both DOS and Linux, there were a lot of programs I just didn't use because I couldn't make their displays comfortable. But on the web in recent years, I used to use a contrast enhancer but the only good one of those turned out to include some really nasty spyware. I should look again to see if others have got good.
Thank you for the insightful comment!
My bad, I forgot that the blog.md file is actually “virtual”, parsed from the RSS feed. I will add a fix later.
Tab autocomplete shouldn’t be difficult to implement, I might take a look as well.
Cheers!