[Enhancement] verbosity with --progess #108
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#108
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
i realy like, that #64 is fixed.
but i still miss the feature having another verbosity level with
borg create --progress
in my opinion it should be added to verbosity-level one.
What do you think of the idea proposed on #106? Basically:
If that works, then I could close this ticket in favor of #106 and implement the progress bar there.
seems a bit like it.
i thought the #106 is especially about a progress bar.
--progess
is not displaying a bar, but the current status.but your solution (passing the parameter) seems fine to fix this issue.
Oh gotcha. I didn't realize
--progress
wasn't an actual progress bar.. I guess I was assuming it would work likersync --progress
, which isn't a valid assumption.I'll play around with the flag and figure out if it makes more sense included at borgmatic verbosity level one (as you originally suggested), or as a separate flag.
So I played with the flag a bit. My main concern with including it by default (at, say, verbosity level one) is that the updating display may not play nicely with or be overly verbose in a non-interactive display. For instance, if you're redirecting verbose borgmatic output to logs or using it in a cronjob, then
--progress
could make that log output less useful.If you buy that, then that leaves the command-line
--progress
pass-through flag. I also considered a borgmatic configuration option instead, but whether you want to see progress seems more like a temporary display concern (like verbosity is) rather than something you'd want hard-coded in a config file.Let me know what you think.
Valid argument.
Having a seperate (pass-through) parameter would be perfect.
Released in borgmatic 1.2.11. Enjoy!