BashStyle-NG is a graphical tool and function chain that lets you do more with GNU Bash
BashStyle-NG consists of a graphical tool and a functionchain.
The graphical tool (bashstyle) is used to easily change a huge amount options
regarding Bash, Readline, VIm and Nano. The configuration is stored using ConfigOBJ.
The functionchain is used to realize the setup when starting a new Bash.
Besides a diversity of additional functions or wrappers is provided.
Another thing shipped is dirinfo (a simple, in-progress directory-indexing
mechanism for the shell), aswell as a first-run-wizard.
12 different prompt-styles are shipped, all of them can be modified using the
GUIs built-in custom-prompt-builder (CPB).
Every option and every function is described in the documentation.
Screenshots (click for larger size):
License: GNU GPL v3
Overview of changes in v8.3 “Tweeka-Time”
=== Bug fixes ===
- #143 (make): don’t enforce make install/uninstall to be run as root (prevents building rpm packages)
- #144 (docs): don’t auto-install docs like AUTHORS, COPYING etc. let this the package-maintainer do. Only the user-manual will be installed on your system
- #145 (clock-advanced prompt): fix calculating prompt-size when changing user and fix calculating overall prompt-size in monochrome version
- #146 (nx-rc):make “reload” working again (broken since 8.2)
- #147 (wizard): fixed some bugs that prevented upgrading the ini-file for bs-ng-wizard (first update of the file in v8.3)
=== new features ===
- install-extras: simple script to install other (possibly) insteressting stuff for bash (currently: bash-git-prompt)
=== misc changes ===
- nx-rc: don’t pollute environment with useless variables
- installdirs: don’t create no longer used directories upon install
- colorshell: option to return to normal text-color after pressing enter
- bs-ng-wizard: update ini_file to v2 (add color_shell_reset option)
=== configure v4.2.2 ===
- add –no-postinstall configure-flag (for package-maintainers)[no post-installation tasks will be performed, ensure your packaging scripts will do the thing instead]
- add –no-installdocs configure-flag (for package-maintainers) [no documentation will be automatically installed, ensure your packaging scripts will do the thing instead]
- changed configure’s note-message at the end a bit