I was about to open this same discussion, but found it here already.
Other commands that need output: add
, key
, list
, log
, git
, fork
.
pijul add .
shows nothing. It ignores the dot and nothing is added. If you use pijul add *
then it adds everything, but doesn’t say anything different.
pijul add .
adds nothing. This should be an error instead. The alternative which probably does what the user wants is pijul add -r .
, which adds everything under the current directory recursively.
Hello. There are many cases in which
pijul
subcommands return nothing. I would rather prefer if it returned something. I tried to look for a--verbose
flag, but to no avail.Examples:
$ pijul init
Currently does not return anything.
git
at least returns “Initialized empty Git repository in /tmp/foo/.git/”. I thinkpijul
should return something, too.$ pijul change
Currently returns nothing at all and I have no idea why. I created a file, still returned nothing, I
pijul add
’d the file, still nothing. It should really print something as to what is going on.There are probably a couple of more such commands. I think
pijul
should return some output in all cases to give the user a clue about what is going on, why cannot it do something, or if it did something, and so forth.