The sound distributed version control system

#315 Make some pijul commands give feedback to the user

Opened by coconut on February 12, 2021 Feature request UI
coconut on February 12, 2021

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 think pijul 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.

pmeunier added tag Feature request on August 4, 2021
pmeunier added tag UI on August 4, 2021
joyously on August 21, 2021

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.

fogti on August 24, 2021

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.