[Request] Add defaults to MPF.CLI #844

Closed
opened 2026-01-29 16:23:14 +00:00 by claunia · 1 comment
Owner

Originally created by @Whovian9369 on GitHub (Jun 17, 2025).

Originally assigned to: @mnadareski on GitHub.

Is your feature request related to a problem? Please describe.
Add (user settable?) defaults to MPF.CLI.

Describe the solution you'd like
It would be nice for the interactive CLI mode to have (possibly user selectable) defaults.

Describe alternatives you've considered
Manual selection every time, which can get confusing or annoying when doing multiple dumps in a row.

Additional context
This would especially be useful around default systems, device path, mounted path, file path, and custom parameters that are unlikely to change often.
Possibly as an additional request, it would be convenient to have a separate option around the "base directory" (Like how ISO/ is used with MPF.UI) and/or options like Output Directory or Volume Label.

Originally created by @Whovian9369 on GitHub (Jun 17, 2025). Originally assigned to: @mnadareski on GitHub. **Is your feature request related to a problem? Please describe.** Add (user settable?) defaults to MPF.CLI. **Describe the solution you'd like** It would be nice for the interactive CLI mode to have (possibly user selectable) defaults. **Describe alternatives you've considered** Manual selection every time, which can get confusing or annoying when doing multiple dumps in a row. **Additional context** This would especially be useful around default systems, device path, mounted path, file path, and custom parameters that are unlikely to change often. Possibly as an additional request, it would be convenient to have a separate option around the "base directory" (Like how `ISO/` is used with MPF.UI) and/or options like `Output Directory` or `Volume Label`.
claunia added the enhancement label 2026-01-29 16:23:14 +00:00
Author
Owner

@mnadareski commented on GitHub (Jun 18, 2025):

Within reason, a default file path and a default system can be set trivially from the provided configuration. The fact that they weren't being set before is a miss on the original implementation.

CLI doesn't attempt to find all possible drives and relies on the user to input them. There's also not an easy way of having it be user-configured without it being another full setting. This extends to the mounted filesystem path as well. This also, unfortunately, extends to a default filename from the volume label. A placeholder value can be provided, though.

Custom parameters should probably not be reused between runs, especially since all parameters need to be input. If that's needed frequently, then interactive mode probably shouldn't be used.

@mnadareski commented on GitHub (Jun 18, 2025): Within reason, a default file path and a default system can be set trivially from the provided configuration. The fact that they weren't being set before is a miss on the original implementation. CLI doesn't attempt to find all possible drives and relies on the user to input them. There's also not an easy way of having it be user-configured without it being another full setting. This extends to the mounted filesystem path as well. This also, unfortunately, extends to a default filename from the volume label. A placeholder value can be provided, though. Custom parameters should probably not be reused between runs, especially since all parameters need to be input. If that's needed frequently, then interactive mode probably shouldn't be used.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/MPF#844