Multiple configs #2

New Issue

jesse · 2024-04-22T19:56:43Z

jesse commented

2024-04-22 19:56:43 +00:00

Different config options work well with different templates and situations. Rather than having one config that works for a single common use, it would be better to allow multiple configs that can be easily switched. For instance:

qq2clone config new <name>    # Make new config table with <name> and default values
qq2clone config load <name>   # Load config <name>
qq2clone config show          # List all config tables, with a * by the loaded one
qq2clone config show <name>   # List config table with <name>
qq2clone config edit args...  # Change values in current loaded config table
qq2clone config delete <name> # Delete config table of given name (never default)

Different config options work well with different templates and situations. Rather than having one config that works for a single common use, it would be better to allow multiple configs that can be easily switched. For instance: ``` qq2clone config new <name> # Make new config table with <name> and default values qq2clone config load <name> # Load config <name> qq2clone config show # List all config tables, with a * by the loaded one qq2clone config show <name> # List config table with <name> qq2clone config edit args... # Change values in current loaded config table qq2clone config delete <name> # Delete config table of given name (never default) ```

jesse referenced this issue

2024-04-22 19:58:41 +00:00

complete: list xml #7

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jesse/qq2clone#2