i think the proper way would be to use the

--extensions-dir=/path/to/code-dendron-ext

flag when launching

caveat is that the latest version of markdown-notes and markdown-preview need to be in that dir

could probably setup some symlinks during the setup script

That would mean all other personal extensions would be left out, correct?

I'm going to go play some music and unwind, but will reflect. ❤️

yep. sounds good. i’m going to go for a run 🏃‍♂️ in the meanwhile 🙂

Hmm, looking at the current state of Emmet vis a vis Markdown, (Both in VSCode and elsewhere), I see that Emmet remains a tool mostly focused on web stuff, and has not been extended to directly support Markdown, or more general languages, e.g. Python. There is no reason why it can't, so I would like to put in a feature request for it. According to the VSCode extension guide, the place to do this is in the lsp for the language you want to add emmet support to. as we have(/going to have)? such a server for Dendron use that to add emmet-expansions for Markdown.

@User can you submit a feature request so we can track it in our roadmap? https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title= for non-markdown related markup, my thinking is that dendron should be able to support them. that being said, i don't have the bandwidth to work on it but am happy to show others how it can be done if they want to 🙂

i don't know if anyone else has this issue but when i'm working in vscode, i often try to use

cmd+l

to navigate code and can't understand why it results in a line highlight 😅

I almost messaged you about that last week! I guess we should remap

cmd-l

to

cmd-p

when not in dendron. 😂

Or extend lookup. 🙂

That’s why I wrote that toy

britt-picker

extension, to add

Create file

as an option to

cmd-p

.

nice! will there be a

britt-picker 2.0

?

First I’d like to at least push the code. I broke it and haven’t had time to step back and fix.

I saw this before I wrote it, which is a better version: https://marketplace.visualstudio.com/items?itemName=jit-y.vscode-advanced-open-file

there's also file utils which is what i use https://marketplace.visualstudio.com/items?itemName=sleistner.vscode-fileutils

last post of the day. night all 😴

@kevins8 have you ever done any work in jupyter notebooks?

@kevins8 Gnight!

Ok, goodnight talk to ya later

@SeeDubLan I have, but I’m headed to wind down and sleep as well. Chat tomorrow?

@SeeDubLan yes. will answer more tomorrow if you leave some context in the chat

Sure, sounds good, rest well

@User Big problem with the latest update. Clicking on a note in the sidebar tree causes the note to be replaced by a blanc note, with no warning. There is loss of data unless you have backup.

@User Trying to recreate this. Just upgraded to 0.13.4. Opened files via the tree view as well as the regular file list and it's not replacing it with blank notes for me (thankfully).

Try reopening vscode and clicking on the tree view. Its happening for me in both VSC and Codium

I did that and it still opened my notes without deleting them...Except for one, I just discovered: I have a note titled 000 Index in the root of my vault, and if I click that one in the tree view it is replacing it with a blank note each time.

But all my other notes are fine/being opened, not replaced.

Yes. that's whats happening to my notes

Its changing the IDs every tim ei click