zed-industries / zed

Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
https://zed.dev
Other
47.6k stars 2.78k forks source link

Autocomplete completions are cut in half #8126

Open Belluxx opened 7 months ago

Belluxx commented 7 months ago

Check for existing issues

Describe the bug / provide steps to reproduce it

Description: the entries of the auto-completion dialog are often cut in half. Steps to reproduce: write a piece of code and wait for the autocompletions to appear. You will see that initially the text is not cut in half but after some milliseconds the right-side type-predictions (in grey color) appear overlapping the left side.

Environment

OS: MacOS 14.3.1 (23D60) SoC: M1 8GB Zed version: 0.122.2

If applicable, add mockups / screenshots to help explain present your vision of the feature

issue

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.

No response

Belluxx commented 7 months ago

I confirm that the issue is still there in v0.123.4

effdotsh commented 7 months ago

Confirmed this is still happening on 1.24.2 preview, I'll take a crack at it tonight.

effdotsh commented 7 months ago

The delay before the right half entering is dictated by completion_documentation_secondary_query_debounce, which is set to 300ms by default. My experience was much smoother when I set it to 0. Is there a solid justification for this being a non-zero value by default?

For the cut-off text, I'm planning on just adding ellipses when it gets truncated, like how vscode does it:

image
Belluxx commented 7 months ago

@effdotsh Thank you for providing a fix so quickly

github-actions[bot] commented 3 days ago

Hi there! 👋 We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. Are you able to reproduce this issue in the latest version of Zed? If so, please let us know by commenting on this issue and we will keep it open; otherwise, we'll close it in a week. Feel free to open a new issue if you're seeing this message after the issue has been closed. Thanks for your help!

evtn commented 2 days ago

this is still an issue for me on Linux

Belluxx commented 2 days ago

Still an issue on MacOS in v0.153.7