You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
.The text was updated successfully, but these errors were encountered: