search

MarcWeber / ultisnips

Official Mirror of UltiSnips trunk on LaunchPad. Send pull requests to SirVer/ultisnips!
https://launchpad.net/ultisnips
25 stars 5 forks source link

Lazy-appending to sys.path prevents YouCompleteMe to detect UltiSnips. #16

Closed blueyed closed 11 years ago

blueyed commented 11 years ago

See https://github.com/blueyed/ultisnips/commit/d0189cbb00e51746545794da24141a1c582f30e8 for more explanation and a suggested fix.

MarcWeber commented 11 years ago

Reopen if the most current patch introducing setup_py_path_early is not good enough for you

blueyed commented 11 years ago

For reference: https://github.com/MarcWeber/ultisnips/commit/d9d8e7ff2a9f3436133de57a1d621b2de92bf87f

This looks decent. I wonder if YouCompleteMe could autodetect that there is UltiSnips#SetupPath and call it conditionally.. IIRC it is not possible to check for autoload function, is it? Would it make sense to just call it before trying to import UltiSnips? That would make the integration much smoother, without having to change a UltiSnips setting.

MarcWeber commented 11 years ago

If you use YouCompleteMe you'll use UltiSnips anyway, so it won't matter wher you load it.

blueyed commented 11 years ago

Yeah.

The point is however that you (as a user) have to configure something to make it work now (setup_py_path_early=1), and it is not easy to find out. UltiSnips will just stop working with YCM. This is why I have considered a patch for YCM to autoload/trigger setup of UltiSnips.

MarcWeber commented 11 years ago

Then make YCM check for the g: vars instead. Every user is likely to configure UltiSnips (at least this version) in some way.

MarcWeber commented 11 years ago

This version has g:UltiSnips[key] and g:UltiSnipskey for compatibility. SirVers version only has g:UltiSnipskey