wrong snippets are included

Bug #941067 reported by Aldis Berjoza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UltiSnips
Invalid
Undecided
Unassigned

Bug Description

Sorry I couldn't form good title. Here's the problem.

I have
* ruby.snippets
* rails.snippets
* haml.snippets
* ruby_haml.snippets
* rails_haml.snippets

in ruby snippets I have
extends rails

in haml I have:
extends ruby_haml, rails_haml

Now the problem:

when I edit somefile.rb end for example type:

problems.each<TAB>

at this moment Ultisnips offers menu to select which snippet to use.
But for ruby I only have 1 snippet for ".each", the other one was imported from ruby_haml.snippets

Conclusion: UltiSnips has bad filename checking code.

Here's my config if you need to take a look at it:
https://github.com/graudeejs/dot.vim

and here are my snippets:
https://github.com/graudeejs/dot.vim/tree/master/snippets

NOTE: I don't use snippets that come with UltiSnips, instead I've written my own snippets from scratch

Revision history for this message
Aldis Berjoza (graudeejs) wrote : Re: [Bug 941067] [NEW] wrong snippets are included

On Sat, 25 Feb 2012 19:13:06 -0000
Aldis Berjoza <email address hidden> wrote:

> Public bug reported:
>
> Sorry I couldn't form good title. Here's the problem.
>
> I have
> * ruby.snippets
> * rails.snippets
> * haml.snippets
> * ruby_haml.snippets
> * rails_haml.snippets
>
> in ruby snippets I have
> extends rails
>
> in haml I have:
> extends ruby_haml, rails_haml
>
> Now the problem:
>
> when I edit somefile.rb end for example type:
>
> problems.each<TAB>
>
> at this moment Ultisnips offers menu to select which snippet to use.
> But for ruby I only have 1 snippet for ".each", the other one was
> imported from ruby_haml.snippets
>
> Conclusion: UltiSnips has bad filename checking code.
>
> Here's my config if you need to take a look at it:
> https://github.com/graudeejs/dot.vim
>
> and here are my snippets:
> https://github.com/graudeejs/dot.vim/tree/master/snippets
>
> NOTE: I don't use snippets that come with UltiSnips, instead I've
> written my own snippets from scratch
>
> ** Affects: ultisnips
> Importance: Undecided
> Status: New
>

I see behaviour changed. You probably should close this pr. Sorry for
noise. I update my snippets to work well with latest UltiSnips

--
Aldis Berjoza
  http://www.bsdroot.lv/

Revision history for this message
SirVer (sirver) wrote :

Yep, you became victim of a backwards incompatible change in Version
2.0. Sorry for that. I set this to invalid.

  status invalid

Changed in ultisnips:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.