shell dot on steroids https://pagure.io/shellfu
Alois Mahdal c95b5fbf75 Bump version преди 9 години
bin Avoid confusion with -I from ffoom and ffdoc преди 9 години
doc Update docs after CLI change преди 9 години
include Explain variables in cfgrep преди 9 години
mkit Add FIXME note about shallow clones преди 9 години
notes Add style guide (draft) преди 9 години
test Remove unnecessary pipe преди 9 години
.gitignore Do not track test artifacts преди 9 години
LICENSE Split-fork from qecc преди 9 години
Makefile Split setup/mk.sh to create mkit преди 9 години
README Add note on name conflict when using -v from __echo frontends преди 9 години
config.mk Bump version преди 9 години
ffoo.sh.skel Use the _expand internal backend преди 9 години

README

Fast Foo Bash library
=====================

ffoo - Fast Foo - a Bash Library


NOTES
-----

* if when using `debug -v` you stumble on a variable name
that is *really* used internally by pretty.sh, routines
pick up the internal ones which may easily confuse you.
Examples are `src` or `caller`.

You can circumvent this by composing the debug string
yourself, e.g.:

debug "src='$src'"

in place of

debug -v src

This will be solved in the future (1.0.0?) probably by
refactoring the internal names to some long, ugly but
"safe" names. Now, however, readability of the internal
code is of higher priority.

Note that there is no risk damage to data integrity, it's
just that the routine is unable to show you desired value.


* if `debug -v "x*:` is used, `x*` apparently tries to match
*filenames* first, and only if there is no match, it goes
on to match variable names. This does not seem to affect
`@`, though.

Probably some eval pitfall. For now I'll just remove `*`.
If somebody can fix it, we can re-add it.

On the other hand, I don't even understand how `*` should
exactly behave compared to `@`, so having it disabled does
not seem like such a loss. And by the way, did you know
that the eval is evil? So in the end, maybe we should not
have this feature in the first place... :)