Launch Extensions

Launch can be customized and extended by the end user through its xml interface. This interface can be used to add or override the launch support for any filetype that is supported by Editra.

NOTE: As of version 1.10 of the Launch plugin this is mostly not necessary anymore. Any filetype that is recognized by Editra can be supported in Launch automatically and can have its commands edited through the user interface.


Requirements

  • Launch Plugin >= 1.5

To use this interface all that needs to be done is to either create or edit launch.xml in the user config directory ($CONFIGDIR/cache/launch.xml). Included below is an example to show how the xml is structured and what features are availble.

<!-- Launch Xml Specification -->
 
<launch version="1">
 
   <!-- Defines a Launch handler
   name parameter is the file type name that the handler is associated with
   -->
   <handler name="Python" id="ID_LANG_PYTHON">
 
      <!-- List of commands that are available to the launcher
      default attribute specifies the default command to use
      -->
      <commandlist default="python">
         <!-- Commands that are available to be executed
         name attribute is the alias that will be shown in the dropdown list
         execute attribute is the actual command that will be run
         -->
         <command name="python" execute="python2.5 -u"/>
         <command name="pylint" execute="/usr/local/bin/pylint"/>
      </commandlist>
 
      <!-- Regular Expression patterns for highlighting error
      lines in the processes output
      -->
      <error pattern="File &quot;(.+)&quot;, line ([0-9]+)"/>
 
      <!-- Regular Expression for getting the filename and line number
      from text that is highlighted as an error. This is usually the same as
      the error pattern. This regular expression must have 2 groups in it the
      first group is the filename and the second is a digit for the line number.
      -->
      <hotspot pattern="File &quot;(.+)&quot;, line ([0-9]+)"/>
 
   </handler>
 
   <!-- The following is a minimal example to add support for C -->
   <handler name="C" id="ID_LANG_C">
   </handler>
 
</launch>