> (and here I thought cmd and ctrl never appear on the same keyboard...) @User Welcome to MacOs, hahahaha

I'm definitely not an iPerson))

@User > what if you were highlighting a pdf text that is inside the assets folder? wouldn't that be preserved if you choose not to replace the existing file? > I think it could work best not by eliminating uuid or overwriting the files, but by checking if there's anything with the same name the - what should the proper behavior be if we spot an file with the same name? do nothing? replace? prompt user? - what if you had multiple asset files with the same name in different folders?

.
├── folder1
│   └── foo.png
└── folder2
    └── foo.png

- dendron would generate two files. if we just use the prefix, we wouldn't know that these were two different files - foo-uuid1.png - foo-uuid2.png

@User Well though good questions! I'll try my best to try to answer them. > wouldn't that be preserved if you choose not to replace the existing file? > Yes! If that is the behaviour that makes most sense, yes! And that's (almost) what I wrote in python to do - I asked to sort by modification date for groups based on the name radical (the file original name) . > what should the proper behavior be if we spot an file with the same name? do nothing? replace? prompt user? If you spot a file with the same name, I think you should just jump that one (thus, do nothing) - maybe prompt user, but (in my case, at least) it would take me some time to deny (or accept) all the prompts. Replacing get's into the first problem when you just overwrite any modification - and I don't think that would be the best default behaviour. > what if you had multiple asset files with the same name in different folders? If you have two files of the same name in different folders, you could use the folder to prefix it! Just like it's being already done with all the other files: everything, to get into the Dendron tree, already receives the prefix of the folders they were in, why not use the same method for assets?

another way of asking the same thing; why not name assets also with the same convention?

folder1.foo.png

😎

With note references getting better I wanted to ask if there are any plans to help prevent breaking references while editing. To use a dendron docs example: I think that the todos page would benefit from including the "Moving lines" part from "Tips". I add this to todos page:

## Reordering tasks

((ref:[[dendron.tips]]#Moving lines,1:#*))

This works out well in preview! (Though I don't know if it would work when exporting to static site). But if I edit the header in

dendron.tips

to something else then the reference just quietly breaks and shows nothing. Renaming notes changes their references automatically and headers probably need the same kind of love now). Or at least some visual indicator that this header is referenced somewhere and editing it would break things.

@User I think these would become available after bigger change related LSP (language server protocol). These things might currently be somewhat hard to do, since to do it properly requires monitoring and validating all the files in the vault, and showing diagnostics (errors) on broken links / references. In case this is done pre-lsp change, it would do all computation in the UI process, potentially making the vscode laggy. LSP will most probably cause also bigger changes in the codebase, so the more is built on top of the existing sources, the more tedious the migration will be. Anyway, @User to comment if I'm right or not 🙂

Yeah, I'm not asking for this to be implemented asap)) Just a thought on what's needed before note references can be considered done.

Was it so that the links currently break if the renaming is done outside of vscode (or even inside vscode, but not using the rename command)?

hmm I guess that must be the case if we don't have any cache files mapping the uuids and (old) file names together...

renaming files with F2 in vscode does break links)

yep. I guess with LSP we could spit out errors related to all broken links + give an option to automatically fix them

...or even just automatically fix them if it can be done

Hey guys with the new update to vscode it seemed to break dendron

any fixes yet for it?

@User haven't updated to the latest version yet. what is the error you're seeing?

well the engine is not loading

hang on i'll get a screenshot

I get that when trying to reload the index

both on linux and windows

that's an issue with frontmatter not having valid yaml

need to make friendlier error messages for that 😅

if you search for the note with the timestamp mentioned, you should be able to fix it by correcting or removing the frontmatter

ahhhh so is it a easy fix?

oh

yep. just updated to latest version of vscode w/out any hiccups

ok

it's fixed

thanks man

so what happened on my end?