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

Smart case matching #1158

Open
sharpchen opened this issue Feb 5, 2025 · 2 comments
Open

Smart case matching #1158

sharpchen opened this issue Feb 5, 2025 · 2 comments
Labels
feature New feature or request

Comments

@sharpchen
Copy link

Feature Description

Requesting a feature that prioritize casing when any captial character were typed.

This feature might help in the following scenario:

  • a user prefers snippet over lsp when typing a keyword, such as if~ snippet is prefered over if keyword. So the user might have such config:
providers = {
  snippets = {
    min_keyword_length = 2,
    score_offset = 3,
    should_show_items = function(ctx)
      return ctx.trigger.initial_kind ~= 'trigger_character'
    end,
  },
  lsp = {
    min_keyword_length = 1,
    score_offset = 3,
  },
}
  • such config has problem when working scenarios like in the following gif

    There's a lot of snippets starts with parameter, and the expected item is ParameterAttribute from lsp. The item was pushed out of the visible list because blink ignored the casing. If blink could support smart-case to prioritize the exact case when any capital is typed, it should help to solve such problem.

Image

@sharpchen sharpchen added the feature New feature or request label Feb 5, 2025
@Saghen
Copy link
Owner

Saghen commented Feb 5, 2025

Do you still run into this issue with fuzzy.use_frecency = false and fuzzy.use_proximity = false?

@sharpchen
Copy link
Author

Yep

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants