Kirill Bulatov
Kirill Bulatov
I disagree with the tendency to overcomplicate and believe that a simple `HashSet::contains`-like, case-aware, deduplication is all we need — this is exactly what VSCode and Sublime provide, the original...
@dalton-oliveira welcome to submit a PR. I think any good-first-issue labeled issue that has an approach description that more or less matches yours can safely get a PR straight away,...
https://github.com/zed-industries/zed/pull/12909 brought initial support for this feature which is almost complete but only shows a single, first signature help it gets (and also does not show description labels, just the...
Zed does not save any "workspace exclusions" yet, but it saves recent workspaces' information in the database, see https://github.com/zed-industries/zed/discussions/6703?notification_referrer_id=NT_kwDOACkO1bI5MjE0NzYyNjUwOjI2OTA3NzM¬ifications_query=repo%3Azed-industries%2Fzed+is%3Aunread#discussioncomment-8281516 for more details. We need to store such exclusions in the...
To copy my description here: https://github.com/zed-industries/zed/discussions/7204#discussioncomment-8335245 ESLint is yet another LSP server starting for specific languages and currently is very static and not flexible. All config values it takes are...
We have dedicated keymaps for other editors, including VSCode. People had added more bindings to those in PRs like https://github.com/zed-industries/zed/pull/7464 (that was for Intellij, but the idea is exactly the...
Oh, that's the point, I see (sorry, starting to forget what VSCode actions are at this point). We have exactly one duplicate line action now: https://github.com/zed-industries/zed/blob/7956a9a547949cf826d3e30f46c12a7edef67316/crates/editor/src/actions.rs#L154 and that one is...
Discoverability is always a problem for developers, so that's why I always ask external people to add to docs: they know it better. For me, that was "obvious" (not for...
Not really, that bug was caused by wrong approach to parsing of GitHub API responses, related to assets. In the error above, there's some npm and network error.
On a general note about the project panel slowliness (after implementing my own way with the outline panel tree): almost every operation in project tree goes through `update_visible_entries`, which clears...