Top-Ranking Issues (All Time) 📊

[JosephTLyons]

Updated on 06/07/2024 08:14 AM (EDT)

enhancement

1. Build and Debug support #5065 (672 👍)
2. Add a diff view #4523 (631 👍)
3. GitHub Copilot Chat Support #4673 (412 👍)
4. Rainbow brackets #5259 (387 👍)
5. Codeium support #4726 (383 👍)
6. Add support for "remote development" #5347 (347 👍)
7. EditorConfig #8534 (280 👍)
8. Minimap #5308 (249 👍)
9. Jupyter Notebook #5273 (238 👍)
10. Source control view panel #4367 (231 👍)
11. Add the possibility to use offline models (maybe via ollama) #4424 (219 👍)
12. Helix keymap #4642 (188 👍)
13. Test runner integration #5242 (188 👍)
14. CoPilot should be decoupled from zed #6708 (140 👍)
15. Pin to code structure while scrolling (aka "sticky scroll") #5344 (125 👍)
16. Icon extensions #8843 (118 👍)
17. add ability to show errors inline like VS Code(error lens) #4901 (98 👍)
18. Language server agnostic snippets #4611 (94 👍)
19. Code runner #5141 (92 👍)
20. Option to combine the tabs-bar into the titlebar #5066 (89 👍)

design

1. Rainbow brackets #5259 (387 👍)
2. Add support for "remote development" #5347 (347 👍)
3. Minimap #5308 (249 👍)
4. Jupyter Notebook #5273 (238 👍)
5. Test runner integration #5242 (188 👍)
6. Pin to code structure while scrolling (aka "sticky scroll") #5344 (125 👍)
7. Option to combine the tabs-bar into the titlebar #5066 (89 👍)
8. Semantic highlighting #5345 (75 👍)
9. Code completion icons #4943 (39 👍)
10. Render markdown in comments/doc comments #5313 (36 👍)
11. Reduce the height of toolbar or allow moving/disabling #5241 (33 👍)
12. Keybinding UI editor #5328 (32 👍)
13. Dark theme contrast #5334 (28 👍)
14. Ability to see collapsed / files containing search #4925 (20 👍)
15. The error underline looks bad #7436 (13 👍)
16. Allow "Diagnostic" panel to only show current file #4739 (12 👍)
17. Zed to embed other apps' windows #5310 (11 👍)
18. Request for a more native looking title bar on macOS under fullscreen #9730 (9 👍)
19. Line number gutter width control #7334 (7 👍)
20. Add project menu #5357 (5 👍)

ai

1. GitHub Copilot Chat Support #4673 (412 👍)
2. Codeium support #4726 (383 👍)
3. Add the possibility to use offline models (maybe via ollama) #4424 (219 👍)
4. CoPilot should be decoupled from zed #6708 (140 👍)
5. Add support for Supermaven #10013 (59 👍)
6. Add build time options to disable ML/AI features #6756 (47 👍)
7. Add support for Tabnine #4504 (38 👍)
8. Support for Gemini Pro API Key #4299 (37 👍)
9. Support Sourcegraph's Cody #4536 (35 👍)
10. Implement Groq or OS models for Assistant Tab (settings.assistant) #11075 (26 👍)
11. Support code completion with Tabby #4421 (23 👍)
12. custom assistant instructions #10040 (10 👍)
13. Codestral (Mistral code suggestion) #12519 (9 👍)
14. Cursor-like Code Edit #9320 (8 👍)
15. Add Configuration Option for Custom OpenAI Server URL #10716 (8 👍)
16. Update GPT-4 Assistant Version #7038 (7 👍)
17. [Assistant] add custom_model parameter #11984 (7 👍)
18. 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 (7 👍)
19. Hint conflicted with copilot #6967 (4 👍)
20. Inline Assistant change default model #4486 (4 👍)

defect

1. Items in .gitignoreshould still be searchable via file finder #4745 (31 👍)
2. Discrete GPU activated on launch #5124 (29 👍)
3. Comment shortcut is not correct in JSX #5291 (28 👍)
4. Project panel horizontal scroll #7001 (27 👍)
5. Hard Tabs Not Working #7656 (25 👍)
6. Zed downloads NodeJS binary and npm packages from Internet without user’s consent #12589 (25 👍)
7. Suggest autocomplete options immediately after inserting a period #8766 (24 👍)
8. Support user's default shell #5320 (23 👍)
9. LSP does not work for nested projects #4574 (21 👍)
10. Auto-indent causes issues with YAML files #9441 (19 👍)
11. Font rendering on LoDPI displays #7992 (18 👍)
12. [Zed Preview] Elixir language server - failed to deserialize latest release #4445 (15 👍)
13. PHP intelephense lsp setting not working! #4258 (14 👍)
14. The error underline looks bad #7436 (13 👍)
15. GPUI overdraws too much #8043 (13 👍)
16. Golang import error persists until editor restarted #5112 (12 👍)
17. tree view is unusably slow on a large monorepo #8242 (11 👍)
18. Problem with Function Keys on Keyboard 65% [67-keys] #4435 (10 👍)
19. Occasional undefined error when formatting a TypeScript file #11189 (9 👍)
20. Cannot install gopls when Go is not in the default env path #5318 (9 👍)

vim

1. easymotion vim #4930 (68 👍)
2. vim-mode support for marks #5122 (45 👍)
3. Which-Key like menu #10910 (38 👍)
4. Vim mode: add :s/search/replace command #9428 (20 👍)
5. vim record #4448 (19 👍)
6. vimrc support #4456 (18 👍)
7. Vim Mode - Fold/Unfold using za #6822 (17 👍)
8. vim Command %s replace preview #4411 (17 👍)
9. Change vim leader mapping #4375 (16 👍)
10. Vim: Macros #1506 (13 👍)
11. vim mode: support gf command #4501 (12 👍)
12. Vi mode: support something like yank/cut/delete around class/function, or yank/cut/delete inside class/function #4320 (12 👍)
13. vim: Allow alactritty vim mode #7417 (10 👍)
14. vim-mode: support count and scrolloff with H/M/L #4941 (9 👍)
15. Add a mark / select mode #8580 (8 👍)
16. Ctrl + ^ (Ctrl + 6) doesn't toggle between alternate files #7709 (7 👍)
17. Zed should exit vim visual mode after cmd-/ #4439 (7 👍)
18. impl "most" gitsigns.nvim functionality #6780 (6 👍)
19. Vim Dock Navigation Keybinds Not Working As Expected #8280 (6 👍)
20. Vim Mode - Visual Selection Inconsistencies #6900 (4 👍)

linux

1. [linux] Vulkan ERROR_INITIALIZATION_FAILED #8168 (9 👍)
2. Linux: When using X11, Zed will freeze the entire DE every now and then #9448 (6 👍)
3. linux: unwrap() on 'Invalid keystroke cmd-shift-[', crashes at startup. #10382 (6 👍)
4. Cannot open new project from Zed #11089 (6 👍)
5. auto_update fails on deserializing release step #11114 (5 👍)
6. Does Zed work with Darling? #7012 (4 👍)
7. blade: Outline rendering for 1 pixel borders is not being rasterized properly #11056 (4 👍)
8. linux: Only one instance of zed can run at a time after recent commit #11770 (4 👍)
9. Sprite atlas bleeding with blade renderer #12352 (4 👍)
10. can we have this app in flathub and snapstore #9922 (3 👍)
11. linux: Window flickering when resizing after recent commit #11469 (3 👍)
12. Vim mode: Difficulties attempting to rename a symbol #11882 (3 👍)
13. error: failed to run custom build command for openssl-sys v0.9.93 #11953 (3 👍)
14. Provide a prebuilt aarch64-linux build #12608 (3 👍)
15. Linux: Middle mouse button paste does not work in editor #12691 (3 👍)
16. dnf dependencies in script/linux seem to be missing c++ #8622 (2 👍)
17. Pressing escape should dismiss the "do you want to save" prompt #9203 (2 👍)
18. [linux] fs: Too many open files #10310 (2 👍)
19. Only some ligatures are being applied #12176 (2 👍)
20. Rendering of right border is missing for some tabs with custom ui_font_size #11549 (1 👍)

windows

1. [Windows] Failing to read settings file #9316 (5 👍)
2. auto-update not supported for OS "windows" #11753 (5 👍)
3. panic: ERROR_OUT_OF_POOL_MEMORY on Windows #10018 (4 👍)
4. Windows: Worktree ignoring events due to invalid canonical path #9535 (3 👍)
5. [Windows] Scrolling upwards causes Zed to click window X button and close #12369 (3 👍)
6. [Windows] Zed not running in debug and release both builds #9251 (2 👍)
7. Windows: Crash when selecting empty row #10864 (2 👍)
8. Windows: how can i show the main menu. #10919 (2 👍)
9. can't be compiled with ld from msys2/mingw #11040 (2 👍)
10. [WINDOWS] Most LSPs give error: "Cannot read LSP message header" #12013 (2 👍)
11. serious memory leak issue on windows10 after commit  #12561 (2 👍)
12. ( Windows )Zed successfully compiled, but cannot run #11864 (1 👍)
13. [Windows] Theme importer incompatible with windows #12079 (1 👍)
14. tsx language disappear after selecting it in windows #12208 (1 👍)
15. Bundle as MSI installer on windows #12288 (1 👍)
16. [gpui] [Windows]Two issues make GPUI hello world demo panic on Window 10/11 #9540 (0 👍)
17. Windows: SIGSEGV while startup in msys2/clang64 #10522 (0 👍)
18. add target information into system specs (at least for Windows) #11649 (0 👍)
19. windows: work zed with Zed rust-analyzer with hang windows unresponse some seconds #11978 (0 👍)
20. error when running program on windows 11 #12032 (0 👍)

panic / crash

1. linux: unwrap() on 'Invalid keystroke cmd-shift-[', crashes at startup. #10382 (6 👍)
2. auto-update not supported for OS "windows" #11753 (5 👍)
3. Crash when joining channel on macOS Catalina/BigSur #5384 (4 👍)
4. panic: ERROR_OUT_OF_POOL_MEMORY on Windows #10018 (4 👍)
5. New install of Zed will not Launch #9805 (3 👍)
6. [Windows] Zed not running in debug and release both builds #9251 (2 👍)
7. [linux] fs: Too many open files #10310 (2 👍)
8. Windows: Crash when selecting empty row #10864 (2 👍)
9. Cannot open Zed #9711 (1 👍)
10. It crashed when making large amount of replace using cmd + F #11464 (1 👍)
11. ( Windows )Zed successfully compiled, but cannot run #11864 (1 👍)
12. Zed unable to open GUI failed to retrieve next drawable #12551 (1 👍)
13. crashes on linux with vulkan-nouveau #12696 (1 👍)
14. Linux: Going to a different TTY causes Zed to panic. #9154 (0 👍)
15. Exception INVALID_OPTIONS on mach port 0 (guarded with 0x0000000000000000) #9261 (0 👍)
16. error: rustc interrupted by SIGSEGV, printing backtrace #9432 (0 👍)
17. GPUI image crash #10029 (0 👍)
18. Windows: SIGSEGV while startup in msys2/clang64 #10522 (0 👍)
19. Zed crashes when sshfs containing a git repo is unmounted #10992 (0 👍)
20. "assertion failed: payload_size <= max_payload_size" on restart + upgrade is pending #4591 (0 👍)

documentation

1. Unable to drag file to dock #4665 (3 👍)
2. Mention theme auto-switching in default settings #9627 (2 👍)
3. Documentation about how it works the collaboration feature between computers #8260 (1 👍)
4. Docs bug "Adding New Languages" page doesn't say how to add a new language #9732 (1 👍)
5. Document required OpenAI API key permissions #11901 (1 👍)
6. Strange editor area when showing plain text content #12473 (1 👍)
7. Tree Sitter queries documentation #8379 (0 👍)
8. zed.dev/features#language_servers 'and more' link is a 404 #9011 (0 👍)
9. Information about commands when no file is open #11957 (0 👍)
10. Add scroll cursor {top,center,bottom} actions to Default Key Bindings #5075 (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