No not really

for my own notes I've thought about using a separate hierarchy for lexical information, but I'm iffy on whether or not it''s useful vs just text searching for the term in my notes. It would look something like, each term would have a node

lex.<term>

, and then in notes referencing the definition, "`Here's the [[term|lex.term]] in a sentence.`

and you could mouse hover over the link in the editor to see whatever the content of the lexical note is

and then adding hierarchies if terms start to accumulate

Interesting idea, thanks

hope you'll let me know if you find a good/better way of doing this

Sure thing

how can I reference all of the notes only in the layer of the hierarchy directly below the current note?

![[projects.*]] embeds not only the children of the current note, but also the children of those notes

Not sure if this is the right place to ask, but how do I get word-suggestions working? I.e. I want to write something and then get a suggestion based on the words in my document. For example

som|ething

. At the moment I write

som

and either get not suggestions or it suggests me something markdown-relevant, like

link

or

h1

or

unordered list

. I found

"editor.wordBasedSuggestions": true,

, but it doesn't seem to do anything relevant.

how are you triggering those suggestions? On my setup I get word suggestions by default when I hit

ctrl+space

in the middle of a word

I do it with

ctrl+space

, too.

Alright, I installed an extension called "All Autocomplete" and now it works. Would prefer a solution without installing anything, but for the time being this is good enough.

Preview Mermaid in Dark Themes

refactor hierarchy regression

my new daily note today has

traitIds: journalNote

in the frontmatter. I see that traits were added in the new release but i can't find info about this metadata. Is there a place i can learn more?

just this for now as far as I know: https://wiki.dendron.so/notes/bdZhT3nF8Yz3WDzKp7hqh/

traits

We currently do not support this but feel free to submit a feature request and we can track it in our roadmap: https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

1. What is the difference between the Markdown pod's "Export to Markdown" and "Publish to Markdown"? As per this page (https://wiki.dendron.so/notes/13c4a608-0a32-4c62-9c7e-2b7f9f2d18bf/), both convert Dendron specific Markdown to regular Markdown. 1a. Why is the Export marked as 'experimental' but the Publish is not? 2. Is there any Dendron-to-Markdown export that appends a Backlinks section at the end of each exported Markdown file?

Are images expected to be shown in the local publishing preview (output of

dendron publish dev

)? Right now, I'm not seeing images in published notes, but they are present in Dendron previews. See image below

Images in Publish Preview

Hi everyone, I can't install the dendron-cli > npm install @dendronhq/dendron-cli > npm ERR! code ETARGET > npm ERR! notarget No matching version found for @dendronhq/dendron-11ty-legacy@0.7.2. > npm ERR! notarget In most cases you or one of your dependencies are requesting > npm ERR! notarget a package version that doesn't exist. I checked the following site and thread but I don't know how or where to get the missing package ? - https://github.com/dendronhq/dendron/issues/776 - Thread archived: #build-site regression I currently have the Dendron v0.73.1 extension installed via VS Code

What's the command you used to install it? Could you try doing

npm install -g @dendronhq/dendron-cli@latest

?

the command come from this page: https://wiki.dendron.so/notes/2340KhiZJWUy31Nrn37Fd/

Could you try using it in a new, clean directory?

I have also tried the command you proposed and get this: > npm install -g @dendronhq/dendron-cli@latest > > ... > > changed 979 packages, and audited 980 packages in 1m > > 169 packages are looking for funding > run

npm fund

for details > > 14 vulnerabilities (4 low, 10 high) > > To address all issues possible (including breaking changes), run: > npm audit fix --force > > Some issues need review, and may require choosing > a different dependency. > > Run

npm audit

for details.

That looks like it worked, try running

dendron --version

I run dendron --version and got this: > dendron --version > > dendron : File C:\Users\Zork\AppData\Roaming\npm\dendron.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170. > At line:1 char:1 > + dendron --version > + ~~~~~~~ > + CategoryInfo : SecurityError: (:) [], PSSecurityException > + FullyQualifiedErrorId : UnauthorizedAccess

Dendron CLI on Windows