A sublime text plugin for mistral
- Total 68
- Win 38
- Mac 18
- Linux 12
|Oct 21||Oct 20||Oct 19||Oct 18||Oct 17||Oct 16||Oct 15||Oct 14||Oct 13||Oct 12||Oct 11||Oct 10||Oct 9||Oct 8||Oct 7||Oct 6||Oct 5||Oct 4||Oct 3||Oct 2||Oct 1||Sep 30||Sep 29||Sep 28||Sep 27||Sep 26||Sep 25||Sep 24||Sep 23||Sep 22||Sep 21||Sep 20||Sep 19||Sep 18||Sep 17||Sep 16||Sep 15||Sep 14||Sep 13||Sep 12||Sep 11||Sep 10||Sep 9||Sep 8||Sep 7|
About the Mistral Package for Sublime Text
The Mistral package for sublime text contains a ton of snippets you can use to build Mistral workflows using Sublime Text. Both Sublime Text 2 and 3 are supported. This package uses the base YAML syntax highlighting included with Sublime Text.
To install the Mistral pacakge, you first need to install Sublime Text. Go to the following link to download, http://www.sublimetext.com/. This a great application for editing text and supports Linux, Mac, and Windows equally well.
Install Method 1 - Will Bond's Package Control (Recommended)
Will Bond has made a great plugin that loads packages into Sublime Text. If you use this method you will automatically get updates of the Mistral package when they are released. I highly recommend using this approach.
- Start Sublime Text
- Install Package Control from will bond following the instructions at http://wbond.net/sublime_packages/package_control.
command+shift+p(Mac) and type Install Package. You should see “Package Control: Install Package”.
- Type Mistral and press Enter.
A few steps and you will be on your way.
- Create new file and give it the extension
.mistand open it in Sublime Text
- If it doesn't automatically get recognized (You will see Mistral in the bottom right corner), then press
command+shift+p(Mac) and type
Enter. You should see the bottom right of the status bar change.
start,Tabfrom the selection box. It will instantly give you a base Mistral file to start and you can set the name accordingly.
- Use the following snippets to build out your Mistral file and get your workflows going.
acts,Tab–> Actions - Create an 'actions:' section in the file.
act,Tab–> Action - Create a skeleton of action within the 'actions' section.
bec,Tab–> base: std.echo - Create an action with std.echo as the base.
bem,Tab–> base: std.email - Create an action with std.email as the base.
bhttp,Tab–> base: std.http - Create an action with std.http as the base.
bmhttp,Tab–> base: std.mistral_http - Create an action with std.mistral_http as the base.
bssh,Tab–> base: std.ssh - Create an action with std.ssh as the base.
wfs,Tab–> Workflows - Create a 'workflows:' section that will also start off your first workflow.
wf,Tab–> Workflow - Create a single workflow within an already created 'workflows' section.
tec,Tab–> task: std.echo - Create std.echo task within the 'tasks' section of the workflow.
tem,Tab–> task: std.email - Create std.email task within the 'tasks' section of the workflow.
thttp,Tab–> task: std.http - Create std.http task within the 'tasks' section of the workflow.
tmhttp,Tab–> task: std.mistral_http - Create std.mistral_http task within the 'tasks' section of the workflow.
tssh,Tab–> task: std.ssh - Create std.ssh task within the 'tasks' section of the workflow.
Copyright © 2015 Giampiero De Ciantis firstname.lastname@example.org
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.