-
Notifications
You must be signed in to change notification settings - Fork 130
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
path name with colon causes problems with gsettings and GSETTINGS_SCHEMA_DIR #322
Comments
Right, that's a good point, the directory won't work in at least As an aside you can set things without a schema too (at least with Will have a think about changing the id, and how a smooth upgrade can be handled. |
glib changed, and it only works with older versions |
Right, never noticed as I've only really used dconf-editor together with |
this popped up again in #376 (comment) the best would be to just ‘get with the program’ 😉 and use the same naming conventions as pretty much all other gnome extensions. without a colon, that is. |
Yeah will just have to bite bullet here, propably do it for the 40 release |
To avoid future (potential) issues with this - yeah, I think we should change the id/name to Will create a PR for this. |
Closing as uuid has been changed to safer |
this extension uses a
:
(colon) character in its directory name in~/.local/gnome-shell/extensions
, namelypaperwm@hedning:matrix.org
, which causes problems when usingGSETTINGS_SCHEMA_DIR=...
and thegsettings
command line tool. the:
is interpreted as a path separator.this means
gsettings
cannot be used to configure this extension, as suggested in the readme.since this is only the extension (out of quite a few on my system) using a non-standard character, i suggest to adhere to the established practices and conventions for gnome extensions, and use an identifier and directory name that do not cause problems.
The text was updated successfully, but these errors were encountered: