custom.css, config.edn, etc. do not function when they belong to read-only filesystems #11267
Open
1 of 2 tasks
Labels
:type/enhancement
Enhancement to product. Does not affect the overall basic use.
Search first
What Happened?
When the
custom.css
file (located at/logseqdirectory/graphdirectory/logseq/custom.css
) is a symbolic link to a file in a read-only filesystem, the contents will appear in the in-app 'edit custom.css' page, but will not have any effect. The same seems to be the case with theconfig.edn
file within the same directory.Reproduce the Bug
/logseqdirectory/graphdirectory/logseq/custom.css
1a. In my case this means declaring the
custom.css
file with home-manager.Settings > Edit custom.css
Expected Behavior
custom.css
declared using home-manager, or any otherwise valid.css
file that is linked from a RO directory, should be read and applied properly by logseq.Desktop or Mobile Platform Information
NixOS
24.05
Using nixpkgs unstable, home-manager, and nix-flakes
Logseq version
0.10.8
Additional Context
I have found a workaround for this issue, which involves declaring the
custom.css
andconfig.edn
in a nearby directory, then setting home-manager'shome.file."filename".onChange
setting to a script that copies the file from the directory it's created in to the/logseq
directory of my graph.Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: