Thank you for this... sorry for late reply. just got my pc repaired, had to format and all.

If I change the auto-configured vscode workspace settings in a Dendron workspace so that the root of the workspace is itself, not a path called "vault" - i.e. change my dendron.code-workspace file to contain

"folders": [
        {
            "path": "."
        }
    ],

Am I going to cause myself problems with Dendron? I was doing some automation using tasks and VScode's default root being Vault makes things really messy...

nope, that'll work just fine

i try using dendron and Obsidian together for the obvious reasons. (hi @Bouza ). How do i do it best? Looks like importing files copies them which kinda destroys the reason to use 2 tools at once. also, while migrating I set up dendron in the default thingies. Now it looks quite messy with a bunch of folders and files sitting around the

C://user/

directory. Can i change the path and which files are part of it?

Same question from here. Im also interested in experimenting to publish an Obsidian vault

Has there been any progress on the

Preview shows "Start anchor ... not found" when linking notes. #2568

issue? The last update was on March 15th, stating that it was being tracked internally,

[[Preview Shows Start Anchor Not Found When Linking Notes|dendron://private/task.2022.03.15.preview-shows-start-anchor--not-found-when-linking-notes]]

. I've having to work around it by making the block anchors into headers (i.e.

#^NE1

, this keeps them not visible in the preview) and then referring to them as headers (

#NE1

). It works, it is just sort of a pain as I need an opening and closing header, and it clutters my outline.

not yet - what are you creating block anchors of? note that this behavior should work - the ticket mentioned some edge cases when highlighting a single block or within code blocks

I had both single and multi-block anchors, all of which respond with

Start anchor not found

regardless of whether they are custom or generated by

Copy Note Ref

Is the idea that the MySQL will replace the JSON cache, or at least have the same/more information? Just thinking about some python automations to notes and wondering if it's worth waiting or working with the cache

AFAIK, the plan is to have the sqlite backend eventually replace the JSON cache altogether.

Could you create a separate issue with a small example of how it doesn't work on your end? I couldn't seem to reproduce it on my end. https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title=

What's the correct way to clone and initialize a remote vault? Do you initialize dendron first, then add a vault, or do you just clone directly? (The intent would be a single shared repository, making it easier to commit changes back to master. Don't want to have to navigate into separate vaults and commit individually.)

if the vault is already part of the

dendron.yml

, then dendron will clone it automatically if you are looking to turn a vault into a remote vault, we have a command for that at https://wiki.dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f47#vault-convert

Does the workspace file have to be called just dendron? If you rename it will dendron not work?

Hi, I just installed Dendron and am not having any luck with it. I'm getting an error trying to create a note using "C-L dendron" "Create New" I then get an error pop up error that is unreadable as it seems to be a map of position:character... it starts "doctype html ... Also in the "Graph Panel" there is an error: {"name":"DendronError","status":"unknown","payload":"No Engine: c:\\Users\\\\Dendron"} I've restarted Code, but haven't done any other troubleshooting. Any suggestions?

Thanks for the reply! I've converted a vault to remote and pushed it to a remote repository. My issue is how to best pull it back down and properly initialize it. In a new folder, if I clone my repo the files pull down but Dendron is not initialized. I then do the command to initialize a workspace. The problem is, that the newly initialized workspace creates a different folder hiearchy than the originally cloned project. What is the process for correctly pulling the remote? Initialize first then pull somehow? Pul then initialize? The real question is how to clone the remote, and keep the original hiearchy so when making new notes they go into the same vault.

I found the issue. I didn't realize that this started up something on localhost. I had to update my NOPROXY setting to include that

glad you figured it out. for context, the mental model for Dendron is as follows: - the workspace is the top most folder you create when you run

Initialize Workspace

. It is at the same level where the

dendron.yml

file is located - a workspace consists of one or more vaults for note creation within a multi-vault workspace, see https://wiki.dendron.so/notes/24b176f1-685d-44e1-a1b0-1704b1a92ca0

Thanks!

Bumping this question back up - You can wildcard a note reference at the end to find all children, like

![[demo.journal.2021.*]]

https://wiki.dendron.so/notes/AMc4PzACuK0SfltZ8rcV6/ Is it possible to wild card at the beginning to find children that are arbitrarily deep, like

![[*.some-parameter.*]]

which would return: - parent-1.x.y.z.some-parameter - parent-1.x.y.some-parameter - parent-2.a.some-parameter.another-child I know I have instance of

some-parameter

in my hierarchy but it's not at a consistent depth.

that's currently not supported. if you submit a feature, we can track it on the roadmap 🙂 https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

dumb question - how do i know i'm consuming bug / patch fixes on my dendron published site? is this governed by the cli-version i'm using? e.g.

"@dendronhq/dendron-cli": "^0.110.0",

Dendron + Obsidian

Yes - continually bumping the cli-version will guarantee you're using the latest code for your site. One thing to note - for npm, the

^

in front of

"^0.110.0"

means that any version equal to 0.110.0 or greater is acceptable - so to guarantee you're using the latest, bump that number up (i.e. in this example,

^0.111.0

). Sometimes in Github Actions pipelines, the older versions of binaries may get cached and the

^

won't always pick up the latest available

Thanks for the info!

you can also just specify "latest" as the version and should just work

Hi has anyone succeeded in deploying a site using gitlab?

Yes, but in private hosted instance, but it works!

Great news @rlh1994 ! How did you do it? I haven't found documentation on this, and I'm not good at CI

What is the situation with custom css? There's a wiki page that describes it, but theres no theme option in the dendron.yml file, so the wiki seems outdated