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

New command completion: be case insensitive #794

Closed
kiryph opened this issue Apr 17, 2017 · 3 comments
Closed

New command completion: be case insensitive #794

kiryph opened this issue Apr 17, 2017 · 3 comments

Comments

@kiryph
Copy link
Contributor

kiryph commented Apr 17, 2017

My original dictionary completion example for $\right showed also the candidates \Rightarrow and \Rrightarrow which is not the case right now. I can get the uppercase variant when I already use the upper leading R.

IMHO this is helpful to see variants you might be interested in.

Another issue is that I do not see \Rrightarrow even though I added the package amssymb and the file amssymb with the correct entry exists.

\documentclass{article}
\usepackage{amssymb}

\begin{document}
\R
\end{document}

Pressing <Leader>li does not list any packages.

@lervag lervag closed this as completed in c6967b0 Apr 17, 2017
lervag added a commit that referenced this issue Apr 17, 2017
@lervag
Copy link
Owner

lervag commented Apr 17, 2017

The first part: If \right should include \Rright, then the regex filter can not be anchored. I anchored it after one of your comments, because it seems natural that one starts to type the start of a command. However, I agree that we can make the filter case insensitive.

The second issue is a separate issue. However, I can't reproduce it. That is, it works as expected for me. Note that the list of packages is only parsed when initializing.

@kiryph
Copy link
Contributor Author

kiryph commented Apr 17, 2017

Sorry, the second issue was again an outdated neocomplete menu. Pressing ctrl-x ctrl-o revealed all the candidates.

Update
Adding to my vimrc let g:neocomplete#enable_refresh_always=1 (default 0 which means off), updates the menu always (with screen flickering) and I see all possible entries. I am not sure whether I keep this setting due to the flickering.

@lervag
Copy link
Owner

lervag commented Apr 17, 2017

Ah, yes. Neocomplete does not work perfectly when there are very many completion candidates. The refresh_always option works, as you say, but I keep it off for the same reason you mention.

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