Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

<Tab> popup selection list not appearing after 2/23/2014 (commit 43e8b9aba3...) #148

Closed
econoplas opened this Issue · 2 comments

2 participants

@econoplas

Thanks for vim-snipmate. It is truly amazing!

I started using vim-snipmate for the first time on Win32 and Linux on 2/22 when I git cloned the master vim-snipmate repository. Today I did a 'git pull' to update to the latest and now when I type something like 'da' followed by TAB key... rather than seeing the usual popup selection list containing 'date' and datetime', instead I get spaces inserted after the 'da' up to the next tab stop. So the popup selection list seemed to have stopped working.

I thought I had messed up my settings or something, so I checked my own settings. Nothing had changed.

So I went back in time and tried vim-snipmate commit 43e8b9a from 2/18/2014 and it worked as before, and then I tried commit 0631587 from 2/23/2014 and the popup selection list didn't appear.

So I reverted back to 43e8b9a and vim-snipmate is back to normal.

I thought I would report the results of my troubleshooting research in case someone else encounters this behavior.

Sorry I am not a proficient vim script programmer yet or I would attempt a fix and submit a pull request. I would probably just cause more breakage at this point.

I would be glad to help troubleshoot further to narrow down the cause of the issue or test any potential fixes as needed. Let me know.

@ajzafar ajzafar closed this issue from a commit
@ajzafar ajzafar Fix available snips completion popup
This was broken in 0631587. The code used to use the lookup trigger as
a regex, which changed partially in 0631587.

Fixes #148.
40f0efd
@ajzafar ajzafar closed this in 40f0efd
@ajzafar
Collaborator

Thanks for the comprehensive report! It should be fixed now.

@econoplas

Confirmed... ran 'git pull' and it is working well again. Thanks for the extremely quick turn-around!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.