I installed the current version of Edge on Win11,
Version silverbullet 2.0.0-pre4-0eb191e43b09f9edefc2fc2096c47080de726135
And now the system doesn’t recognize folders and files that start with @.
Example: @desktop.md
It worked without any problems until I installed the current version.
The @ symbol is not allowed anymore in names. This is theoretically a restriction that could be partially lifted, but I wanted to keep the restrictions concise and simple for now (in my PR). It exists to not collide with the @123 and @L1C2 syntax when linking.
I’d be interested in the naming scheme you are using to require the @ symbol
Thanks for the clarification…
My folder and file structure comes from Obsidian, and I used to name files and folders with @ so they would appear before the numbered folders.
Before migrating, in Obsidian, I changed the wikilinks to full paths and forced the rewrite by renaming the main folder, and everything worked fine.
When I opened the structure with SB, everything worked perfectly.
The wikilinks, the files, and folders…
One more thing I found strange was that folders that didn’t have MD files weren’t showing up. For example, folders with images and PDFs.
But I understand that @ is a protected character.
Now I’ll have to rename my folders and files that have @.
And I’ll have to do it in Obsidian to rename the links since SB no longer gives me access to rename them.
Thanks!
But happy with the new version, because now the PDF transclusion works…
${template.each(query[[from index.tag "document" where string.find(name, 'PAGAR') limit 100]], template.new(" ${name}\n![[${name}|1200x200]]\n"))}
And these strings can stand standalone?
I mean, if not (if these strings are alsays suffixed to something else, e.g. page name) then, as I stated somewhere else (cannot remember where atm.), we can easily allow the @ etc. as leading characters, or even inside something given that last instance of them only will be treated specially, e.g. @Page Name will be OK, @Page Name@ will also be OK (does not match some grammar like @(\d+|L\d+(C\d+)?)$ or whatever it is, and also this could be allowed @Page Name @Wow! and @Page Name@123 will be the only one that would yield name = "@Page Name", pos = 123, and for example @Page Name@L5C10@123 would yield name = "@Page Name@L5C10", pos = 123.
Or do I miss something important here? That way many rules could be relaxed, I think, and without (much) ambiguity and with only simple rules to comprehend and to follow. 
OK, OK, I know I contradict myself a little, because I would like to see leading @ syntax for the (hopefuly) future citations. But we can still support the rest of it. After all, we can also disallow ^@L?\d as citation name (very minor issue comparing to than with the page naming).
Like I said, this is something that doesn’t cause inherent problems, your “rule book” just gets longer and more complex.