Add support for configuration file#39
Merged
BRO3886 merged 1 commit intoBRO3886:feat/default-tasklist-configfrom Mar 10, 2026
Merged
Add support for configuration file#39BRO3886 merged 1 commit intoBRO3886:feat/default-tasklist-configfrom
BRO3886 merged 1 commit intoBRO3886:feat/default-tasklist-configfrom
Conversation
gtasks now reads in configuration from config.toml in its configuration directory. Currently the client ID, secret, and default task list can be specified. It now also follows the XDG desktop standard for the location of its configuration directory. This also addresses, in part, issue BRO3886#36.
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gtasks now reads in configuration from config.toml in its configuration directory. Currently the client ID, secret, and default task list can be specified.
It now also follows the XDG desktop standard for the location of its configuration directory.
This also addresses, in part, issue #36.