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.

Sign up for GitHub

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

Jump to bottom

Per-user settings #48

Closed
ghost opened this issue Feb 16, 2014 · 1 comment
Closed

Per-user settings #48

ghost opened this issue Feb 16, 2014 · 1 comment
Labels
bug imported

Comments

@ghost
Copy link

ghost commented Feb 16, 2014

From mr.King.Midas on August 27, 2012 14:56:59

Can you add per-user settings ?
Or may be "history" ?

Original issue: http://code.google.com/p/clink/issues/detail?id=49
@ghost
Copy link
Author

ghost commented Feb 16, 2014

From martin.r...@gmail.com on September 28, 2012 16:16:20

In 0.2 I have changed clink to save state per-user rather than using the "all users" profile. This is more reliable across all versions of Windows.

Status: Fixed
Owner: martin.r...@gmail.com

@ghost ghost closed this as completed Feb 16, 2014
fulbertus pushed a commit to fulbertus/clink that referenced this issue Jan 26, 2023
@chrisant996
Fix mridgers#48; menu-complete gets stuck
390d744 
`menu-complete` gets stuck when new match dir is same length as previous
match dir.  The regression was introduced as part of the
`match_pipeline` in the v1.0.0 rewrite.  It only considered the word
offset/length and didn't examine the word content.  So it didn't
consider `clink\lib\` different from `clink\lua\`.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug imported
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants