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

MRU order messed up #15

Closed
Droggelbecher opened this issue Jan 26, 2016 · 4 comments
Closed

MRU order messed up #15

Droggelbecher opened this issue Jan 26, 2016 · 4 comments

Comments

@Droggelbecher
Copy link

The default matcher gives me the most recently used file as first suggestion, then the second most recentely used etc... (given, I didn't type anything yet).
That makes it possible to cycle through most recently used files with ctrl-j/ctrl-k.
I've gotten pretty used to that behaviour as it allows me to quickly change between the few most recently used files.
Any chance to see cpsm support this as well? (Alternatively: Is there a way to tell CtrlP to use a different matcher for the MRU list?)

@nixprime
Copy link
Owner

I've added a new setting g:cpsm_match_empty_query, which you can set to 0 to prevent cpsm from rearranging items for empty queries; however, this will affect non-MRU mode as well, because CtrlP doesn't inform the matcher whether or not it's in MRU mode. If you want to keep cpsm's behavior for empty queries in non-MRU mode, this can be done with a binding that toggles the value of this setting (see README for an example).

@Droggelbecher
Copy link
Author

Works nicely for MRU, thanks for the blazingly fast reaction 👍 :)

However for non-MRU mode I now get " ERROR: function takes at most 10 arguments (11 given)" as soon as I type the first character.

@nixprime
Copy link
Owner

Another recent commit changed the Python extension, so you have to rebuild it by redoing step 2 in the installation instructions. Sorry for the inconvenience.

@Droggelbecher
Copy link
Author

Oh no problem, sorry for not noticing that myself :)

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

No branches or pull requests

2 participants