Overview of changes:
* Added extra shorthand arguments for common usage errors
Things like missing positional arguments or unknown arguments need
to be dealt with so often it warrants these shorthands.
* Fortified command, file and pipe delimiters
Often it's helpful to see more clearly where output begins and where
it ends. Note that this is a small step from pretty.sh's total
minimalism, on the other hand these file and command printers are
not exactly minimalistic already; they are not intended for normal
use but rather for debugging.
Overview of changes:
* Fixed coerce__noctl() to actually do something
Turns out that the function could not ever work properly since
Perl's tr/// operator does not support POSIX character classes like
traditional tr(1) does. The expression was replaced with s///
variant, preserving the same character range.
Also it will now *replace* characters $COERCE__REPCHAR, instead of
removing them. (Removing behavior can be achieved by setting the
variable to empty string.)
Overview of changes:
* Enabled shellfu-sh-coerce to avoid Term::ANSIColor dependency on RHEL-6
Turns out this module is not easily available on RHEL-6, so by adding
the dependency in recent version, we broke shellfu-sh-coerce and its
reverse dependencies there.
debian/control does not allow creating dependency lists by repeating
Depends: field, like RPM .spec files do. I did not realize it when
adding coerce.sh
Overview of changes:
* Added module coerce.sh for character set coercion
* sfdoc will jump to first object mention in object mode (`-O`)
* Minor fixes and cleanups
Overview of changes:
* Improved an updated tab completion for sfdoc
The tab completion now offers more recent argument and most
importantly, module and/or object names.
* Fixed global variable '$modname' leaking from shellfu()
* Fixed --which treated as if no value was needed
* Mitigated risk of grep ambiguities
* Smaller cleanups and updates
Where regular expression is read from a variable and -e argument is not
provided, the resulting call may end up being interpreted as grep
argument, This can be pretty dangerous, eg. if the variable expands to
`--help`, grep help is shown and grep exits with zero, which would be
interprered as match. Another example is when the variable expands to
a valid grep parameter; this would mean that next argument would be
interprered by grep as the regex, and if the argument after that would
be missing, grep would read stdin, resulting in data messup or grep
waiting
indefinitely.
See also:
https://github.com/koalaman/shellcheck/issues/1342
It's been followed for years in number of projects (granted, all being
exclusively written by author of this style), so calling it "draft"
seems just weasely.
Overview of changes:
* Added SFPI functions to find and dereference plugin variables
* Renamed SFPI name-access functions to be less confusing
* Fixed broken sfpi__import()
* Finished style guide on naming, capitalization and namespacing
* Minor fixes and cleanups
You can't "get function" or "get module" with these functions; just
their *names*. Also "get" is inconsistent with eg. sfpi__ls() and
sfpi__key(): the "getting" part is implied.
Overview of changes:
* Switched to in-line `do`/`then` style
Many projects actually use it already.
* Updated docs and meta-data after moving from GitHub to pagure.io
* Updated docs after mofing COPR repos
* Added VCS Browser URL to specfile
* Codebase maintenance and cleanups