Closed Aodhagan closed 2 years ago
this might be a vscodium issue vs a dendron issue. we provide some sample snippets but otherwise don't change the snippet logic of vscodium
As an update, this same problem occurs for me in both VSCode and VSCodium. When I use the command pallette to open up a folder that is defined as a dendron workspace I get the "Dendron is active" popup in VSCode/VSCodium. However snippets dont work although other aspects of the Dendron do work e.g., dendron look up etc.
If I then open up the command pallette and execute "Dendron Change Workspace" and then select the same Dendron workspace folder, Dendron is re-initialised and the snippets work. This occurs for me in both VSCode and VSCodium and is unrelated to whether the workspace folder is in an encrypted hard drive are not (apologies but my initial incomplete testing suggested that it was).
can you do the following?
>insert snippet
and make sure your snippet is still there>toggle keyboard shortcuts troubleshooting
and tell me what you see when you try to autocomplete a code snippetApologies, haven't replied up to now as I cannot replicate the issue for the past couple of days. When the above problem occurred it was as if the Dendron Snippets did not exist (despite Dendron being active). There was no error reported in the toggle keyboard shortcuts troubleshooting
either. Perhaps I will close this issue and I will open another one if the problem re-occurs.
Apologies for the inconvenience and thank you for the great software! I'm really enjoying using it and is my first attempt at PKM it feels like a real game changer. Thanks again!
Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)
Describe the bug
Dendron snippets do not work when the Dendron workspace is on an encrypted hard drive
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Snippets should work
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)
Additional context
Add any other context about the problem here.
Dendron Log file
Please attach the output of
> Dendron:Dev: Open Logs
here