Open lnicola opened 2 years ago
For Dendron taking a long time to start on a non-dendron workspace, will take a followup to look into that. Our work Q for next week is already full so this will be the following week.
For Show Preview
, we can add a context clause to have it be available when working inside a Dendron workspace. Mind splitting that off in a separate feature request?
Filed #1545.
Don't worry about taking longer to solve it. It's open-source (and free) software. If it gets fixed in the next six months or so, I'm happy :-).
This should be fixed in v69. Can you let us know if this is still an issue?
Maybe I'm missing something, but it still gets activated in a non-Dendron directory.
ah - you're right. i was mixing this up with the preview issue. will keep this open
Please select the area your Bug applys to.
Describe the bug
The Code extension slows down the editor startup.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The other annoying thing is that Dendron brings two "Show Preview" commands that conflict with other commands in popular extensions. Sometimes I'm editing AsciiDoc or another Markdown file, and I run the Dendron command by mistake.
Screenshots
Here it took 256 ms on a reasonably fast computer:
Desktop (please complete the following information)
Additional context
Since Dendron is already split between multiple extensions, my suggestion is to split the workspace initialization into another extension. This way, "Initialize workspace" would always be available, but the main extension could have an
"workspaceContains:dendron.yml"
activation event instead of"*"
.Dendron Log file
N/A