initalized a new work space and threw my old vault in my but it's not picking it up

should I just add a new vault and copy and paste the old schemas and md files into it?

As far as I know handling other files beside images isn't fully supported yet. Of course you can link to them but there is no specific support. I think Syntax highlighting is provided by Vscode itself but may be wrong here

Is it using the same name (e.g. 'vault')? Then it should pick it up. Otherwise you could add a new vault pointing to your existing vault

Happy Monday everybody! Is there a way to turn off the partial case-sensitivity in lookup? e.g. I have a note "c.DigitalGarden". If I just type "digital" into lookup, that note is returned, but if I type "c.digital" it isn't.

You may need to edit your

dendron.yml

to point at the vault. Feel free to message me your config and I can take a look

Can you try searching for "c digital"? Using spaces when searching is more flexible. Otherwise that does sound like a bug if you would like to send a bug report to the Dendron GitHub repository.

Thanks @User -- yeah, using spaces works, but I will file an issue too if you don't mind. using spaces can be counter-intuitive when I know I want something in a certain namespace, and also can over-capture making it hard to get what I want.

1. for files, we recommend you create a folder named

assets

in your vault and copy files there. you can link to them using a standard markdown link. if you use

dendron paste image

, it takes the image in your clipboard and paste it in the

assets folder

2. syntax highlighting is provided by vscode 🙂

Is there a way to turn off the auto-hiding of the markdown header at the top of notes?

In your

dendron.yml

, have

enableAutoFoldFrontmatter: false

present under

workspace:

, so:

yml
workspace:
    enableAutoFoldFrontmatter: false
    ...
    ...

Hmmmm or maybe it is

autoFoldFrontmatter

? Should test, since this is what's listed here: https://wiki.dendron.so/notes/f83c1d87-eac0-48f3-a5cf-8a69989d8ec1/#autofoldfrontmatter

It should be the former. It has been migrated. The doc has also been updated here: https://github.com/dendronhq/dendron-site/pull/235 but It hasn't been merged to the site yet.

Thanks! I'll see if that solves it. Appreciate the help.

copy-pasting the relevant changes here:

### autoFoldFrontmatter
> This setting is scheduled for deprecation 📆
>
> Use [[enableAutoFoldFrontmatter|dendron.topic.config.dendron.workspace#enableautofoldfrontmatter]] instead.

## enableAutoFoldFrontmatter

Sets the frontmatter folding behaviour.
When set to `true`, Dendron will automatically fod the frontmatter when opening new notes.
This includes newly created notes, and existing notes that are being opened for the first time in the current session of VSCode.

- default: false

Yep that worked thanks so much.

Ah! Thanks for the PR reference. I've merged. When

dev

is merged to

master

tomorrow, with release, the docs will be updated on wiki.dendron.so 🙂

hmm, tried out next publishing again today but I found out that at the last step (

dendron publish export

) does not put the resources in a

/docs

folder which I need to point to when choosing the directory for github pages, is it intended behavior? (or I'm getting something wrong)

by default, nextjs exports to

out

folder. to export to

docs

, you want to run the following

dendron publish export --target github

I 💖 how the task note features are coming together & how they use text decorators! Question: should the results of

completed: true

be visible as a text decorator, or is that setting just more "internal" to the task note? Currently I see whatever is written after

status:

show up in other notes, but I don't see anything change in other notes when I put

completed: true

or

completed: false

.

i don't think we're using

completed

field atm 😅 setting

status: x

will indicate that its complete

Is there a frontmatter

keyword

which can allow me to position the page in order I need? What is happening?

root.md
    note1.md
    note3.md
    note2.md

What I want - is to specify a detail in frontmatter for a note so that it shall always appear in certain order while publishing

Yep, that's the

nav_order

property -> https://wiki.dendron.so/notes/f2ed8639-a604-4a9d-b76c-41e205fb8713.html

how can I disable daily / scratch notes in dendron? The daily notes are randomly created as stubs with the latest version (0.66.1)

yep, finally got publishing working 🥳 curious abt is this is "default way" to publish? If yes, this should be included in the publish page https://wiki.dendron.so/notes/e5st4LFLtIwwbQmC6JBaF/

where exactly do i place the

{
  "key": "{desired keybinding}",
  "command": "dendron.lookupNote",
  "args": {
    "selectionType": "selection2link"
  }
}

This should be in

keybindings.json

which can be accessed by

Preferences: Open Keyboard Shortcuts (JSON)

. This will open VSCode's keybinding config file and it will contain all of your user defined keybindings for everything in VSCode not just Dendron.

good point. we'll want to update the documentation. do you think you could submit a pull request? 😇

Sure thing, two questions/suggestions here: 1. Maybe we can replace the "Quickstart" section in this page https://wiki.dendron.so/notes/4ushYTDoX0TYQ1FDtGQSg/ with a page reference to publish/cook/github, which is this page https://wiki.dendron.so/notes/yg3EL1x9fEe4NMqxUC3jP/ because I found that most of us use github while fail after faithfully following the instructions under the quickstart section because it is does not include detailed instructions like in the cook/github page 2. What does `dendron publish build`(under https://wiki.dendron.so/notes/2340KhiZJWUy31Nrn37Fd/) do? Is it necessary for publishing? (will submit a pull request after both of these points are confirmed)

oh my gosh... selection2link is so much better!! Quality of life difference

Glad you like it. the default behavior (selectionExtact) also has an option to leave a trace of the extracted selection, which could be useful in other cases. 🙂