Closed apaz-cli closed 3 years ago
The path in vscode_custom_css.imports
does not need to be contained inside vscode_custom_css.staging_dir
. Actually, the extension will delete the staging dir before applying patches, so you should put the CSS file somewhere else, and use vscode_custom_css.imports
to reference them: they will be copied to the staging dir.
However for the pictures, VSCode's current policy will block loading it, so you may need to place it into some HTTP-accessible place.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days.
I created the directory and the file. When it can't find vscode_style.css the extension yells at me, so I figure that it finding the file must not be the issue. I've also chowned /usr/share/code and all of .vscode, so permissions shouldn't be an issue. Everything seems to go right, but the css is not applied. The extension host log prints no relevant messages either.
It likely doesn't matter, but here's the content of that css file.
With my old configuration broken, and now the new one broken, I'm not quite sure how to use the extension correctly anymore. Perhaps the readme could be updated. There's some outdated information on it.