Top-Ranking Issues (All Time) 📊

[JosephTLyons]

Updated on 02/24/2025 07:06 AM (EST)

feature

1. Build and Debug support #5065 (1803 👍)
2. Add a diff view #4523 (799 👍)
3. Codeium support #4726 (718 👍)
4. Rainbow brackets #5259 (668 👍)
5. Jupyter Notebook #5273 (525 👍)
6. Helix keymap #4642 (452 👍)
7. Source control view panel #4367 (401 👍)
8. Test runner integration #5242 (342 👍)
9. Pin to code structure while scrolling (aka "sticky scroll") #5344 (337 👍)
10. Show inline previews for rgb hex color strings #4678 (317 👍)
11. Support using ollama as an inline_completion_provider #15968 (247 👍)
12. Telescope-style search box #8279 (240 👍)
13. Dev Containers #11473 (237 👍)
14. Microsoft Debug Adapter Protocol support #5307 (224 👍)
15. Which-Key like menu #10910 (206 👍)
16. Option to combine the tabs-bar into the titlebar #5066 (196 👍)
17. Make the Python experience wonderful #7808 (185 👍)
18. Spell Checking #5305 (181 👍)
19. easymotion vim #4930 (180 👍)
20. Add build time options to disable ML/AI features #6756 (169 👍)
21. Add options to hide title and status bar #5120 (169 👍)
22. Improve auto-completion of DOM tags in React.  #4271 (138 👍)
23. AI Assistant should have embedding context of the entire codebase #15924 (109 👍)
24. Highlighting of special code comment types like TODO, INFO, etc. #11895 (104 👍)
25. Code completion icons #4943 (97 👍)
26. Smooth scrolling #4355 (94 👍)
27. Support LSP Semantic Tokens #7450 (93 👍)
28. Pretty TypeScript errors #7844 (92 👍)
29. Selection-first modal editing (like Kakoune, Helix editors - alternative to "vim mode") #4888 (91 👍)
30. Support Difftastic for visualizing code diffs #9721 (86 👍)
31. Support opening .code-workspace files to open vs code type workspace directly #9459 (83 👍)
32. "Smooth Caret" animation #4688 (83 👍)
33. ZedAI Multi file edits like Cursor's composer #16562 (75 👍)
34. can we have this app in flathub and snapstore #9922 (72 👍)
35. Add support for Tabnine #4504 (72 👍)
36. Flash.nvim style search in a document. #14801 (69 👍)
37. Support for non UTF-8 text encodings #16965 (69 👍)
38. iOS support for iPad #11889 (68 👍)
39. Support for quarto's .qmd file format #12406 (68 👍)
40. Zen mode #4382 (68 👍)
41. Mermaid diagram rendering in Markdown preview #10696 (65 👍)
42. Block comment command #4751 (65 👍)
43. Support AWS Bedrock as an Assistant provider #16544 (64 👍)
44. Animated/smooth cursor movement #4991 (58 👍)
45. org-mode support #11138 (57 👍)
46. Allow add custom AI assistant provider #15732 (54 👍)
47. Drag tab to open new window #6722 (53 👍)
48. Implement Leap Key Navigation #4934 (53 👍)
49. Support per-file tab (indentation) settings: tab_size, hard_tabs #4867 (51 👍)
50. User configurable mouse bindings (like keymap for key+mouse) #10647 (49 👍)

bug

1. Font rendering on LoDPI displays #7992 (194 👍)
2. Zed downloads NodeJS binary and npm packages from Internet without user’s consent #12589 (115 👍)
3. Fonts are blurry (Windows 11) #14113 (65 👍)
4. Only some ligatures are being applied #12176 (47 👍)
5. GPUI overdraws too much #8043 (39 👍)
6. The error underline looks bad #7436 (38 👍)
7. Prioritize exact matches in autocompletions #12698 (37 👍)
8. Inputting Japanese Characters in the Zed Terminal vs. iTerm2 #9900 (36 👍)
9. Linux Shortcuts don't work with non-latin / international keyboard layouts #14053 (34 👍)
10. Mouse selection scrolling too fast #12046 (29 👍)
11. ssh support on windows platform #19892 (29 👍)
12. Zed not respecting tab size when saving file #4842 (28 👍)
13. Project panel directory closes when installing project dependencies #13762 (27 👍)
14. copilot does not respect proxy #6701 (26 👍)
15. [linux] Vulkan ERROR_INITIALIZATION_FAILED #8168 (22 👍)
16. Zed refuses to use GPU (Nvidia) WSL 2 #15295 (22 👍)
17. blade: Text is rendered either too thick or too thin #13564 (21 👍)
18. Zed failed to open a window: NoSupportedDeviceFound #13441 (20 👍)
19. Zed keeps checking for LSP updates (and disabling LSPs irreversibly in the process), Even when offline, And this is really hurting my UX. #9789 (19 👍)
20. Incorrect spacing of terminal font #11744 (19 👍)
21. Zed memory leak, TOML extension subprocess named "taplo" requests almost 30 GB real memory some hours later #13190 (19 👍)
22. Lines with RTL text aren't rendered correctly #7465 (18 👍)
23. linux: Keyboard shortcuts do not work on non-English keyboard layout #10972 (18 👍)
24. Search project symbols not working on _python_ project #16749 (18 👍)
25. "Sort JSON" code action does nothing #16746 (17 👍)
26. Cannot uninstall extension on windows #18153 (17 👍)
27. Terminal input is slow #18263 (17 👍)
28. Dark Text on Light Background is Rendered Weirdly #19100 (17 👍)
29. Unable to resolve module './App.vue'  #8336 (16 👍)
30. font_features non-functional on Linux #15752 (16 👍)
31. Regression: TypeScript with Yarn PnP configuration not working in Zed v0.154.2 #18410 (16 👍)
32. gopls: packages.load error: JSON decoding failed : invalid character 'x' in string escape code  #11647 (15 👍)
33. All Zed extensions are blocked corporate firewall (Cisco Secure Client) #14730 (15 👍)
34. Several node processes launches every time I open the app and cause 2+GBs of RAM usage #16430 (15 👍)
35. Go To Definition broken on Zed: v0.149.3 (Mac) #16619 (15 👍)
36. Go to definition sometimes opens a new tab "Definitions for X" with a single snippet instead of actually going to the definition #6730 (14 👍)
37. Newline indentation does not follow my tab size setting (in a svelte file) #6861 (14 👍)
38. Characters spacing a bit too large #7621 (14 👍)
39. Last manually-closed workspace reopens on Zed startup #7759 (14 👍)
40. Problem with Function Keys on Keyboard 65% [67-keys] #4435 (14 👍)
41. Zed uses lot of RAM #18673 (14 👍)
42. inline code completion frequently leaves a {{INSERTED_CODE}} artifact at the top of the inserted code #19471 (14 👍)
43. Leading slash with env::current_dir() in Windows #20559 (14 👍)
44. C# Extension - Go to Definition opens blank file #11104 (13 👍)
45. Turning off soft wrap via command doesn't really work properly #13286 (13 👍)
46. Text rendering has glitches for pathologically large files #5355 (13 👍)
47. GPUI window resizes are very slow on Linux #15311 (13 👍)
48. Copilot autocomplete is ignored when there are trailing lines in a document, and no characters present on the line of the suggestion. The tab key inserts spaces instead #4549 (13 👍)
49. vim motions "v a t" or "v i t" is not working #16034 (13 👍)
50. Closing one Zed window closes every Zed window #17362 (13 👍)

meta

1. Make the Python experience wonderful #7808 (185 👍)
2. Audit and document Zed network connections #24804 (2 👍)
3. UI & Theme Contrast #23914 (1 👍)
4. UI implications of hidden tabs #23930 (1 👍)
5. Popover UI layering problems #23917 (0 👍)

unlabeled

1. DeepSeek R1 inline issues #23640 (23 👍)
2. Support Zed usage when offline / without network #24878 (19 👍)
3. Add shortcuts for answering dialogs #23106 (6 👍)
4. AI autocomplete breaks context menu completion #22925 (5 👍)
5. Permalinks support enterprise git repository with custom root domain #23103 (5 👍)
6. LINUX | Signature help in completion doesn't render consistently #23692 (5 👍)
7. Large files without newlines (all on one line) cause Zed to hang/crash #16120 (5 👍)
8. Syntax aware folding (indents.scm support) #22703 (4 👍)
9. Expanding Syntax Highlighting Customization #23277 (4 👍)
10. Add editor::ToggleAllFold #23397 (4 👍)
11. Different color / font for AI and user text #23676 (4 👍)
12. Git Blame links to wrong PR #25044 (4 👍)
13. close diagnostics buffer when empty #22986 (3 👍)
14. Updating to v0.168.2 breaks GPU support on Linux #23057 (3 👍)
15. Automatically convert strings with template expressions into template strings #23232 (3 👍)
16. format_on_save is ignored when saving a remote YAML file #23489 (3 👍)
17. changing pwsh through terminal->shell->program setting on windows to new powershell causes a panic on launch #23872 (3 👍)
18. Option to control when to show AI completion (Supermaven) #22924 (2 👍)
19. Disable border in centered layout #22971 (2 👍)
20. Nested outline for (javascript) functions  #23075 (2 👍)
21. LSP start failure in one open project causes the "Failed to run X. Click to show..." message to be displayed in all other project windows #23431 (2 👍)
22. Doesn't understand the difference between tab_width and indent_size in editorconfig #24108 (2 👍)
23. Cannot show a long line of CJK charactors (e.g. Chinese) completely #24175 (2 👍)
24. Hotkeys not working on Ubuntu 20.04 when Cyrillic locale is used #24499 (2 👍)
25. Changing model at runtime with NIXOS specific read-only configuration file #24537 (2 👍)
26. Crash when an edit prediction suggests inserting a newline immediately after the final message header in the prompt editor #25377 (2 👍)
27. Markdown rendering issues in tooltip for commit #25423 (2 👍)
28. Format Selectins Not work, it works as Format Buffer #22768 (1 👍)
29. "Fix all auto-fixable issues" never works #22920 (1 👍)
30. Possible failure of locale env propagation to language server #22975 (1 👍)
31. soft_wrap setting does not work when set in languages.Markdown for documents with frontmatter #22999 (1 👍)
32. Linked edits and completions don't work together #23028 (1 👍)
33. IME mode change shortcut not working #23105 (1 👍)
34. remove_trailing_whitespace_on_save shouldn't remove whitespace in string literal #23126 (1 👍)
35. Show panel name on icon hover for expanded panels #23336 (1 👍)
36. Make editor: go to ...split split for target location of the same file #23390 (1 👍)
37. Assistant Panel: Model selection should be conversation/tab specific #23484 (1 👍)
38. Use lsp workspace folders instead of starting a language server per worktree #23637 (1 👍)
39. Consider other heuristics for selecting which keybinding to display #23660 (1 👍)
40. Alt-click and drag to add multiple cursors to multiple lines #23650 (1 👍)
41. Let me type an absolute filepath in the file finder #23740 (1 👍)
42. Opening a new window flickers before opening an empty buffer #23742 (1 👍)
43. Next/Prev keyboard nav for Find In Project list #23781 (1 👍)
44. GoToDefinitionSplit doesn't split if the definition is in the same file #24982 (1 👍)
45. Rendering of keyboard shortcuts for split pane is lagging behind #25047 (1 👍)
46. Ruby extension doesn't have a working language server by default #25099 (1 👍)
47. Vim: Typescript/tsx anybrackets selection is wrong #25146 (1 👍)
48. Collab panel, add contact no value entered in search from value no matches #25453 (1 👍)
49. Collab panel, chat ui problems with copy message #25454 (1 👍)
50. Not Responding on Waylan Ubuntu 24.10 #23695 (0 👍)

crash

1. crash after compile on windows minigw #13575 (14 👍)
2. Crash on linux: Aquire image error ERROR_SURFACE_LOST_KHR #14225 (8 👍)
3. Linux: Zed completely freezes NVIDIA external monitor when launching or resizing window #18106 (8 👍)
4. Editor constantly freezing in a large Rust codebase #19022 (5 👍)
5. Zed won't even start on Linux for me anymore. #18573 (3 👍)
6. Ruff extension: language server error #19408 (2 👍)
7. Crash using AI workflow feature #17422 (1 👍)
8. unable to run zed error info Instance extension "VK_KHR_get_physical_device_properties2" is not supported. #17598 (1 👍)
9. Crash upon using vim::repeat in vim_mode #18118 (1 👍)
10. While opening zed, the window freezes. #20645 (1 👍)
11. Excessive memory consumption on project search with large files present #20970 (1 👍)
12. Zed crashes when using ciw vim motion in assistant panel over collapsed actions #22342 (1 👍)
13. Panic when pasting /default context over full selection #22675 (0 👍)
14. Language server error: powershell-es #25249 (0 👍)
15. [Linux] Toggle back full-screen crash window [F11] #16117 (0 👍)
16. Hang if window closed during auto update #18339 (0 👍)
17. VulkanError(ERROR_INITIALIZATION_FAILED) on NVIDIA after resuming from sleep (vkcube is fine)" #18553 (0 👍)
18. Crash on selecting workflow #18894 (0 👍)
19. unresponsive on startup checking for update #19699 (0 👍)
20. Panics on first start with flatpak #20014 (0 👍)
21. Instantly Hangs Cinnamon on boot on Mint 21.3 #20131 (0 👍)
22. Blade-graphics fails at init 846 in gentoo #21164 (0 👍)
23. Snippet with nested location with same order [gif inside] #22157 (0 👍)
24. Linux: Zed causes brief system freezes when opening new windows #22320 (0 👍)

---

For details on how this issue is generated, see the script

[exalted]

:two-cents: You'll know better, but a GitHub project sounds like a better solution.

[JosephTLyons]

:two-cents: You'll know better, but a GitHub project sounds like a better solution.

It would be nice to have something that is more directly supported by GitHub with less custom code involved, but I don't know if GitHub Projects support sorting on the fields I need. I checked it out and wasn't able to find a way to sort on reactions and comments and such. You can create custom fields in the project table, but you'd have to manually update those, or write another script to tap into them. I'm not sure what the best solution is for generating a list like this - this is just my first attempt.

[maxbrunsfeld]

This is very cool @JosephTLyons; thanks for setting it up.

[JosephTLyons]

This is very cool @JosephTLyons; thanks for setting it up.

Yeah no problem

I'm currently running it manually; I don't have any experience with GitHub actions and I don't know want to assume there are enough Action Minutes to go around, but if I spent some time to learn it and if there were enough minutes to spare, I could try to automate it to run once a day.

I've done my best to optimize the script, it still takes about 5 seconds to run it because I can't seem to find a way to limit the query size using the GitHub Search syntax, so even though I only display 5 items per label, I have to pull all open issues per label and slice the list down to size locally.

[clo4]

I have to pull all open issues per label and slice the list down to size locally

@JosephTLyons I think you should be able to use ?per_page=5 in the query, eg. https://api.github.com/search/issues?per_page=5&q=... -- I've had to fight the API to get more than 100 issues for the fig support dashboard 😄

Also, should be possible to do this concurrently - if the script is public, I'd be happy to optimize it :)

It can probably just run in a repo on your user account, using a gh actions schedule. If the repo is public, you don't need to worry about it using up your minutes!

[JosephTLyons]

I have to pull all open issues per label and slice the list down to size locally

@JosephTLyons I think you should be able to use ?per_page=5 in the query, eg. https://api.github.com/search/issues?per_page=5&q=... -- I've had to fight the API to get more than 100 issues for the fig support dashboard 😄

Also, should be possible to do this concurrently - if the script is public, I'd be happy to optimize it :)

It can probably just run in a repo on your user account, using a gh actions schedule. If the repo is public, you don't need to worry about it using up your minutes!

I'm currently using PyGitHub in a Python script. I haven't found how to limit the results using it, as the search uses the search syntax that you have on the frontend on the issues page. I probably missed something, but I felt like I couldn't get the "per_page" filter (or any other limit to the final query) to work there:

https://github.com/zed-industries/feedback/blob/347ecc15c8b0f4f696d91075f9d9f2f558cad5d0/scripts/update_top_ranking_issues/main.py#L41

[JosephTLyons]

Need some opinions here. Previously, I was just skipping all issues with these tags ("discussed", "meta", "needs info", "triage"}, as these type of labels are just optional ones; all issues with these labels have other "core" labels that are required.
We are adding more more labels now and it seems issues can now have multiple "core" labels, which means issues can end up in multiple label groups in the generated markdown above. I'm not sure how to handle this. I could either filter out duplicate issues, but this would be a bit misleading, since issues would just not show up in places they technically should, or maybe I just get rid of the label exclusion list all together and allow all duplicates to surface in all label groups, but this would probably result in a bunch of noise.

Until I get some feedback on this, I will just generate the list assuming that all issues will at least have one of the following labels: "enhancement", "defect", "polish, and "documentation".

[iamnbutler]

Honestly, tags will probably be fast and loose for a bit while we figure out how to parse feedback.

In the coming few weeks the fire hose will probably open up a lot, as I think we'll be increasing the amount of people with access by triple digits.

Suggestions are welcome for a framework to organize/parse feedback.

[JosephTLyons]

Honestly, tags will probably be fast and loose for a bit while we figure out how to parse feedback.

In the coming few weeks the fire hose will probably open up a lot, as I think we'll be increasing the amount of people with access by triple digits.

Suggestions are welcome for a framework to organize/parse feedback.

Yeah, this was just something I tossed together randomly without much thought; if it ends up not working with however the repository is ultimately organized, it can be tossed.

[JosephTLyons]

This issue should be auto-generating now, every 12 hours UTC (the cron scheduler can't be set to any timezone specifically). I also set it to rebuild after issues close. Feel free to change the triggers, cron schedule, or timezones in the script to your liking.

[JosephTLyons]

I'm thinking it might make sense to remove comments from the sorting mechanism. With likes, users can only add one, and no one can change the creation datetime, but anyone can comment multiple times to boost the issue up (to the top of the group of issues with the same number of likes). I'm thinking just likes and creation datetime is enough to stabilize the sort and prevent others from artificially boosting an issue's importance. It also might help to reduce some of the noise in this issue. Let me know what you think about this.

As a note, I did experiment with having the script generate a table, to reduce the amount of repeated emojis showing, but GitHub does not render the dynamic issue links (the ones that show the name of the issue and whether its closed or open) inside of markdown tables, so that idea was tossed.

[jamesmunns]

Hey there! Apologies if this is off-topic, is there somewhere I can 👍 linux support as a blocking issue? I do have a Mac, but don't use it as a primary development machine, which means that I probably won't have a chance to test out Zed until there is some kind of Linux client.

I can open an issue, but it seems explicitly documented that is a WIP feature :)

[JosephTLyons]

Hey there! Apologies if this is off-topic, is there somewhere I can 👍 linux support as a blocking issue? I do have a Mac, but don't use it as a primary development machine, which means that I probably won't have a chance to test out Zed until there is some kind of Linux client.

I can open an issue, but it seems explicitly documented that is a WIP feature :)

Sure, I went ahead and made a meta issue here:

• https://github.com/zed-industries/feedback/issues/174