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

SuperTab does not seem to fall back to secondary completion #99

Closed
Onturenio opened this Issue Mar 7, 2014 · 13 comments

Comments

Projects
None yet
3 participants
@Onturenio

I'm using Supertab together with Latex-Box. My .vimrc looks like:

let g:SuperTabDefaultCompletionType = "context"
let g:SuperTabContextDefaultCompletionType = ""
let g:SuperTabCompletionContexts = ['s:ContextText', 's:ContextDiscover']
let g:SuperTabContextDiscoverDiscovery = ["&omnifunc:"]

Everything works very well when I want supertab to apply omnicompletion or file completion. However, most of the time I want it to apply , but in this situations it does not work. For example, if I write "averylongword avery" supertab tries to use omnicompletation. Since it can not do anything with this, I expect that it applies , which is the default completion type, but it does not. It just sends the error message:

"-- Omni completion (^O^N^P) Pattern not found",

and does nothing else.

Is this the expected behaviour? To me it looks like something is wrong, but I can not tell if it's just my .vimrc setup or a bug in the script.

@ervandew

This comment has been minimized.

Show comment
Hide comment
@ervandew

ervandew Mar 7, 2014

Owner

Completion chaining has to be configured. Here is the example from the docs (:help supertab-completionchaining):

autocmd FileType *
  \ if &omnifunc != '' |
  \   call SuperTabChain(&omnifunc, "<c-p>") |
  \   call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
  \ endif
Owner

ervandew commented Mar 7, 2014

Completion chaining has to be configured. Here is the example from the docs (:help supertab-completionchaining):

autocmd FileType *
  \ if &omnifunc != '' |
  \   call SuperTabChain(&omnifunc, "<c-p>") |
  \   call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
  \ endif

@ervandew ervandew closed this Mar 7, 2014

@Onturenio

This comment has been minimized.

Show comment
Hide comment
@Onturenio

Onturenio Mar 7, 2014

Sorry, but I still don't get it and the setup does not work.

I have this right now:

let g:SuperTabDefaultCompletionType = "context"
let g:SuperTabContextDefaultCompletionType = "<c-p>"
let g:SuperTabCompletionContexts = ['s:ContextText', 's:ContextDiscover']
let g:SuperTabContextDiscoverDiscovery = ["&omnifunc:<c-x><c-o>"]
autocmd FileType * 
      \if &omnifunc != '' |
      \call SuperTabChain(&omnifunc, "<c-p>") |
      \call SuperTabSetDefaultCompletionType("<c-x><c-o>") |
      \endif

I have gone carefully through the documentation (several times), and I read this code as follows: SuperTab tries to use context completion first. In particular it applies first ContextText, which will apply file completion if possible (among others that do not apply to my case). If this does not find any match, it will continue for ContextDiscover. Here, I specify that SuperTab should use omnicompletion. If this does not work, the chain shall continue, and should be triggered.

The results is that it should try to use file completion, then omnicompletion, and finally word completion. But it does not do that. Actually right now it only tries completion, ignoring any other things.

Sorry if I sound desperate, but I have really gone through the documentation and I could not figure out how to get the results I want. My hope is that this will help to improve the documentation with maybe a more illustrative example...

Sorry, but I still don't get it and the setup does not work.

I have this right now:

let g:SuperTabDefaultCompletionType = "context"
let g:SuperTabContextDefaultCompletionType = "<c-p>"
let g:SuperTabCompletionContexts = ['s:ContextText', 's:ContextDiscover']
let g:SuperTabContextDiscoverDiscovery = ["&omnifunc:<c-x><c-o>"]
autocmd FileType * 
      \if &omnifunc != '' |
      \call SuperTabChain(&omnifunc, "<c-p>") |
      \call SuperTabSetDefaultCompletionType("<c-x><c-o>") |
      \endif

I have gone carefully through the documentation (several times), and I read this code as follows: SuperTab tries to use context completion first. In particular it applies first ContextText, which will apply file completion if possible (among others that do not apply to my case). If this does not find any match, it will continue for ContextDiscover. Here, I specify that SuperTab should use omnicompletion. If this does not work, the chain shall continue, and should be triggered.

The results is that it should try to use file completion, then omnicompletion, and finally word completion. But it does not do that. Actually right now it only tries completion, ignoring any other things.

Sorry if I sound desperate, but I have really gone through the documentation and I could not figure out how to get the results I want. My hope is that this will help to improve the documentation with maybe a more illustrative example...

@ervandew

This comment has been minimized.

Show comment
Hide comment
@ervandew

ervandew Mar 7, 2014

Owner

What is the result of running: :verbose set completefunc?

Owner

ervandew commented Mar 7, 2014

What is the result of running: :verbose set completefunc?

@Onturenio

This comment has been minimized.

Show comment
Hide comment
@Onturenio

Onturenio Mar 7, 2014

As expected,

completefunc=SuperTabCodeComplete
        Last set from ~/.vim/plugin/supertab.vim

and for :verbose set omnifunc? I get

        Last set from ~/.vim/ftplugin/latex-box/mappings.vim

As expected,

completefunc=SuperTabCodeComplete
        Last set from ~/.vim/plugin/supertab.vim

and for :verbose set omnifunc? I get

        Last set from ~/.vim/ftplugin/latex-box/mappings.vim
@ervandew

This comment has been minimized.

Show comment
Hide comment
@ervandew

ervandew Mar 7, 2014

Owner

this:

autocmd FileType * 
      \if &omnifunc != '' |
      \call SuperTabChain(&omnifunc, "<c-p>") |
      \call SuperTabSetDefaultCompletionType("<c-x><c-o>") |
      \endif

needs to be changed to:

autocmd FileType * 
      \if &omnifunc != '' |
      \call SuperTabChain(&omnifunc, "<c-p>") |
      \call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
      \endif

Note the change to use <c-x><c-u> as the default completion since supertab uses user completion (completefunc) to do its chaining.

Owner

ervandew commented Mar 7, 2014

this:

autocmd FileType * 
      \if &omnifunc != '' |
      \call SuperTabChain(&omnifunc, "<c-p>") |
      \call SuperTabSetDefaultCompletionType("<c-x><c-o>") |
      \endif

needs to be changed to:

autocmd FileType * 
      \if &omnifunc != '' |
      \call SuperTabChain(&omnifunc, "<c-p>") |
      \call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
      \endif

Note the change to use <c-x><c-u> as the default completion since supertab uses user completion (completefunc) to do its chaining.

@Onturenio

This comment has been minimized.

Show comment
Hide comment
@Onturenio

Onturenio Mar 8, 2014

OK, this seems to work. The only issue is that now it does not perform file completion. It looks like the chain

file completion -> omnicompletion -> keyword completion

is not possible.

It's fine, I can live with this results. As a constructive chriticism, maybe the help could be clearer in this respect. I have gone through some closed issues and it looks like I'm not the first one having problems to understand how to tune SuperTab (see here and here).

Thank you very much for your time here and for developing this great plugin!

OK, this seems to work. The only issue is that now it does not perform file completion. It looks like the chain

file completion -> omnicompletion -> keyword completion

is not possible.

It's fine, I can live with this results. As a constructive chriticism, maybe the help could be clearer in this respect. I have gone through some closed issues and it looks like I'm not the first one having problems to understand how to tune SuperTab (see here and here).

Thank you very much for your time here and for developing this great plugin!

@ervandew

This comment has been minimized.

Show comment
Hide comment
@ervandew

ervandew Mar 15, 2014

Owner

OK, this seems to work. The only issue is that now it does not perform file completion. It looks like the chain

file completion -> omnicompletion -> keyword completion

is not possible.

Yes and no. The only completion chaining that can be supported with vim's current completion mechanism is having either user or omni completion tried, then some other completion.

However, supertab's context completion supports looking at the text before the cursor and deciding what completion method (one and only one) it should use. So you can kind of get what you want by combining context completion with completion chaining, but instead of the flow being:

file completion -> omnicompletion -> keyword completion

it would end up being:

if text before the cursor looks like a file path:
  file completion
elif text before the cursor looks like an attempt to access a member (method, field, etc):
  user completion
    where user completion is currently set to supertab's 
    completion chaining, resulting in:
      if omni completion has results:
        omni completion
      else:
        keyword completion
else:
  keyword completion

To enable that flow simply make sure you still have context set as the default completion type for supertab:

let g:SuperTabDefaultCompletionType = 'context'

So if you normally have it set to something else, but want to leverage context completion only with completion chaining then you'd have:

autocmd FileType *
  \ if &omnifunc != '' |
  \   call SuperTabChain(&omnifunc, "<c-p>") |
  \   call SuperTabSetDefaultCompletionType("context") |
  \ endif

If you alway want to have context always as the supertab default, then simply omit setting of the default type in your autocmd:

let g:SuperTabDefaultCompletionType = 'context'
autocmd FileType *
  \ if &omnifunc != '' |
  \   call SuperTabChain(&omnifunc, "<c-p>") |
  \ endif

As a constructive chriticism, maybe the help could be clearer in this respect. I have gone through some closed issues and it looks like I'm not the first one having problems to understand how to tune SuperTab (see here and here).

I agree that the docs can always use more work. I'll try to provide more examples to hopefully clear things up.

Owner

ervandew commented Mar 15, 2014

OK, this seems to work. The only issue is that now it does not perform file completion. It looks like the chain

file completion -> omnicompletion -> keyword completion

is not possible.

Yes and no. The only completion chaining that can be supported with vim's current completion mechanism is having either user or omni completion tried, then some other completion.

However, supertab's context completion supports looking at the text before the cursor and deciding what completion method (one and only one) it should use. So you can kind of get what you want by combining context completion with completion chaining, but instead of the flow being:

file completion -> omnicompletion -> keyword completion

it would end up being:

if text before the cursor looks like a file path:
  file completion
elif text before the cursor looks like an attempt to access a member (method, field, etc):
  user completion
    where user completion is currently set to supertab's 
    completion chaining, resulting in:
      if omni completion has results:
        omni completion
      else:
        keyword completion
else:
  keyword completion

To enable that flow simply make sure you still have context set as the default completion type for supertab:

let g:SuperTabDefaultCompletionType = 'context'

So if you normally have it set to something else, but want to leverage context completion only with completion chaining then you'd have:

autocmd FileType *
  \ if &omnifunc != '' |
  \   call SuperTabChain(&omnifunc, "<c-p>") |
  \   call SuperTabSetDefaultCompletionType("context") |
  \ endif

If you alway want to have context always as the supertab default, then simply omit setting of the default type in your autocmd:

let g:SuperTabDefaultCompletionType = 'context'
autocmd FileType *
  \ if &omnifunc != '' |
  \   call SuperTabChain(&omnifunc, "<c-p>") |
  \ endif

As a constructive chriticism, maybe the help could be clearer in this respect. I have gone through some closed issues and it looks like I'm not the first one having problems to understand how to tune SuperTab (see here and here).

I agree that the docs can always use more work. I'll try to provide more examples to hopefully clear things up.

@kiryph

This comment has been minimized.

Show comment
Hide comment
@kiryph

kiryph Sep 24, 2014

OK, this seems to work.

let g:SuperTabDefaultCompletionType = "context"
let g:SuperTabContextDefaultCompletionType = "<c-p>"
let g:SuperTabCompletionContexts = ['s:ContextText', 's:ContextDiscover']
let g:SuperTabContextDiscoverDiscovery = ["&omnifunc:<c-x><c-o>"]
autocmd FileType * 
      \if &omnifunc != '' |
      \call SuperTabChain(&omnifunc, "<c-p>") |
      \call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
      \endif

I cannot confirm that the chaining of completions with the current versions of supertab latex-box and vim version 7.3.547 works. latex-box completion works for \cite{ but <ctrl>-p does not step in if latex-box completion cannot complete.

Do I need a newer vim version?

:verbose set completefunc? is empty
:verbose set omnifunc? is correct

kiryph commented Sep 24, 2014

OK, this seems to work.

let g:SuperTabDefaultCompletionType = "context"
let g:SuperTabContextDefaultCompletionType = "<c-p>"
let g:SuperTabCompletionContexts = ['s:ContextText', 's:ContextDiscover']
let g:SuperTabContextDiscoverDiscovery = ["&omnifunc:<c-x><c-o>"]
autocmd FileType * 
      \if &omnifunc != '' |
      \call SuperTabChain(&omnifunc, "<c-p>") |
      \call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
      \endif

I cannot confirm that the chaining of completions with the current versions of supertab latex-box and vim version 7.3.547 works. latex-box completion works for \cite{ but <ctrl>-p does not step in if latex-box completion cannot complete.

Do I need a newer vim version?

:verbose set completefunc? is empty
:verbose set omnifunc? is correct

@kiryph

This comment has been minimized.

Show comment
Hide comment
@kiryph

kiryph Sep 24, 2014

I could narrow my problem down by echoing &omnifunc

autocmd FileType * 
      \ verbose set omnifunc? |
      \ if &omnifunc != '' |
      \ call SuperTabChain(&omnifunc, "<c-p>") |
      \ call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
      \ endif

Seems ~/.vim/ftplugin/latex-box/mappings.vim is executed after my vimrc autocommand.
How can this be solved?

I am using pathogen to load the plugins.

Running by hand the autocmd FileType via :do FileType everything is setup correctly.

kiryph commented Sep 24, 2014

I could narrow my problem down by echoing &omnifunc

autocmd FileType * 
      \ verbose set omnifunc? |
      \ if &omnifunc != '' |
      \ call SuperTabChain(&omnifunc, "<c-p>") |
      \ call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
      \ endif

Seems ~/.vim/ftplugin/latex-box/mappings.vim is executed after my vimrc autocommand.
How can this be solved?

I am using pathogen to load the plugins.

Running by hand the autocmd FileType via :do FileType everything is setup correctly.

@ervandew

This comment has been minimized.

Show comment
Hide comment
@ervandew

ervandew Nov 16, 2014

Owner

@kiryph
Sorry for the extremely late reply. If you run the command :scriptnames you can see exactly in what order things are sourced. So in your case you may need to move the autocmd definition to an ftplugin file (:h ftplugin) or to an after-directory (:h after-directory).

Owner

ervandew commented Nov 16, 2014

@kiryph
Sorry for the extremely late reply. If you run the command :scriptnames you can see exactly in what order things are sourced. So in your case you may need to move the autocmd definition to an ftplugin file (:h ftplugin) or to an after-directory (:h after-directory).

@kiryph

This comment has been minimized.

Show comment
Hide comment
@kiryph

kiryph Nov 18, 2014

@ervandew
thanks for your reply. I didn't know the command :scriptnames. Very helpful when using pathogen for plugin loading. It easily shows the load order which was the problem.

For completeness my setup:

" file: ~/.vimrc
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
"                               Plugin: Supertab                               "
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
" supertab (completefunc) + latex-box (omnifunc)
let g:SuperTabDefaultCompletionType = "context"
let g:SuperTabContextDefaultCompletionType = "<c-p>"
let g:SuperTabCompletionContexts = ['s:ContextText', 's:ContextDiscover']
let g:SuperTabContextDiscoverDiscovery = ["&omnifunc:<c-x><c-o>"]
" Problem with load order (vimrc is evaluated before latex-box setting of omnifunc)
" \ verbose set omnifunc? | " is empty
" added this autocommand to after/ftplugin/tex.vim
" :do FileType solves also the problem
autocmd FileType * 
      \ if &omnifunc != '' |
      \ call SuperTabChain(&omnifunc, "<c-p>") |
      \ call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
      \ endif
"file ~/.vim/after/ftplugin/tex.vim
if &omnifunc != '' |
\ call SuperTabChain(&omnifunc, "<c-p>") |
\ call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
\ endif

Verification of settings and load order

% within a tex file
:verbose set completefunc?`
    completefunc=SuperTabCodeComplete
        Last set from ~/.vim/bundle/56c-supertab/plugin/supertab.vim   

:verbose set omnifunc?
    omnifunc=LatexBox_Complete
        Last set from ~/.vim/bundle/23-latex-box/ftplugin/latex-box/complete.vim 

:scriptnames
:v/\v(tex)|(vimrc)|(pathogen)/delete
  1: /usr/share/vim/vimrc
  3: ~/.vimrc
  4: ~/.vim/bundle/00-pathogen/autoload/pathogen.vim
 32: ~/.vim/bundle/21-latex-suite/plugin/SyntaxFolds.vim
 33: ~/.vim/bundle/21-latex-suite/plugin/filebrowser.vim
 34: ~/.vim/bundle/21-latex-suite/plugin/imaps.vim
 35: ~/.vim/bundle/21-latex-suite/plugin/libList.vim
 36: ~/.vim/bundle/21-latex-suite/plugin/remoteOpen.vim
132: ~/.vim/bundle/21-latex-suite/ftplugin/tex_latexSuite.vim
133: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/main.vim
134: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/texrc
135: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/texproject.vim
136: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/texmenuconf.vim
137: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/envmacros.vim
138: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/wizardfuncs.vim
139: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/elementmacros.vim
140: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/mathmacros.vim
141: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/multicompile.vim
142: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/compiler.vim
143: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/folding.vim
144: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/templates.vim
145: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/custommacros.vim
146: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/bibtex.vim
147: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/brackets.vim
148: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/smartspace.vim
149: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/texviewer.vim
150: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/version.vim
151: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/packages.vim
152: ~/.vim/bundle/21-latex-suite/compiler/tex.vim
153: ~/.vim/bundle/23-latex-box/ftplugin/tex_LatexBox.vim
154: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/common.vim
155: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/complete.vim
156: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/motion.vim
157: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/latexmk.vim
158: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/folding.vim
159: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/findmain.vim
160: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/mappings.vim
162: /usr/share/vim/vim73/ftplugin/tex.vim
163: /usr/share/vim/vim73/ftplugin/plaintex.vim
164: /usr/share/vim/vim73/ftplugin/initex.vim
165: ~/.vim/after/ftplugin/tex.vim
166: ~/.vim/after/ftplugin/tex_plugins.vim
167: ~/.vim/after/ftplugin/tex_swapit.vim
168: ~/.vim/bundle/21-latex-suite/indent/tex.vim
169: ~/.vim/bundle/23-latex-box/indent/tex.vim
170: /usr/share/vim/vim73/indent/tex.vim
171: /usr/share/vim/vim73/syntax/tex.vim
172: ~/.vim/bundle/23-latex-box/after/syntax/tex.vim
173: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/packages/amsmath
174: ~/.vim/bundle/21-latex-suite/ftplugin/bib_latexSuite.vim

kiryph commented Nov 18, 2014

@ervandew
thanks for your reply. I didn't know the command :scriptnames. Very helpful when using pathogen for plugin loading. It easily shows the load order which was the problem.

For completeness my setup:

" file: ~/.vimrc
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
"                               Plugin: Supertab                               "
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
" supertab (completefunc) + latex-box (omnifunc)
let g:SuperTabDefaultCompletionType = "context"
let g:SuperTabContextDefaultCompletionType = "<c-p>"
let g:SuperTabCompletionContexts = ['s:ContextText', 's:ContextDiscover']
let g:SuperTabContextDiscoverDiscovery = ["&omnifunc:<c-x><c-o>"]
" Problem with load order (vimrc is evaluated before latex-box setting of omnifunc)
" \ verbose set omnifunc? | " is empty
" added this autocommand to after/ftplugin/tex.vim
" :do FileType solves also the problem
autocmd FileType * 
      \ if &omnifunc != '' |
      \ call SuperTabChain(&omnifunc, "<c-p>") |
      \ call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
      \ endif
"file ~/.vim/after/ftplugin/tex.vim
if &omnifunc != '' |
\ call SuperTabChain(&omnifunc, "<c-p>") |
\ call SuperTabSetDefaultCompletionType("<c-x><c-u>") |
\ endif

Verification of settings and load order

% within a tex file
:verbose set completefunc?`
    completefunc=SuperTabCodeComplete
        Last set from ~/.vim/bundle/56c-supertab/plugin/supertab.vim   

:verbose set omnifunc?
    omnifunc=LatexBox_Complete
        Last set from ~/.vim/bundle/23-latex-box/ftplugin/latex-box/complete.vim 

:scriptnames
:v/\v(tex)|(vimrc)|(pathogen)/delete
  1: /usr/share/vim/vimrc
  3: ~/.vimrc
  4: ~/.vim/bundle/00-pathogen/autoload/pathogen.vim
 32: ~/.vim/bundle/21-latex-suite/plugin/SyntaxFolds.vim
 33: ~/.vim/bundle/21-latex-suite/plugin/filebrowser.vim
 34: ~/.vim/bundle/21-latex-suite/plugin/imaps.vim
 35: ~/.vim/bundle/21-latex-suite/plugin/libList.vim
 36: ~/.vim/bundle/21-latex-suite/plugin/remoteOpen.vim
132: ~/.vim/bundle/21-latex-suite/ftplugin/tex_latexSuite.vim
133: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/main.vim
134: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/texrc
135: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/texproject.vim
136: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/texmenuconf.vim
137: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/envmacros.vim
138: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/wizardfuncs.vim
139: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/elementmacros.vim
140: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/mathmacros.vim
141: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/multicompile.vim
142: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/compiler.vim
143: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/folding.vim
144: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/templates.vim
145: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/custommacros.vim
146: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/bibtex.vim
147: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/brackets.vim
148: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/smartspace.vim
149: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/texviewer.vim
150: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/version.vim
151: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/packages.vim
152: ~/.vim/bundle/21-latex-suite/compiler/tex.vim
153: ~/.vim/bundle/23-latex-box/ftplugin/tex_LatexBox.vim
154: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/common.vim
155: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/complete.vim
156: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/motion.vim
157: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/latexmk.vim
158: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/folding.vim
159: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/findmain.vim
160: ~/.vim/bundle/23-latex-box/ftplugin/latex-box/mappings.vim
162: /usr/share/vim/vim73/ftplugin/tex.vim
163: /usr/share/vim/vim73/ftplugin/plaintex.vim
164: /usr/share/vim/vim73/ftplugin/initex.vim
165: ~/.vim/after/ftplugin/tex.vim
166: ~/.vim/after/ftplugin/tex_plugins.vim
167: ~/.vim/after/ftplugin/tex_swapit.vim
168: ~/.vim/bundle/21-latex-suite/indent/tex.vim
169: ~/.vim/bundle/23-latex-box/indent/tex.vim
170: /usr/share/vim/vim73/indent/tex.vim
171: /usr/share/vim/vim73/syntax/tex.vim
172: ~/.vim/bundle/23-latex-box/after/syntax/tex.vim
173: ~/.vim/bundle/21-latex-suite/ftplugin/latex-suite/packages/amsmath
174: ~/.vim/bundle/21-latex-suite/ftplugin/bib_latexSuite.vim
@ervandew

This comment has been minimized.

Show comment
Hide comment
@ervandew

ervandew Nov 18, 2014

Owner

@kiryph
So it looks like you got it sorted out... correct?

Owner

ervandew commented Nov 18, 2014

@kiryph
So it looks like you got it sorted out... correct?

@kiryph

This comment has been minimized.

Show comment
Hide comment
@kiryph

kiryph Nov 18, 2014

Ah right. I didn't mention that: Yes, it works.

kiryph commented Nov 18, 2014

Ah right. I didn't mention that: Yes, it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment