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
A configuration file can be generated by right clicking the workspacer system tray icon, and selecting the option to create an example configuration in:
I followed the instructions but there was no workspacer folder inside my C:\Users\Henrik\.config\. I found the workspacer.config.csx in a different place.
I think, I got cought in the same bug as you. What I found out, is that when I put my config files into C:\Users\<username>\.config\workspacer, Workspacer does not detects / applies the configuration. It only applies the configuration if I put it into C:\Users\<username>\.workspacer . Also when I run the create example configuration option, workspacer creates C:\Users\<username>\.workspacer folder and then puts there the example configuration.
So we can conclude that Workspacer, in actuality does not look at the C:\Users\<username>\.config\workspacer directory for configuration, and this is the nature of the bug. It could be a feature if the documentation were rectified.
Considering, the Unix-style dot file placement, it would not much of a stretch to implement XDG Base directory specification compliance as much as possible on windows. The author of the documentation already shows an intent to that, since, (s)he denoted C:\Users\<username>\.config\workspacer as a possible location for config files, and the default value of $ENV:XDG_CONFIG_HOME is C:\Users\<username>\.config .
In the quickstart page it says the following:
I followed the instructions but there was no
workspacer
folder inside myC:\Users\Henrik\.config\
. I found theworkspacer.config.csx
in a different place.This location:
C:\Users\Henrik\.workspacer\workspacer.config.csx
It took quite some time for me to figure this out. Do you want me to update the docs with the correct information?
The text was updated successfully, but these errors were encountered: