>Diagnostics Report

. see https://wiki.dendron.so/notes/a6c03f9b-8959-4d67-8394-4d204ab69bfe.html#check-the-logs

the graph might not update well after a refactor. there are some outstanding issues in our backlog

is this still the case after a reload?

So I was trying to show only h2 but the whole doc from below it was shown

And if I use

![[PID##causative-organism]]

instead of

![[PID#causative-organism]]

the whole doc is shown

can you try

![[PID#causative-organism:#*]]

?

Here is the note that goes into specifying ranges for note references: https://wiki.dendron.so/notes/f1af56bb-db27-47ae-8406-61a98de6c78c/#wildcard-headers-as-a-range-boundary

Yep this works

Will you guys eventually move Dendron to its own separate button on the VSCode Activity Bar? The Explorer interface can get cluttered up pretty easily, and given that Dendron has its own visual context elements, it would make sense to give it a separate spot in the UI.

yep - we have an outstanding item for a separate navbar (you can do it today by dragging the individual views into a blank section)

👍 for explaining what is happening and giving users a choice.

it took a few migrations to get to this point 😅

I'm going through the publishing guide and first things I noticed. The docs are from linux perspective. And the npm dependency is... inconvenient for Microsoft People and even more for non tech people

or maybe it's just me. Staying away from JS as far as I can

Note Graph showing a node that isn't there

now it's disappeared upon restarting codium

We have an open issue you can thumbs up that may be of interest, and feel free to contribute to the convo in the issue: https://github.com/dendronhq/dendron/issues/2177 You aren't alone, and many Windows users - especially in Enterprise contexts - aren't able to go through the prereqs process for CLI without considerable effort and introduction of risk from security policy perspective, etc. The feature request is to have a single binary or package that is self-contained. Otherwise, if you have a CI/CD process for the deployment or updating of sites within your environment, publishing can be done at that level vs. ran locally, too, if that is available. Same with WSL, though I think security policies in places may not allow WSL as an option to enable on Windows workstations

@User! It's CROP time (every other Wednesday) 🙂 Please vote for your favored community issue 👨‍🌾👩‍🌾: 1. [Reference to a linked list of notes](https://github.com/dendronhq/dendron/issues/292) 2. [Dendron doctor - get createddate from file attribute not now()](https://github.com/dendronhq/dendron/issues/444) 3. [code snippets in multi-vault setup](https://github.com/dendronhq/dendron/issues/376) 4. None of these (if there's an issue you'd like to add to rotation, please reply with a Github issue). To vote, respond with a 1️⃣ 2️⃣ 3️⃣ or 4️⃣ to this message. Voting closes Monday at noon Pacific Time.

Would be nice if Dendron when init a new workspace could follow the new standard and use

main

as the starting branch, instead of

master

as to how Github & Gitlab are doing.

Does Dendron create a git repository when creating a new workspace? If it does, let me know and I'll make sure it follows your git defaults at the very least

Dendron doesn't initialize git in new workspaces.

git

is used to do so, via

git init

. The default is

master

in

git

still, but it does provide directions if you wish to change the default behavior: > └──╼ $git init > hint: Using 'master' as the name for the initial branch. This default branch name > hint: is subject to change. To configure the initial branch name to use in all > hint: of your new repositories, which will suppress this warning, call: > hint: > hint: git config --global init.defaultBranch > hint: > hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and > hint: 'development'. The just-created branch can be renamed via this command: > hint: > hint: git branch -m So, you can change defaults with:

git config --global init.defaultBranch main

Or change current with:

git branch -m main

That being said, I've added the snippet to the docs that will go live tomorrow: https://github.com/dendronhq/dendron-site/commit/7eeed8e8745288fcc01d7cfe3cd69919141cc419

IMO would be great to have an option for full text search to be on by default!

I'm sure it came up already and it is probably a huge Feature. But it would be great to execute codeblocks and keep the Result like in Jupyter Notebooks. I've heard the Org-Mode implementation is even better

Yes, it has been requested quite a bit. We don't have an ETA on it, but it's something that we have discussed.

question would be what types of codeblocks would be runable as well. I mean it would depend on the choosen Language js maybe possible other languages could get harder.

for me Powershell and SQL would be great.

Maybe it would be enough to just add .ipynb files and still use the Notebooks Technology?

Hey it looks like publishing got messed up in the new release, all my katex notes aren’t rendering