Bug#810929: Renders Vim unusable

2016-01-15 Thread Michael Fladischer
On Thu, 14 Jan 2016 10:38:26 +1300 martin f krafft 
 wrote:
> Following my install of vim-ultisnips, I cannot use Vim anymore.
> I did not even use vim-addons to enable the addon.
> 
> For any document I open, once I enter insert mode and type as much
> as a single character, I get a traceback from Ultisnips (see below).

I'm unable to reproduce this in a clean sid chroot. Did you have an
older version of vim-ultisnips installed before?

What is the output of `vam status ultisnips`?

Does the directory ~/.vim/snippets exist?

Do you have any other snippet managers installed for vim, e.g. vim-
snipmate? Anything through pathogen/vundle/...?

Cheers,
-- 
Michael Fladischer
Fladi.at


signature.asc
Description: This is a digitally signed message part


smime.p7s
Description: S/MIME cryptographic signature


Bug#810929: Renders Vim unusable

2016-01-13 Thread martin f krafft
Package: vim-ultisnips
Version: 3.1-2
Severity: grave

Following my install of vim-ultisnips, I cannot use Vim anymore.
I did not even use vim-addons to enable the addon.

For any document I open, once I enter insert mode and type as much
as a single character, I get a traceback from Ultisnips (see below).

Installing vim-snippets seems to prevent this from happening, so
either vim-ultisnips needs a dependency on vim-snippets, or
(better) a better default handling.

Here is the traceback:

An error occured. This is either a bug in UltiSnips or a bug in a
snippet definition. If you think this is a bug, please report it to
https://github.com/SirVer/ultisnips/issues/new.

Following is the full stack trace:
Traceback (most recent call last):
  File "/var/lib/vim/addons/pythonx/UltiSnips/snippet_manager.py", line 61, in 
wrapper
return func(self, *args, **kwds)
  File "/var/lib/vim/addons/pythonx/UltiSnips/snippet_manager.py", line 810, in 
_track_change
self._try_expand(autotrigger_only=True)
  File "/var/lib/vim/addons/pythonx/UltiSnips/snippet_manager.py", line 709, in 
_try_expand
snippets = self._snips(before, False, autotrigger_only)
  File "/var/lib/vim/addons/pythonx/UltiSnips/snippet_manager.py", line 584, in 
_snips
source.ensure(filetypes, cached=autotrigger_only)
  File "/var/lib/vim/addons/pythonx/UltiSnips/snippet/source/file/_base.py", 
line 47, in ensure
self._load_snippets_for(ft)
  File "/var/lib/vim/addons/pythonx/UltiSnips/snippet/source/file/_base.py", 
line 80, in _load_snippets_for
self._parse_snippets(ft, fn)
  File "/var/lib/vim/addons/pythonx/UltiSnips/snippet/source/file/_base.py", 
line 93, in _parse_snippets
file_data = compatibility.open_ascii_file(filename, 'r').read()
  File "/var/lib/vim/addons/pythonx/UltiSnips/compatibility.py", line 76, in 
open_ascii_file
return open(filename, mode)
IOError: [Errno 2] No such file or directory: 
u'/home/madduck/.vim/snippets/_.snippets'

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vim-ultisnips depends on:
ii  python2.7.11-1
ii  vim-addon-manager 0.5.4
ii  vim-nox [vim-python]  2:7.4.963-1+b1

Versions of packages vim-ultisnips recommends:
pn  vim-snippets  

vim-ultisnips suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)