@User @User @User @User Thanks for the feedback. Here's what I'm thinking based on your suggestions: > 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. When importing files, if we detect conflicts, we'll generate a webview that shows you all the files that conflict. At that point you can either proceed or cancel (in the future, you'll be able to toggle a checkbox to decide what action to take on a per file basis) > another way of asking the same thing; why not name assets also with the same convention? folder1.foo.png 😎 🤯 hierarchies all the way down! love it. this will provide enough entrophy to make collisions unlikely while at the same time preserving the imported assets. @User would this cover your current use case?

> so what happened on my end? @User dendron currently doesn't index the contents of your metadata in real time. that's why we have the

reload index

command. instead it re-indexes on startup. if it finds a bad yaml header, it will choke. you will see the same issue if you have a badly formatted schema

ahhhh ok

thanks

here's the issue for it https://github.com/dendronhq/dendron/issues/188

this has been high on my bucket list for a while and this just put it over the edge. will address this in this week's release (or next week at the latest)

@User > This works out well in preview! (Though I don't know if it would work when exporting to static site). it does! note refs are carried over when publishing :) > But if I edit the header in dendron.tips to something else then the reference just quietly breaks and shows nothing. planning on adding an error message. haven't gotten around to this yet. > 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. In the future, just like you can rename a note, you should be able to rename a header. this will cause any references pointing to that header to also rename. its a more involved task and like @User mentioned, most likely will happen after the lsp migration. in the short term, will add that error message. long term, i've opened this issue to start tracking this: https://github.com/dendronhq/dendron/issues/189

> it does! note refs are carried over when publishing 🙂 @User does it work well enough for you to accept a pull request with such a line? ))

most definitely 🙂

seems risky, but ok). I sent a PR.

@User we live on the edge 😅 also, with the amount of typos i generate, i think this is the least of our concerns. when I do implement the header error report, i'll have a check before deploy that will sweep for broken note references

merged! https://www.dendron.so/notes/593206ea-5658-4874-bafd-18a138870f91.html#reordering-tasks

Latex and pictures don't work on the github page😦

😢

@User Is this a bug or I've done anything wrongly?

Or github pages simply doesn't support latex?

i don't think we support latex yet in published pages. pictures we do though

can you send me a link to the github hosting your site?

sure

for latex, give us a feature request and i'll add it to the roadmap 🙂 https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

what is the url of the page with the missing pics?

change  ->  and everything should work 🙂

Let me try, thanks! (I changed this when I exported it into a pdf)

got it. did it not work for pdf export having the initial

/

?

yep

could you file a bug report here so we can fix that going forward? https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title=

Sure, no prob

Hmm it didn't work @User