Thank you for checking it! I added the override, but it is still not working...

Ctrl + L

doesn't do anything

Ctrl+Shift+P

->

Dendron: Lookup

-> Shows me a window with the current note

Ctrl+Shift+S

allows me to create a new scratchnote

oh, if your on windows, replace

cmd+l

with

ctrl+l

It's still not working...

Any suggestions based on this ?

the

extension.vim

line, right click and select remove keybinding

Thank you! Works now!

Is is recommended to use dendron alongside vim ?

yes! the keybinding is the outstanding compatibility issue at the moment

Awesome! I just installed vscodium, so that none of my existing extensions/cofigurations effect dendron :) And now things look to be working well :)

This is beautiful! Thank you for creating this !!

Yep deleting cache fixed it, thanks!

Hi Folks - Sorry if this is an obvious question - I am under the gun in terms of time -- is there a repository within Dendron or the community writ large of schemas? I am looking specifically for Project related schemas as BASB / PARA thinks of them. But anything related would be a start

Is it possible to append date to notes - Something similar to journal notes ? But, for example if there is a weekly meeting for a project eg.

titan

can we create notes with

titan.meet.2021.06.21

and next time create

titan.meet.2021.06.28

but append the date to the note name automatically ? (Similar to journal notes )

That makes sense. Thank you for pointing me to that setting. I will point out though that the default behavior is that after a new vault is initialized, the root.md file contains # Welcome to Dendron, which immediately causes the Markdown Lint to grumble. So the user experience is that, "I installed this shiny new note taking tool.. and what do we have here? I haven't touched anything, but am already seeing warnings?!" So maybe fix root.md to contain ## Welcome to Dendron ?

I have configured font family for Markdown preview for the vault (

settings.json

) as :

{
  "markdown.preview.fontFamily": "'FiraCode NF', -apple-system, BlinkMacSystemFont, 'Segoe WPC', 'Segoe UI', system-ui, 'Ubuntu', 'Droid Sans', sans-serif"
}

Even though

FiraCode NF

is installed in my system and also can be set as editor font and reflects the change. But setting it in the markdown enhanced preview setting is not reflecting the change. Any suggestions on debugging this issue ? Specifically, I am completely unable to use any ligatures.

I believe to change the font family for Markdown Preview Enhanced you need to modify the css of MPE. The setting you have there is for Markdown Preview that comes with vscode.

Try the

Markdown Preview Enhanced: Customize CSS

command from the command palette 🙂

Okay, I'll try to customize css :)

But, the setting was under

vault

so I though dendron would support changing it.

I am getting another wierd issue with linking of scratch notes - When I try to navigate to a linked scratch note (Created by highlighting and using

Ctrl+Shift+S

) I get the following error - I am using windows and vscodium.

Has this been resolved? Not working here either.

Hello, I'm getting the below error, can enyone help me troubleshoot it? I've tried wiping all schema files and reloading the index, but it didn't help. I have inspected the log file and the only suspicious line is the one showing the error, which I've pasted below. https://pastebin.com/PMNw7qmg

Hey, It seems like a file in your vault may be invalid you could try to run

Dendron: Doctor

in the hopes that it is a frontmatter issue, other wise I Currently have no idea. https://wiki.dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f47.html#doctor

This is a parsing problem (the

>

in the wikilink is causing it). I'll make sure this gets fixed as soon as possible. In the meantime, if you go to the line where that wikilink is and remove the bracket, it should stop causing this problem. Sorry about that.

Thank you gentlemen for the help 🙂 The Doctor command throws out an "error running command: Cannot set property 'pause' of undefined", not sure if that is normal or relevant. @User that was my thought at first, so I madly deleted the whole contents of the "dendron.topic.commands.md" file, then the file itself, but the error still shows.

The culprit is in

dendron.topic.lookup.schemas

. You also might want to pull from remote again. Looks like this has been fixed a while ago.

How long has it been since you've set up the vault?