The sound distributed version control system

#831 `record --all` should be Broken into Recording all Files and Recording without a Prompt in the Text Editor

Opened by stellarpower on October 28, 2023
stellarpower on October 28, 2023

The --all flag for recording does two things at the same time:

  • It includes all files that have changed, and
  • It does not prompt me for editing the change in my text editor - and so is suitable for binary files.

What happens when I want to record a specific path, already know my message, and am working from a script - so do not want to bring up my text editor to edit the change?

pijul record --all /some/path/spec records all files, and ignores the argument. As the documentation does say, this isn’t a bug per se, but I believe those two features should be separate flags.

E.g. pijul record --confirm --message "..." [ /some/paths/here] to confirm that what you said is what you meant, and to record the changes from the given files without opening EDITOR.

Then I presume without confirming, all would behave the same as if we gave pijul no arguments, so pijul record --all could then function as if applying the confirm flag and not limiting the recording to specific files.

There may be a few different ways to plumb this, with some candidates better than others - but I feel like the act of not needing to open the editor is a useful flag on its own and it’s better for each switch to do one thing, with those that do several acting as a combination for convenience.