20090608 Beta

[jps]

There is a bug in 20090608 that causes an extra tab stop to be inserted of sorts: auto quotes shouldn't be causing any issues. It'll be fixed in the next beta.

[tgkeul]

Please give me a hint. My snippets don't work anymore. I can start them and fill $1 but when pressing TAB to jump to $2 sublime will just insert a \t.

Key definiton in my plsql package

Code: Select all

  <binding key="c,u,r,tab" command="insertSnippet 'Packages/PLSQL/New Cursor.sublime-snippet'">
    <context name="selector" value="source.plsql"/>
  </binding>


Key definitions related to TAB in my User\Default.sublime-keymap

Code: Select all

   <binding key="tab" command="insertAndDecodeCharacters \t"/>
   <binding key="tab" command="indent">
      <context name="newlineInSelection" value="true"/>
   </binding>
   <binding key="tab" command="nextInSelectionHistory">
      <context name="canUnpopSelection" value="true"/>
   </binding>


The snippet

Code: Select all

<snippet>
    <content><![CDATA[
/**
* ${1:cursor_name}
*
* @param ${2:param_name}
*/
cursor $1
($2 in ${3:param_type})
is
  select $4
    from
   where = $2;
]]></content>
</snippet>


[jps]

Key bindings to move through the tab stops have been changed, instead of nextInSelectionHistory/prevInSelectionHistory, you'll now want nextField and prevField:

Code: Select all

   <binding key="tab" command="nextField">
      <context name="hasNextField" value="true"/>
   </binding>
   <binding key="shift+tab" command="prevField">
      <context name="hasPrevField" value="true"/>
   </binding>


Note to everyone else: Default.sublime-keymap already includes these changes, this will only effect you if you're overwriting the default version after installing.