-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggest autocomplete options immediately after inserting a period #8766
Comments
I'm working in a TS codebase and the behaviour I'm seeing is the suggestion popover appears after showing the intent of accessing a property: inserting a period. The only time it doesn't pop up is when some code is suggested by Copilot. zed-popover-intent.mp4 |
@Moshyfawn, do you have any particular configuration? I haven't changed anything, it is the default installation. Thank you. |
This has been the case with every configuration I've tried. My current settings are as follows: {
"theme": "Rosé Pine",
"ui_font_size": 14,
"buffer_font_size": 14,
"tab_size": 2,
"show_wrap_guides": true,
"format_on_save": "language_server",
"scrollbar": {
"git_diff": false
},
"git": {
"git_gutter": "tracked_files"
}
} |
I believe the difference in the behavior you're seeing is due to corresponding language server's Here are the only places in Zed codebase we register those trigger characters: zed/crates/project/src/project.rs Lines 2086 to 2096 in 7ad7143
zed/crates/project/src/project.rs Lines 3342 to 3352 in 7ad7143
So, while Zed can add some heuristics to trigger more completions, a more appropriate fix seems to belong to corresponding language servers. |
Hm, the problem is: seems that all 3 mentioned servers do have
So maybe it's Zed's issue, after all: but still, to debug this, one would need to find a case where it reproduces reliably, then
|
PS. I do not have Copilot, but when I had, I had the same behavior. |
I would really appreciate if somebody can provide the issue with an open source project and the repro steps; or, alternatively if somebody could debug those things locally in the places mentioned above and add more context. |
I can provide tomorrow. It basically does not work in any project to me.I do not have anything on my config and I have installed using homebrew.On 3 Mar 2024, at 14:49, Kirill Bulatov ***@***.***> wrote:
I would really appreciate if somebody can provide the issue with an open source project and the repro steps; or, alternatively if somebody could debug those things locally in the places mentioned above and add more context.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I use asdf to install the languages that I want use, in this case, NodeJS 18.x The exactly same setup works for VSCode. |
Sometimes works as expected, other no. I have no idea…
|
Experiencing the same exact issue here with my TypeScript project. I absolutely need an autocomplete list after pressing Edit: I restarted Zed and now it's working after pressing period? Seems inconsistent. Also worth noting that when I try to autocomplete a method, I'm not getting Back to using WebStorm for now. |
I'm experiencing an issue with autocompletion when Copilot is enabled. Most of the time I see a list of suggested symbols immediately after inserting a period. Sometimes, there's an issue where this list doesn't appear and I have to delete and retype the previous word to get the list to show again. It seems to be a conflict with the autocompletion suggested by Copilot. I can confirm that disabling Copilot resolves this. Copilot enabledScreen.Recording.2024-04-23.at.22.53.16.movCopilot disabledScreen.Recording.2024-04-23.at.22.57.59.movI compared with the behaviour of Copilot in VSCode and it hides Copilot suggestions unless the autocomplete list is closed (like with Esc). |
Can confirm that his worked for me with Typescript :) |
It not worked for me. |
I do not understand why this issue was closed; it is not working as expected. |
@klaemo can you provide us your settings.json |
I did this, restarted and had same issue. My settings have nothing. |
I tried and it works. I deleted pyright folder in the location you kindly wrote and it works. But it works only for a few time. It suddenly doesn't work after a couple of minutes or when I close and reopen the app. I'm on zed Zed 0.147.2. {
"theme": "One Dark Vivid",
"ui_font_size": 16,
"buffer_font_size": 13,
"show_wrap_guides": true,
"lsp": {
"ruff": {
"initialization_options": {
"settings": {
"lineLength": 80,
"lint": {
"extendSelect": ["I"]
}
}
}
}
},
"languages": {
"Python": {
"format_on_save": "on",
"formatter": [
{
"code_actions": {
"source.organizeImports.ruff": true,
"source.fixAll.ruff": true
}
},
{
"language_server": {
"name": "ruff"
}
}
]
}
},
"show_completions_on_input": true,
"show_inline_completions": true,
"indent_guides": {
"enabled": true,
"line_width": 1,
"active_line_width": 1,
"coloring": "fixed",
"background_coloring": "indent_aware"
},
"current_line_highlight": "gutter",
"git": {
"git_gutter": "tracked_files",
"inline_blame": {
"enabled": true
}
},
"terminal": {
"font_family": "MesloLGS NF"
},
"cursor_blink": true,
"vim_mode": true
} I think it is a bug of the app. I write a script that each time I close Zed, it delete the pyright folder. In this way it works. Please fix this issue because in this way the editor isn't very useful, unless I execute my script. |
Just in case this helps anyone, I got around this issue by using TypeScript Language Server instead of Vtsls. Maybe the issue is with vtsls? settings.json {
"languages": {
"TypeScript": {
"show_inline_completions": true,
"language_servers": ["typescript-language-server", "!vtsls"]
}
},
...
} |
Experiencing same issue on Windows in TypeScript project. Version of Zed is 0.511.0. |
Having the same issue:
Video can be found in this post: #17260 (comment) |
Having the same problem with Python and Pyright
|
Deleting |
example.movThis worked for me too. But it does seem to result in duplicate suggestions |
I am also a bit disappointed that I do not have autocompletion suggestions, which is something I expect almost in any editing field. Can it be enabled? It really helps writing in LaTeX. |
Ok, I waw able to enable the autocompletions, but it is SLOW. It usually takes some time before the popup appears. How to make it faster? |
Still experiencing these issues with Rust. Tried deleting rust-analyzer but no success |
@eatenpancreas try to remove rust-analyzer from $HOME/.cargo/bin, it helps for me btw, why zed prefers lsp from .cargo? I can’t find this in docs |
i tried this, and about 3 hours later it went back to not suggesting anything after inserting a . |
I don't know what it is, but no matter what i do, everytime i restart zed it works again, and after a few hours or so it'll stop working again. Sure, i can restart zed everytime, but it's quite bothersome to do so. |
@eatenpancreas Same here. It works on restart but stops working after some time. |
This comment has been minimized.
This comment has been minimized.
This is critical bug but no one fix this |
I think I was muted by the Zed team, I have other issues totally ignored... |
I love this editor, coming from jetbrains it's leagues ahead and i'm finding the multi-buffer editing amazing, but stuff like this is very important for basic workflow. It's a bit of a dealbreaker for me and i think i will be switching until this gets resolved |
Tested on Zed Preview release (0.162.1) on a large Typescript project and it seems to be fixed too! ✅ Previously it stopped working when closing or opening a new file, now it continues to work through multiple files. Thanks @osiewicz |
I've been testing the preview out ever since @tdjlkk suggested using it and i haven't had the issue re-appear inside Rust. I'm not sure how that could've caused it but i'm very glad that it seems to be fixed |
Check for existing issues
Describe the feature
As can be seen in the images below, the autocomplete only offers me suggestions after I insert a period, and this happens in any language I use daily (Go, Python & TypeScript).
This is quite annoying because it forces you to either read the documentation or start guessing the possible first letters of what you want.
My question is, is there a way to improve this? I come from using VSCode, and there it works 'as expected,' so why is it different in Zed?
In my opinion, this behavior in Zed is not productive.
After pressing period, nothing happens.
Since I know the name of the attribute, I press L and only at that moment does it suggest what I want.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
The text was updated successfully, but these errors were encountered: