Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Custom configuration file path #4327

Closed
dallaslu opened this issue Aug 2, 2021 · 3 comments · Fixed by #9048
Closed

[Feature Request] Custom configuration file path #4327

dallaslu opened this issue Aug 2, 2021 · 3 comments · Fixed by #9048

Comments

@dallaslu
Copy link

dallaslu commented Aug 2, 2021

The default path is tabby/config.yaml, there are many other files in the same folder. This makes it difficult to sync using a web drive client such as Dropbox, Nextcloud.

Once you can customize the path, it's easy to switch configurations (may be useful in some very specific cases).

At the very least, key text files such as config.yaml can be moved to a folder. For Example: tabby/con/config.yaml.

@clarkwang
Copy link
Contributor

What about adding something like an includes option? Then it'll also be easier to share the conf between Mac/Windows/Linux.

includes:
  - /my/tabby/common.yaml
  - /my/tabby/win10.yaml

@dallaslu
Copy link
Author

dallaslu commented Aug 3, 2021

What about the changes made in the tabby settings screen, are they saved to config.yaml or the include file?

@clarkwang
Copy link
Contributor

clarkwang commented Aug 3, 2021

What about the changes made in the tabby settings screen, are they saved to config.yaml or the include file?

  • The files in includes list have lower to higher precedence (so win10.yaml would override common.yaml).
  • Options in tabby/config.yaml would override includes files.
  • New updated settings would only be saved to tabby/config.yaml. Users need to manually copy the options from tabby/config.yaml to includes files if they like.
  • includes files cannot include other files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants