Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Autocompletion order is a bit meh #680

Closed

Description

Here's an example where I have to type way more than I expect.

screen shot 2016-12-04 at 22 21 37

screen shot 2016-12-04 at 22 21 51

screen shot 2016-12-04 at 22 22 04

All choices are very bad; I have to type "constr" to match "constraints", when I should only need to type "c" to get it as the first hit.

In short, the autocompletion should emphasize near things (local variables/arguments, nearby functions, and so on), over farther-away things (like imports and snippets). I think character distance is as important a clue as lexical-scope distance.

I've also noticed that the autocompletion is peculiarly picky about case. Notice how "Constraint" (capitalized) is not among any of the hits. It's nice that case is used as a hint, but I really expect "Constraint" to be the second suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions