Difference between revisions of "Sublime Text"

736 bytes removed ,  14:41, 1 April 2016
no edit summary
imported>Hannibalektr
imported>Hannibalektr
Line 1: Line 1:
{{RequiresPublicUpdate|Remove this line}}
(INTERNAL: interested in how this all works? [[Sublime Text Development|See how the sausage is made]].)
==Installation==
==Installation==
===Install Sublime===
===Install Sublime===
Line 12: Line 9:


====If no previous Papyrus plugin====
====If no previous Papyrus plugin====
{{RequiresPublicUpdate|Update these settings for public release and remove update ini setting line}}
#In Sublime, right-click and select PapyrusF4 -> Create default INI file
#In Sublime, right-click and select PapyrusF4 -> Create default INI file
#Make the following changes:
#Make the following changes:
Line 18: Line 14:
#*Point "compiler=" and "assembler=" at the compiler and assembler exe files in your PC folder
#*Point "compiler=" and "assembler=" at the compiler and assembler exe files in your PC folder
#*Point "output=" at your "Data\Scripts" folder
#*Point "output=" at your "Data\Scripts" folder
#*Change "wiki=" to "wiki=http://intranet.bethsoft.com/tesv_editor/"
#*Change "wiki=" to "wiki=http://www.creationkit.com/fallout4/"
#*Add the following to the top of the file:
[General]
update=\\bgs\F4\Tools\Sublime Text\Packages\PapyrusF4


====If you have the old Papyrus plugin====
====If you have the old Papyrus plugin====
{{RequiresPublicUpdate|Public users don't have the workspace switch tool - use above steps to generate and edit ini, and adjust instructions for setting it up as the default}}
Follow the above steps for if you have no Papyrus plugin, then do the following:
#Launch the workspace switch tool and it will auto-generate the new ini file for you based on your old ini file
#In Sublime, open an existing PSC file
#In Sublime, open an existing PSC file
#Select View -> Syntax -> Open all with current extension as... -> PapyrusF4 -> PapyrusF4
#Select View -> Syntax -> Open all with current extension as... -> PapyrusF4 -> PapyrusF4
Line 61: Line 53:
==Adding Snippets==
==Adding Snippets==
The existing Papyrus package for Sublime Text includes a number of snippets that will auto-complete to frequently used things (like typing "onhit" and then tab will create a proper OnHit event so you don't have to constantly be looking up the syntax). If you want to make more of these, you can simply add another .sublime-snippet file to the Package directory. Documentation on snippets is available at [http://www.sublimetext.com/docs/2/ Sublime Text docs site].
The existing Papyrus package for Sublime Text includes a number of snippets that will auto-complete to frequently used things (like typing "onhit" and then tab will create a proper OnHit event so you don't have to constantly be looking up the syntax). If you want to make more of these, you can simply add another .sublime-snippet file to the Package directory. Documentation on snippets is available at [http://www.sublimetext.com/docs/2/ Sublime Text docs site].
{{RequiresPublicUpdate|Remove following line}}
If you make a new snippet that you think might be useful, e-mail it to Jeff Lundin for consideration in distribution.


==Tips 'n' Tricks==
==Tips 'n' Tricks==
Anonymous user