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
Tag search in ctrlp-py-matcher #43
Comments
Hi @alphaCTzo7G , I am not 100% if it's possible to fix that by configuration change but I didn't used CtrlPTag with this plugin at all. I think it might require an update to support this. Currently I am not using vim anymore for a long time, so I will not promise you to implement this. Sorry! |
@FelikZ .. thanks for your help.. Actually I found that For some reason, if I have a certain set of characteristics of my repo:
I will try to figure out why this is so.. |
In general I was able to create a small test.. Seems like the problem happens only when there are certain libraries like I created a small test repo here: https://github.com/alphaCTzo7G/test to reproduce the problem.. |
@FelikZ , I figured out the root cause.. It because It seems that @ludovicchabant also faced the same issue and had to modify https://github.com/ludovicchabant/vim-gutentags to handle the issue: https://ludovic.chabant.com/devblog/2017/02/25/aaa-gamedev-with-vim/ His modification of ctrlp-py-matcher is here: https://github.com/ludovicchabant/ctrlp-py-matcher/blob/2f6947480203b734b069e5d9f69ba440db6b4698/autoload/pymatcher.py#L22, but it doesn't solve the issue.. just tells you want happened. Its not possible to get any From this line, it seems that I wonder if you know of any other way to evaluate a variable in the |
None that I know. The only thing that comes to the mind, maybe its possible to convert BOM to non-BOM before eval takes place? |
@FelikZ.. actually I was wrong.. it turns out that different files had different problems @b4n has rectified this issue in this PR: universal-ctags/ctags#1807 There are other files which break Perhaps there should be a warning that because of this limitation, users should use the PR from here: universal-ctags/ctags#1807, otherwise Excuberant-ctags upon which |
The problem with |
@alphaCTzo7G However, after all me saying uctags doesn't handle encoding conversion, it actually partly does if you tell it to though the At any rate, you should probably find a way for invalid UTF-8 not to break your software, because it's unfortunately unlikely to be "fixed" anytime soon, and it's a fairly common thing (in most cases it'll be because the source was |
Appreciate your advice.. the |
@alphaCTzo7G I found a similar situation when work on a specific project. And I finally found that it is because the |
@FelikZ ,
thanks for creating this plugin.. it really sped up the file/MRU search.
However, when I tried to search tags, it didn't really show any tags.
I added the following line:
let g:ctrlp_match_func = { 'match': 'pymatcher#PyMatch' }
to my
.vimrc
, and it led to fast fuzzy searching for files. However, when I tried to search tags using:CtrlPTag
, with a tagDatabase
from one of my files, it gave no results.Then I commented out
let g:ctrlp_match_func = { 'match': 'pymatcher#PyMatch' }
, and did:CtrlPTag
with a tagDatabase
from one of my files. This time, it was slow to find that tag, but it did fine the tag.Is there any additional settings I should use to enable tag search using this plugin?
The text was updated successfully, but these errors were encountered: