-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Proto Extension does not use tab_size for formatting Protobuf files #20009
Comments
Do you have an |
no |
Yes i have the proto extension installed. It used to work without installing/running the proto language server manually. But not i saw that in the logs zed was complaining about not finding language server |
I updated to newest version today. The problem still exists. Additionally when i misformat the file and select formatting, it won't fix it. It does not produce any trace/log messages. I'm using language server protols |
Protols uses clang-format under the hood. Can you confirm you have I couldn't actually get protols working at all, so as a workaround I am invoking
Alternatively, you can create a |
Oh yeah then it formats, but not in the way the CI likes it. Our CI uses https://buf.build/ and i'm not able to configure it as external formatter, also it is very slow and times out. What kind of of protobuf language server do you use? i had problems using |
Ok, well i think i found a ocompatible clang-format config. Anyway it used to work and suddenly stopped working without messing with the config |
Could you paste your |
|
Check for existing issues
Describe the bug / provide steps to reproduce it
The following configuration is ignored in latest version when language server is not running:
Environment
Zed: v0.159.5 (Zed)
OS: Linux X11 ubuntu 24.04
Memory: 31.1 GiB
Architecture: x86_64
GPU: Intel(R) UHD Graphics (TGL GT1) || Intel open-source Mesa driver || Mesa 24.0.9-0ubuntu0.2
If applicable, add mockups / screenshots to help explain present your vision of the feature
Pressing tab adds 4 spaces despite 2 being configured
If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: