Appreciate the video and explanation @kevins8. This seems like a perfect way to keep on top of things and can easily revert to past journals quickly.

Hello everyone! I have a question regarding graph. As far i understood, with command

Dendron: show note graph

it shows tree-style view of notes, right? There is the highest node ("root") and so on. Is it possible to make the graph show connections between notes, that were connected by

[[mention]]

?

Is there a guide around for publishing a single note?

Hmm. Has anyone else managed to get an error 🛑 in

ReloadIndex.execute

with the status

no_root_schema_found

when enabling the experimental LSP? 🤔 It breaks even with a default

root.schema.yml

, so I wonder if the issue is elsewhere.

> Hmm. Has anyone else managed to get an error 🛑 in

ReloadIndex.execute

with the status

no_root_schema_found

when enabling the experimental LSP? 🤔 It breaks even with a default

root.schema.yml

, so I wonder if the issue is elsewhere. @User I'm using the LSP since it was made available without ever encountering this error.

Almost on every start of vscode I get this error message:

The extension 'Dendron Markdown Preview Enhanced' took a very long time to complete its last operation and it has prevented other extensions from running.

Any ideas what to do here? I'm on Windows if that matters,

Yeah I get this frequently as well

@thor you’re seeing this because dendron lsp is looking for a default root schema. this was not a hard requirement pre-lsp and you were able to delete the root schema without any warnings. with 0.13.2, dendron lsp will now regenerate that file if it’s missing so you should not see that error anymore

@Bassmann @imalightbulb do you guys see this when upgrading markdown preview or with regular use? is the preview pane already open when that error comes up? there’s a few easy optimizations that we can make to reduce the startup time if it’s an issue (vscode gives that error when an extension takes longer than 500ms to start)

> > Hello everyone! I have a question regarding graph. As far i understood, with command

Dendron: show note graph

it shows tree-style view of notes, right? There is the highest node ("root") and so on. Is it possible to make the graph show connections between notes, that were connected by

[[mention]]

? > @User currently not with the dendron extension. you can use the

markdown links

(the extension that we forked off) to get connections. note that this extension doesn't work with aliased links. we'll be adding link based graphs as well sometime in november

Hi folks, I hope all is well. (Only slightly off topic!) Does vscode support third party url schemes? if I put [devon](x-devonthink-item://47C14D8A-D6D2-408E-9EC3-4B874F215299) in a markdown file, then enhanced preview generates a clickable link but clicking on the link gives an error which suggests that vscode is trying to open a local file with a name of x-devonthink-item://47C14D8A-D6D2-408E-9EC3-4B874F215299)

@User run

Dendron: Publish Pod

within any note. currently you can publish a note to either json or regular markdown

@User right, that would make sense, but... I have a root schema. I've never not had one, assuming we're talking about

root.schema.yml

.

I'll take a closer look; I think it's a combination of a red herring error message and an error in one of the other schema files that cause it, as moving all of those out while retaining the root schema works. Process of elimination, here we go.

yes. dendron also expects version 1 format 😅 @User

version: 1
imports: []
schemas:
  - id: root
    children: []
    title: root
    parent: root

They're all updated to

version: 1

(in terms of specifying the

schemas

key primarily), but I hadn't specified

imports

to an empty list. Is that a requirement, as well as the empty list for

children

? 🙂

shouldn't be. if it is let me know cause that's a bug 😅

Ah, it seems to fail due to the following schema in

areas.${workplace}.schema.yml

yml
version: 1
imports:
  - journal
schemas:
  - id: daily
    children:
      - journal.journal.daily

Is that an unsupported configuration when

${workplace}

is a namespace? (I thought perhaps it'd get confused who its parent is, but that should be clear from the name of the schema file as far as I understand.)

> @Bassmann @imalightbulb do you guys see this when upgrading markdown preview or with regular use? is the preview pane already open when that error comes up? > > there’s a few easy optimizations that we can make to reduce the startup time if it’s an issue (vscode gives that error when an extension takes longer than 500ms to start) @kevins8 I see that almost every time I open code or reload the window. It's shown before dendron loads and I don't have the preview open. I thought I saw an issue on GitHub but can't find it anymore

@User that was an easy one thanks.

One more! Is there a quick way to copy a note link from the Cmd+L menu? That would be a super useful feature if not.

@User not yet. https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title= 🙂

> Ah, it seems to fail due to the following schema in

areas.${workplace}.schema.yml

>

yml
> version: 1
> imports:
>   - journal
> schemas:
>   - id: daily
>     children:
>       - journal.journal.daily
>

> Is that an unsupported configuration when

${workplace}

is a namespace? > (I thought perhaps it'd get confused who its parent is, but that should be clear from the name of the schema file as far as I understand.) @User the schema syntax is still a little clunky. currently you need a

parent: root

to designate a root schema

Done!

more trouble today! I must have messed something up. I can no long option+click to click on [[]] links in .md files. I can click on the link in the preview but not in the text editor... what did I mess up?

@User hmm, i think that is controlled by the

Open Link (editor.action.openLink)

command. not sure how that gets updated. i usually use the

go to definition

shortcut to navigate links. do you get this issue when you initialize a new workspace as well? https://stackoverflow.com/questions/49861033/what-is-the-shortcut-for-ctrl-click-in-visual-code

@User there doesn't seem to be a short cut defined, but it used to show up exactly as described in your link when I would hover, now it doesn't. If I go to set the shortcut up how to I get it to accept the ctrl+click? I press control and it recognizes that but not the click.

@User can confirm that I don't get the same behaviour in a new workspace. It reverts back the way I remember. Can I just copy all my notes to the new workspace? Or is that asking for problems?

> @User > > my setup: > - I keep 3 versions of vscode (vscode, vscode insider, vscodium) > - I have a mac so I usually have two windows of each version running at any time > - i'm running on mac so i can toggle between windows using

cmd+~

> - each vscode version also has a custom keyboard shortcut which I've configured using alfred > > - vscode versions: > - vscode: used for coding > - vscode insider: two windows, one focused on dendron specific notes and one for personal notes > - both windows use the same vault but different workspaces (this is because vscode does not let you have multiple windows open to the same workspace) > - because you can define a custom path (https://dendron.so/notes/401c5889-20ae-4b3a-8468-269def4b4865.html) for your vault, you can still point two workspaces to the same vault > - vscodium: two windows, one focused on https://dendron.so documentation (use as reference as well as to update) and another for an alternate workspace i'm working on (eg. https://aws.dendron.so) > > the idea here is that I can access any note in any workspace using at most, two keyboard shortcuts. > > and no, i don't use folders inside any of my workspaces 🙂 @User I really appreciate your ideas and responsiveness. Thank you! I'm going to experiment with implementing some of the ideas behind Dendron in Emacs, which I use (in conjunction with org-roam and deft). Might also try doing the same with Roam, with namespaces.

> @User can confirm that I don't get the same behaviour in a new workspace. It reverts back the way I remember. Can I just copy all my notes to the new workspace? Or is that asking for problems? @User yep, that should work fine. i would check your workspace settings

> Open Workspace Settings

. that's really the only thing that changes between workspaces in terms of vscode settings