Termi is a framework to customize your most used command-line tools
NOTICE!! This project is in its prototype phase! Running
termi-confortermi-serveron public networks might have security issues!
The first version of GNU coreutils was announced in September 2002 by merging the earlier packages textutils, shellutils, and fileutils, along with some other miscellaneous utilities 1. Since then, many more handy-but-sometimes-obscure options have been added to each command. However, for backward compatibility, few options are deprecated, making the whole available options unorganized and conflicted. Moreover, most of command-line users don't memorize these options (how many time do you read the man page of ls? ), leaving the outputs sometimes unsatisfactory and resulting in more and more questions about shell asked on StackOverflow2. Termi, starting as a final project and still on its prototype phase though, attempts to resolve the issue.
Termi focus on an easy way to customize outputs of most used command-line tools. Because of its two-phase customization, you can almost do anything to beautify the outputs, like formatted with colors, trimmed to fit in one page, sorted by some columns, and many more. Below is a quick explanation about the two-phase customization.
There are two applications in Termi called termi-conf and termi-server. termi-conf is used to configure the aliases and generate customization scripts, while termi-server listen on socket to transform outputs of commands on demand. So, if you only use Termi to create some handy aliases, you don't have to install termi-server.
We measure performance by using time command. To be done.
- The supported options are based on the newest version of
coreutilspackage on Arch Linux. There should be a way to support multiple versions of commands. - Unit testing.
- Measure performance.
MIT
Footnotes
-
Wikipedia GNU Core Utilities ↩
-
tag-trends about shell ↩