> likelycomplete seems to think that "" is not a real file type,
> which is unfortunate as it's what I'm in half the time.
If you're writing prose, I'd suggest to set ft to "text" or something similar. (Or use markdown markup.)
> The parameters are all global but my language and abbreviations
> settings are per window which makes interfacing the two
> difficult.
It's possible to override &filetype by setting b:likelycomplete_filetype. I guess I could add w:likelycomplete_filetype (a window specific variable), which would help solving your problem.
> Fuzzy matching has a perceptible delay, even with a small
> dictionary (13_000 words, 100 kB)
That's possible. :-) I should probably add a quick ranking mode. By default, likelycomplete remembers the words you write most frequently.
I guess adding
let g:likelycomplete#match_beginning = 1
should improve the situation. By default it also takes into account middle-of-word matches.
I think we should continue the situation off list. If you want you could also file issues at https://github.com/tomtom/likelycomplete_vim/issues
Regards,
Tom
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sunday, March 23, 2014
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment