If you like command line Unix tools, the Inconsolation blog is pretty good. He's currently running through the tools alphabetically.
A collection of Unix terminal/console/curses tools
41–50 of 50 posts
Re: A collection of Unix terminal/console/curses tools
#42I'm a big fan of Joey Hess' moreutils - https://joeyh.name/code/moreutils/ Examples: - sponge: read in all of stdin, then write to the given file. Great for pipelines: sed "s/root/toor/" /etc/passwd | grep -v joey | sponge /etc/passwd - vipe: easily drop a $EDITOR instance in the middle of a pipe chain - ts: timestamp all standard input; great for long-running output
I hope my own collection of related tools is also useful?
https://github.com/skx/sysadmin-util
More focused on those a sysadmin might prefer than general-use, but contributions or updates are welcome.
Re: A collection of Unix terminal/console/curses tools
#43I would like to see a graphical terminal emulator. When I mean by this is that the terminal emulator works the same as usual- it should display normal output, support ANSI escape sequences and have scroll-back. But it also should be able to display graphics. If your UNIX command line program happens to output a graph, it shows up on the terminal. The graph is embedded inline with the text and you can scroll back to i…
Check out terminology [0]. The video is quite long but impressive.
There was a work by someone on github for building a new kind of terminal. It wasn't line-based, rather "context-based": the output of the command was written next to the input, but you could write commands in the same terminal next to each other. It was some amazing stuff, but I can't find it (I think the logo was an octopus or something like that, and the "backend" was emacs)
Re: A collection of Unix terminal/console/curses tools
#44I'm a big fan of Joey Hess' moreutils - https://joeyh.name/code/moreutils/ Examples: - sponge: read in all of stdin, then write to the given file. Great for pipelines: sed "s/root/toor/" /etc/passwd | grep -v joey | sponge /etc/passwd - vipe: easily drop a $EDITOR instance in the middle of a pipe chain - ts: timestamp all standard input; great for long-running output
Although there's some real gems in there (I can't believe I never ran across vipe before!), its Debian package conflicts with the GNU parallel package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718816 Quite annoying.
Re: A collection of Unix terminal/console/curses tools
#45I know lists like this will almost always contain at least one command that I, or any other sys admin on here, would use fairly regularly. But it would be nice if just once an article about "obscure" CLI commands didn't include stuff that's the most basic of essential every day staples for any *nix administrator. Including stuff like vi and emacs is just ridiculous, quite frankly. If you haven't heard of them already…
> Maybe my job this weekend will be to write my own version of these documents but with a decent selection of programs, descriptions and example usages?
Maybe your job this weekend should be to get a little exercise before writing on the internet?
It's a nice little summary of cool tools. "Some are little-known, some are just too useful to miss, some are pure obscure".
Re: A collection of Unix terminal/console/curses tools
#46My latest discovery: jq - command line json processing, formatting and colouring.
I was going to mention jq. It's great, and replaces the previous json tool I was using (can't remember the name now, but it wasn't as useful.) I hope it becomes more popular.
Re: A collection of Unix terminal/console/curses tools
#47For being "obscure", htop manages to find its way into a very large proportion of *NIX screenshots on the web. Not to mention vim, rsync, curl, and ack, all of which I (and I had assumed everyone else) use on a regular basis.
I still don't use ack, mostly because it's not installed everywhere I go on a regular basis and so my fingers still go 'grep' when I think 'text search'. (I also rarely use curl, because my fingers are trained for wget -qO. That one is a personal quirk, though, I didn't know about curl until I'd had that one imprinted on my brain. The cool thing there, though, is that wget -qSO will send headers to stderr and content…
Installation is simple enough assuming you have perl:
curl http://beyondgrep.com/ack-2.12-single-file > ~/bin/ack && chmod 0755 !#:3Re: A collection of Unix terminal/console/curses tools
#48I know lists like this will almost always contain at least one command that I, or any other sys admin on here, would use fairly regularly. But it would be nice if just once an article about "obscure" CLI commands didn't include stuff that's the most basic of essential every day staples for any *nix administrator. Including stuff like vi and emacs is just ridiculous, quite frankly. If you haven't heard of them already…
> Maybe my job this weekend will be to write my own version of these documents but with a decent selection of programs, descriptions and example usages? Maybe your job this weekend should be to get a little exercise before writing on the internet? It's a nice little summary of cool tools. "Some are little-known, some are just too useful to miss, some are pure obscure".
> Maybe your job this weekend should be to get a little exercise before writing on the internet?
Maybe you should learn some manners and stop posting wild assumptions about physique of your peers.
> It's a nice little summary of cool tools. "Some are little-known, some are just too useful to miss, some are pure obscure".
It's barely a summary. A summary requires some details about the points being raised; albeit a briefly phrased. That site was more akin to a bullet-pointed list.
The descriptions are lacklustre, the screenshots are useless for all bar the ncurses programs, and including "just too useful to miss" programs like vi and curl but with zero detail nor examples about how to use them is absolutely worthless. Anyone who's every used a Linux / UNIX command line -even briefly- would already know that vi and curl exists - what they might not know is how to use it. And that's where articles like this should focus if they're wanting to incorporate commonly known commands along with obscure ones. Otherwise you're trying to appeal to everyone yet failing to please anyone.
Re: A collection of Unix terminal/console/curses tools
#49Earlier quoted context omitted.
> Maybe my job this weekend will be to write my own version of these documents but with a decent selection of programs, descriptions and example usages? Maybe your job this weekend should be to get a little exercise before writing on the internet? It's a nice little summary of cool tools. "Some are little-known, some are just too useful to miss, some are pure obscure".
> Maybe your job this weekend should be to get a little exercise before writing on the internet? Maybe you should learn some manners and stop posting wild assumptions about physique of your peers. > It's a nice little summary of cool tools. "Some are little-known, some are just too useful to miss, some are pure obscure". It's barely a summary. A summary requires some details about the points being raised; albeit a br…
Hey man, the guy put together a nice little list of tools, nothing more nothing less.
Re: A collection of Unix terminal/console/curses tools
#50Earlier quoted context omitted.
> Maybe your job this weekend should be to get a little exercise before writing on the internet? Maybe you should learn some manners and stop posting wild assumptions about physique of your peers. > It's a nice little summary of cool tools. "Some are little-known, some are just too useful to miss, some are pure obscure". It's barely a summary. A summary requires some details about the points being raised; albeit a br…
Hey man, the guy put together a nice little list of tools, nothing more nothing less.
> little list of tools, nothing more nothing less.
Which was my point. :P