[feature request] snippet aliasing

[Aldis Berjoza]

It would be very useful if you could make aliases for snippets

This would help avoiding snippets that have same body, but different name.

For example I have eachpair snippet, which I use in ruby end perl
However I'd like to define each_pair snippet for ruby, which would be absolutely the same as eachpair.

[SirVer (sirver)]

Are the eachpair snippet the exakt same in both languges? Because it seems like what you want to do is already supported with regular expression snippets:

snippet "each_?pair" "each pair" br
blaaah
endsnippet

this one will trigger on "eachpair" and on "each_pair".

[Aldis Berjoza (graudeejs)]

On Fri, 11 Nov 2011 20:33:40 -0000
SirVer <email address hidden> wrote:

> Are the eachpair snippet the exakt same in both languges? Because it
> seems like what you want to do is already supported with regular
> expression snippets:
>
> snippet "each_?pair" "each pair" br
> blaaah
> endsnippet
>
> this one will trigger on "eachpair" and on "each_pair".

Oh, I didn't know that

No, snippet expands to different content in different languages.
I just generalise common things.
However your suggestion does exactly what I want.

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

[SirVer (sirver)]

I set this bug report to invalid than. Glad to be of service.

[Aldis Berjoza (graudeejs)]

On Fri, 11 Nov 2011 22:39:55 -0000
SirVer <email address hidden> wrote:

> I set this bug report to invalid than. Glad to be of service.
>
> ** Changed in: ultisnips
> Status: Incomplete => Invalid
>

Ok, there is problem with this

snippet "\.Each_?key" "each_key" bri
.each_key { |${1:key}| ${2:# TODO} }${3:$0}
endsnippet

This snippet doesn't work for
  hash.Eachkey
as well as for
  hash.Each_key

However it works for
  .Eachkey
and
  .Eachkey

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

[SirVer (sirver)]

The problem is that the full WORD before your cursor is matched for the trigger. Inword and regular expression bite each other. What you want to do can be done like this:

snippet "(.*).Each_?key" "each_key" bri
`!p snip.rv=match.group(1)`.each_key { |${1:key}| ${2:# TODO} }${3:$0}
endsnippet

It essentially looks at the WORD, checks if it matches your regular expression, than takes everything before .Eachkey and prepends it in the python block in your expansion.

[Aldis Berjoza (graudeejs)]

On Sat, 12 Nov 2011 11:22:46 -0000
SirVer <email address hidden> wrote:

> The problem is that the full WORD before your cursor is matched for
> the trigger. Inword and regular expression bite each other. What you
> want to do can be done like this:
>
> snippet "(.*).Each_?key" "each_key" bri
> `!p snip.rv=match.group(1)`.each_key { |${1:key}| ${2:# TODO} }${3:$0}
> endsnippet
>
> It essentially looks at the WORD, checks if it matches your regular
> expression, than takes everything before .Eachkey and prepends it in
> the python block in your expansion.
>

Awesome. This is exactly what I need... Now I'll be able to write more
advanced snippets.

Huge thanks :D

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

[Aldis Berjoza (graudeejs)]

Ok, I discovered flaw with regular expressions

For example:

snippet "(each_?key|for_?in)" "for (<key> in <object>) { ..." r
for (${1:key} in ${2:object}) {
 ${3:document.write($2[$1] + "\n");}
}${4:$0}
endsnippet

would trigger for
SomeBadKeyWordeachkey

So snippet aliasing would be nice to have

[SirVer (sirver)]

I do not agree. The feature you are looking for is \b Check for word boundary. See the reference for regular expressions http://docs.python.org/library/re.html

snippet "\b(each_?key|for_?in)" "for (<key> in <object>) { ..." r