but I have no autocomplete in the external pathes of my computer within the notes

is this expected

for now i search the file in terminal and then paste the link .... howevere i wondered if there was a more convenient solution ?

yeah, this is expected right now. you can move/symlink these files into dendron's

assets

folder to make working with these files less cumbersome. in the future, you'll be able to autocomplete file paths inside and outside of your workspace

Is there special variables available within a template? So I can do something like this in a template:

((ref:[[work.journal.<<Y.MM.DD>>]]#Tasks:*))

Similarly, it would be nice if I could conditionally add it:

[[if weekday]]
((ref:[[work.journal.<<Y.MM.DD>>]]#Tasks:*))
[[endif weekday]]

VScode doesn't seem to be picking up the 0.12.1 update, am I the only one not seeing it ?

It's not been updated on the Microsoft Marketplace. It's still at 0.12.0

not sure why I didnt think to check the marketplace 🤦‍♂️ thanks

@User i just checked the output of the build and it looks like the access token expired (microsoft rotates access tokens every 30 days which is a good thing). just updated and re-published. thanks for catching this!

@User not right now. what you can do is use a template to add a snippet prefix and use built in snippet variables: https://code.visualstudio.com/docs/editor/userdefinedsnippets#_variables

and no support for conditionals at this time. i've been using ansible at the moment when generating release notes https://github.com/dendronhq/dendron-template/blob/master/playbooks/templates/dendron.template.release.md#L19:L19

When renaming a note (cmd shift P Dendron : Rename Note) the .md file is indeed renamed however the Title field in the markdown header is not. Is this an expected behavior ?

yeah, this is because users don't can have titles that are different from the filename. instead of assuming, we just leave it in place

if renaming the title adds to your workflow, feel free to give us a feature request and i'll add it to the roadmap 🙂 https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

Quick question, is there a limit to the number of links that can appear on a page once published? I have a page with about 30-40 links to other pages which works fine in VSCode but when published it removes the links. Only keeping about 10 or so links seems to work. Thanks. If this is something that can be tweaked, happy to look into it, if can get a starting pount. Much appreciated

there shouldn’t be. we aren’t able to publish links to notes that aren’t made public but otherwise; they should all resolve. if you can send me a sample note/vault, i can take a look

Is there syntax to make reference blocks render usable checkboxes?

@User figured out the issue - currently, if dendron processes a link that it can't resolve (eg. the file doesn't exist), it will stop converting the page. this happens during the build process will push a fix for that today. what i'm thinking: - add a setting for site :

linkNotFoundBehavior

- it will have the following options: - `raiseError`: stop publication and raise error - `404`: send the user to a 404 page eg:

<a href="404.html"> The little prince </a>

but continue publishing. generate report of all bad pages after build will probably default to 404 behavior. lemme know if there are additional options you might want

@User there is submitting another feature request for us to implement that 😅

@User - thank you very much, you are absolutely correct - there was a page or two missing . The solutions sound like a great idea, thank you!

Is there a way to write and directly make a note public via Medium after I move it to Archives (I'm using PARA)?

Is there a way to flip the sense of the

[[labeled|wiki-link]]

to

[[wiki-link|my label]]

? Most of the other tools that I have do this following the MediaWiki syntax. Some additional templating might make for useful features at some point. E.g.

[[person.leo-da-vinci|{{title}}]

could be the same as

[[person.leo-da-vinci|Leonardo da Vinci]]

assuming Leo’s note had a

title:

attribute in the metadata block. Or did I miss something in the docs?

@User I think medium has a public API (https://github.com/Medium/medium-api-docs) so it should be possible with a medium pod (https://dendron.so/notes/66727a39-d0a7-449b-a10d-f6c438185d7f.html)

if you give us a feature request, i can add it to the roadmap 🙂 https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

for now, you could publish your notes in the archive and use medium's

import feature

to move it to medium

@User not right now but its something i want to support as a configurable toggle. could you submit a feature request? https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title= as for templating, its something we want to support. currently you can get it when you publish using liquid tags: https://dendron.so/notes/1693cee1-3d1d-45b3-a1d2-62a10010ea35.html we have this issue to track the sort of templating you're talking about. feel free to +1 it if this is important to you https://github.com/dendronhq/dendron/issues/168

How do I overwrite vim bindings so i can use various extension shortcuts? Notably, I can't use

CTRL L

(Dendron lookup) without doing

CTRL-SHIFT-P

then

CTRL-L

. EDIT: nevermind, this works ✅

"vim.handleKeys": {
        "<C-l>": false,
    },

(but if you have better advice, please lemme know!)

Trying to figure out how to disable vim's bindings for

CTRL SHIFT ENTER

so I can use `pkief.markdown-checkbox`'s "Markdown Checkbox: Mark Complete" now.

reading the docs > Any key in keybindings section of the package.json that has a vim.use in the when argument can be delegated back to VS Code by setting "": false what shortcut does

<C-l>

point to and does it have the

vim.use...

prefix?

something else to try is

<C-L>

(not sure if case makes a difference)