Skip to content

Allow piping command output to a file (for settings export) #567

@PeridexisErrant

Description

@PeridexisErrant

Piping command output to a file is a fundamental operation, and could be useful in several places.

For example, workflow list-commands and autobutcher list-export (after #566) both print lists of commands - currently to get them in a file it's easier to use dfhack-run command > file.txt in an external terminal, and then import with script file.txt in DFHack. Other benefits would include ease of dumping data in general, and potentially wider adoption of state-dumping options for plugins to enable moving settings to another save.

If security is a concern, valid file names could be restricted to non-existent *.txt files in the DF folder - preserving most common uses, and limiting accidental damage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ideaSuggestions, etc.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions