Skip to content

Configuration file discuss #61

@lowusage

Description

@lowusage

I've seen a few issues here, and a few people talking about some features that could be achieved through the use of a global and/or personal configuration file.

If such a thing is going to be implemented, it should be discussed which format of file should be used, and what kind of things should be taken from that (should we configure the Editor for example, or let it be the EDITOR environment variable ?).

In my sense, Iris should be homogeneous in the file formats it uses : if we use JSON for the message storage, we have to use JSON for configuration. This can of course be discussed, ML languages such as YAML(s) and XML for example are also good ones that are used a lot.

In the short-term I will not have the time to work on this, but I'll very happy to contribute to the project in some weeks! This issue is mainly an attempt to launch myself in, and to discuss how things should be done.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions