I suspect you may be operating in "Restricted mode," aka it doesn't know if it can trust the directory. In that mode, the main tools like Rust analyzer are quite restricted. All of your complaints should be resolved once Rust Analyzer/basedpyrite are up and running.

I do think they should have a more obvious warning that the current directory is untrusted, right now the little green warning in the corner is way too unobtrusive and will result in many people having the same issue as you.

I thought Zed was using tree-sitter: https://zed.dev/blog/syntax-aware-editing? Shouldn't it address all of these issues? Does tree-sitter not understand Python (basically the most popular language out there) and Rust "beyond superficial syntax"? I thought its whole point was that it understands everything about a language's syntax because it builds a concrete syntax tree?

Did you market the project as trusted? Récent update (à few month) requises the trust to reenable the analyses feature It took me a while to understand lol At Somme point I though that the parker were broken in my codebase xD

> And I greatly respect the small binary/download size

The latest x86_64 Linux build is 136MB. (https://zed.dev/docs/linux#downloading-manually)

As for your list of grievances, they all seem to boil down to the respective LSPs not doing their job? Does Ctrl-Alt-l (lowercase L, not Shift+i) include the language's server in the context menu, and are there any errors reported for it if it does?

It sounds like LSP isn’t working for you for some reason. Have you installed the extensions for those languages? These things are definitely supported via LSP

> Overall: It is taking a superficial view of the code base, and treating it more as text than a cohesive structure.

That is the part that makes the space heater