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

omni-compl: start completion in a full keyword #4187

Closed

Conversation

benknoble
Copy link
Contributor

The default omni_start_map is too restrictive for Lisps and Schemes
like Racket, which permit hyphens (among other special characters).

As recorded in #3870, trying to complete file-name-from-path when
typing file-name<C-x><C-o> would give completions like namespace
because the hyphen is ignored to find the start of the word for
completion.

Now the default searches for the start using the keyword class
\k, which is more precise and configurable for each filetype without
modifying the source.

The default `omni_start_map` is too restrictive for Lisps and Schemes
like Racket, which permit hyphens (among other special characters).

As recorded in dense-analysis#3870, trying to complete `file-name-from-path` when
typing `file-name<C-x><C-o>` would give completions like `namespace`
because the hyphen is ignored to find the start of the word for
completion.

Now the default searches for the start using the keyword class
`\k`, which is more precise and configurable for each filetype without
modifying the source.
@hsanson
Copy link
Contributor

hsanson commented Jun 23, 2022

Closed in favor of #4186

@hsanson hsanson closed this Jun 23, 2022
@benknoble benknoble deleted the use-keyword-for-omni-start branch June 23, 2022 02:32
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.

2 participants