mcli should respect XDG basedirs for storing its configuration

[ddevault]

Is your feature request related to a problem? Please describe.

mcli should not store its configuration in the ~/.* namespace on Unix systems.

Describe the solution you'd like

mcli should respect the XDG basedirs spec, using $XDG_CONFIG_HOME/mcli if set, and falling back to ~/.config/mcli if not. It can read ~/.mcli as a last resort to avoid breaking the config for users who have already set it up, but it should not create new files there by default anymore.

[harshavardhana]

This is something we can take a look but we would want to keep previous functionality so it may be good idea to have fallbacks for Linux.

[klauspost]

This will require moving the config to not break existing installs on update.

[vadmeste]

This will require moving the config to not break existing installs on update.

Maybe we can do as a fallback better. I mean the last check will be ~/.mc/

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

[ddevault]

Don't run bots like that, jeesh

[renich]

phew... I'm also waiting for this one.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

[ddevault]

Don't run bots like that, jeesh

[vadmeste]

I sent a PR for this. But I am not sure if we are going to merge it.

Don't run bots like that, jeesh

We receive a lot of issues and we cannot process all of them. It makes sense that a bot helps us here :)

[ddevault]

Those bots are an anti-feature which communicates a lack of investment from maintainers in their community. You should triage issues and close them when you know they're not a good idea, and otherwise leave them open. Having a lot of open issues is not a mark of shame.

[harshavardhana]

Those bots are an anti-feature which communicates a lack of investment from maintainers in their community. You should triage issues and close them when you know they're not a good idea, and otherwise leave them open. Having a lot of open issues is not a mark of shame.

How we manage the issues is our internal requirement, bots will run as per our requirement.