They missed out ls and cd.
A collection of Unix terminal/console/curses tools
31–40 of 50 posts
Re: A collection of Unix terminal/console/curses tools
#32I'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
sed can edit in place though.
Re: A collection of Unix terminal/console/curses tools
#33I 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…
Yes
Re: A collection of Unix terminal/console/curses tools
#34> nethack & slash'em > Still the most complex game on the planet. Does anybody know if a HTML5 version of Nethack exists?
Very likely, but potentially even better is this WebTiles version of Dungeon Crawl Stone Soup: http://crawl.akrasiac.org:8080/#lobby
I think you might be underestimating the complexity of nethack
Re: A collection of Unix terminal/console/curses tools
#35I 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 it.
Interactive programs should also possible- think of a schematic editor or a figure editor running right on your terminal emulator.
The point of all this is to retain the context of whatever you're doing without having to switch windows. That and to advance the state of the art of console tools- certainly they have not changed in decades.
Re: A collection of Unix terminal/console/curses tools
#36I 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…
On the topic of ways to improve the terminal, I'd like to see output separated from input.
Put the prompt 1/4 of the way down the screen instead of at the bottom. Above the prompt, we have a backlog of the commands we input. As we press up, it scrolls through the backlog, as normal.
Below the prompt, we see the output of the command.
I'd also like to see tab completion (and maybe some form of hinting) on programs, not just file paths.
Re: A collection of Unix terminal/console/curses tools
#37I 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…
On the topic of ways to improve the terminal, I'd like to see output separated from input. Put the prompt 1/4 of the way down the screen instead of at the bottom. Above the prompt, we have a backlog of the commands we input. As we press up, it scrolls through the backlog, as normal. Below the prompt, we see the output of the command. I'd also like to see tab completion (and maybe some form of hinting) on programs, no…
>On the topic of ways to improve the terminal, I'd like to see output separated from input.
>Put the prompt 1/4 of the way down the screen instead of at the bottom. Above the prompt, we have a backlog of the commands we input. As we press up, it scrolls through the backlog, as normal.
>Below the prompt, we see the output of the command.
That would be more fitting for a shell than for a terminal.
>I'd also like to see tab completion (and maybe some form of hinting) on programs, not just file paths.
bash already does this. zsh and at least one variant of ksh will do completion if you type the first letter of a command. I was surprised that tcsh doesn't.
Re: A collection of Unix terminal/console/curses tools
#38My latest discovery: jq - command line json processing, formatting and colouring.
Re: A collection of Unix terminal/console/curses tools
#39I'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
How is sponge different from > filename?
It can be used where ">" does not work, e.g. when using sudo. So you can do
echo data | sudo sponge /etc/a.file
Re: A collection of Unix terminal/console/curses tools
#40I'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
sed can edit in place though.
indeed!
sed -i -e 's/root/toor/' -e '/joey/d' /etc/passwd