OK, I just made a new note called "New Note Test" using the lookup. This one exhibits the same behaviour. @User, are your note names in Caps? because all my other ones are lower case and aren't affected.

Also, when I created the new note, suddenly my tree view populated with multiple instances of 000 Index.

Hmm. the first aprt of my note is is caps.

my schema starts with "DAT"

Created "new note test 2", doesn't have this problem. Possibly this is just affected notes with capital letters in the filename.

Hmm, why would that be happening?

No idea! But probably this knowledge will make the bugfixing easier.

I hope you didn't lose too much data 😦

yeah, thanks.

I'm thankful I took the time to figure out and setup up a backup snapshot system a few weeks ago

damn, this is such a 😱 thing to happen

https://github.com/dendronhq/dendron/issues/312 @User I filed an issue here if you'd like to add any details

Anyone having issues with images not rendering in the preview since 0.13.4?

Nevermind had to reload vscode and it was fine again

@User @User @User thanks for the heads up. losing data is NOT acceptable and apologize that this has happened. will be taking a look at this asap!

updates on this --> i found the issue (tree view lower cases all names before passing it to the engine which indexes with cases) and i'm currently releasing a new version

just deployed. see announcement --> https://discord.com/channels/717965437182410783/737323300967022732/771013239982129173

is there a specific reason for the lowercase transform? If I already have a file

Index.md

then Dendron currently forbids creating an

index.md

saying that this would overwrite an existing file. I can't really think of a compelling example why I would want such similar filenames)). But still, aren't these names totally valid on the OS level?

it depends on what sort of file system a user has. eg. mac (HFS+, now APFS) is case in-sensitive by default

the reason we do the transform is to normalize filenames across different file systems

Yeah, this is definitely an issue on Mac:

bash-3.2$ ls -l index*
ls: index*: No such file or directory
bash-3.2$ echo "This is a test" > index.html
bash-3.2$ ls -l index*
-rw-r--r--  1 mtl  staff  15 Oct 28 16:00 index.html
bash-3.2$ cat INDEX.HTML
This is a test

wow, really? Trust mac to think different) What if I create such files outside Dendron and then try to open my workspace?

you mean files with mixed case? dendron will work fine with existing files

and its not just mac. this is something that you can configure depending on what file system you have

Ok, thanks for the info)

moving forward, we'll probably be more consistent with names (eg. paths should be lowercase kebab format. you can have mixed case in your notes using

title

field which all UI components will use to render the names)

I think it makes a lot of sense to normalise file names to lower-case. IMHO as a common denominator it increases portability since it avoids issues with file systems which don't differentiate.

Thanks for the quick turnaround @User . Back to purring smoothly now. I hope unicode namespace support continues into the future. I use unicode to make visually distinct icons for indexes and important notes, and use them as lead characters in searches and search filters.

@User glad to hear it. and unicode support will continue to be a thing!

> and its not just mac. this is something that you can configure depending on what file system you have @User Famously, all of the FAT variants and Amiga!