ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

GSP Snippets

by mathifonseca ST2/ST3

Sublime Text snippets for Groovy Server Pages

Details

Installs

  • Total 801
  • Win 381
  • OS X 248
  • Linux 172
Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8
Windows 0 0 0 1 0 0 1 0 0 0 0 0 1 0 0 1 0 0 0 0 0 1 0 0 0 0 3 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 3 0 0
OS X 0 0 0 0 0 0 0 2 0 0 0 1 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0
Linux 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 1 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Sublime Text GSP Snippets

Installation

The easiest way to get these snippets, is by using Package Control. If you already have it, you just need to search GSP Snippets and install it. In case you don't, take a look here.

Usage

Once you have installed the snippets, the only thing you need to do is type the desired trigger and hit Tab (or whatever you have set as completion key). Also, you can press ⌘ + Space (or Ctrl + Space) to get a list of all available completions.

Triggers

It's the sequence of keys you have will press to insert a snippet. For your (and our) convenience, all our snippets start with the letter g, so that you can start from there and choose from the options that the autocomplete prompts you.

Fields

As you probably already know, there are tags that have optional attributes and many other variations. We've created these snippets according to our usual needs and as you press Tab, you will navigate the fields you need to fill. But in some cases, we've added more attributes that will be highlighted so that you can press Delete if you don't need them or Tab again if you do.

Collaboration

We created these snippets because we got tired of copy/pasting from the Grails Guide, so most of them are just shortcuts to the default tags that are presented there. In some cases, you will find our own inventions, like the gfor, which is a <g:each> tag with a range.

So if you think we got something wrong, have any suggestions, want to make a request or add some creation of your own, please feel free to contact us.

Contact

You can report anything using this repo's issue section.

Also, you can fork it and submit a pull request.

And in case you need a more human touch, you can contact @mathifonseca or @bToGaleotti