Skip to content
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

Add option to truncate long completions #261

Merged
merged 1 commit into from
Mar 27, 2021
Merged

Conversation

tau-dev
Copy link
Contributor

@tau-dev tau-dev commented Mar 27, 2021

The detail entries for big structs such as std.zig.CrossTarget were bricking the preview window in Sublime Text.

I needed to increase the EvalBranchQuota of the json parser to add this option even though it is just a single integer. Maybe we should evaluate the build time impact of adding config options and consider alternatives (TOML?)

The detail entries for big structs such as std.zig.CrossTarget were
bricking the preview window in Sublime Text.
@alexnask
Copy link
Member

Looks good
Maybe we could use zzz, I quite like the syntax and it looks like the codebase should work at comptime, I will evaluate the effect on the compile times/branch quota.

@alexnask alexnask merged commit c063ca4 into zigtools:master Mar 27, 2021
Techatrix added a commit that referenced this pull request Sep 25, 2023
`enable_import_embedfile_argument_completions` existed because this
option has been buggy in the past but not anymore.

`include_at_in_builtins` is a workaround for builtin completions in
sublime text 3 which can instead be detected by
inspecting the clientInfo in initialize request.

`max_detail_length` is a workaround for long completion detail entries
bricking the preview window in Sublime Text #261 which can also
detected through the clientInfo field.

`operator_completions` this option has been added when
this feature was implemented but is there anyone who needs it?
Techatrix added a commit that referenced this pull request Sep 25, 2023
`enable_import_embedfile_argument_completions` existed because this
option has been buggy in the past but not anymore.

`include_at_in_builtins` is a workaround for builtin completions in
sublime text 3 which can instead be detected by
inspecting the `clientInfo` field in initialize request.

`max_detail_length` is a workaround for long completion detail entries
bricking the preview window in Sublime Text #261 which can also be 
detected through the `clientInfo` field.

`operator_completions` this option has been added when
this feature was implemented but is there anyone who needs it?
Techatrix added a commit that referenced this pull request Sep 25, 2023
`enable_import_embedfile_argument_completions` existed because this
option has been buggy in the past but not anymore.

`include_at_in_builtins` is a workaround for builtin completions in
sublime text 3 which can instead be detected by
inspecting the `clientInfo` field in initialize request.

`max_detail_length` is a workaround for long completion detail entries
bricking the preview window in Sublime Text #261 which can also be
detected through the `clientInfo` field.

`operator_completions` this option has been added when
this feature was implemented but is there anyone who needs it?
SuperAuguste pushed a commit that referenced this pull request Oct 1, 2023
`enable_import_embedfile_argument_completions` existed because this
option has been buggy in the past but not anymore.

`include_at_in_builtins` is a workaround for builtin completions in
sublime text 3 which can instead be detected by
inspecting the `clientInfo` field in initialize request.

`max_detail_length` is a workaround for long completion detail entries
bricking the preview window in Sublime Text #261 which can also be
detected through the `clientInfo` field.

`operator_completions` this option has been added when
this feature was implemented but is there anyone who needs it?
KoltPenny pushed a commit to KoltPenny/zls that referenced this pull request Oct 18, 2023
`enable_import_embedfile_argument_completions` existed because this
option has been buggy in the past but not anymore.

`include_at_in_builtins` is a workaround for builtin completions in
sublime text 3 which can instead be detected by
inspecting the `clientInfo` field in initialize request.

`max_detail_length` is a workaround for long completion detail entries
bricking the preview window in Sublime Text zigtools#261 which can also be
detected through the `clientInfo` field.

`operator_completions` this option has been added when
this feature was implemented but is there anyone who needs it?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants