Difference between revisions of "Sublime Text"

m (Lua Love: Updated to LÖVE 11.3 :O (but not completions))
(16 intermediate revisions by 7 users not shown)
Line 1: Line 1:
''Sublime Text is a sophisticated text editor for code, markup and prose.''
+
The following instructions work both in [http://sublimetext.com/ Sublime Text] 2 and 3 unless mentioned otherwise.
  
== Running love projects from Sublime Text 2  ==
+
== Lua Love ==
  
=== On Windows ===
+
The [https://packagecontrol.io/packages/Lua%20Love Lua Love Package] provides syntax highlighting, snippets, autocompletion and build rules.
Create a new Build System first: Tools -> Build System -> New Build System
 
  
Then paste the following code:
+
# Install [https://packagecontrol.io/installation Package Control], restart Sublime.
<source lang="ini">
+
# Press Ctrl+Shift+P to open the '''command palette''' and use the '''Package Control: Install Package''' command.
{
+
# Wait until another input field appears and install the '''Lua Love''' package.
    "selector": "source.lua",
+
# In the '''command palette''' enable syntax highlighting with '''Set Syntax: Lua (Love)'''.
    "cmd": ["love", "$file_path"]
+
# In Sublime 3, you can use Ctrl+Shift+B to select the build system '''LuaLove - Love2D''' which from then on you can start using Ctrl+B.
 +
# In Sublime 2, you have to manually edit the build script (<code>C:\Users\....\AppData\Roaming\Sublime Text 2\Packages\Lua Love\LuaLove.sublime-build</code> in Windows):
 +
 
 +
<source lang="ini">{
 +
"file_regex": "^(?:(?:\t)|(?:.+: ))(.+):([0-9]+): (.*)$",
 +
"selector": "source.lua",
 +
"shell": true,
 +
"cmd": ["love", "${project_path:${file_path:.}}"],
 +
 
 +
"variants": [
 +
{
 +
"name": "Love2D",
 +
"shell": true,
 +
"cmd": ["love", "${project_path:.}"],
 +
"osx":
 +
{
 +
"cmd": ["love $project_path"]
 +
}
 +
},
 +
{  "name": "ldoc: File",
 +
"shell": true,
 +
"cmd": ["ldoc -d $project_path/doc/$file_base_name -f markdown -t $file_base_name $file"]
 +
},
 +
{  "name": "ldoc: Project",
 +
"shell": true,
 +
"cmd": ["ldoc -d $project_path/doc -f markdown -t $project_base_name $project_path/src/"]
 +
}
 +
]
 
}
 
}
 
</source>
 
</source>
  
Now you can use CTRL + B to run your love project.
+
Both Sublime 2 and 3 require the directory of your LÖVE binary to be part of your [[PATH]] variable. You can avoid this by changing the <code>"love"</code> path in the build script. This is [http://stackoverflow.com/questions/21190392/how-to-change-default-code-snippets-in-sublime-text-3 more complicated in Sublime 3].
  
=== On Mac ===
+
== Simple Build System  ==
  
Create a new Build System first: Tools -> Build System -> New Build System
+
Create a new Build System: <code>Tools -> Build System -> New Build System</code> and use the following code.
  
Then paste in the following code:
 
 
<source lang="ini">
 
<source lang="ini">
 
{
 
{
 
     "selector": "source.lua",
 
     "selector": "source.lua",
     "cmd": ["/Applications/love.app/Contents/MacOS/love", "$file_path"]
+
     "file_regex": "^Error: (?:[^:]+: )?([^: ]+?):(\\d+):() ([^:]*)$",
 +
    "windows": {
 +
        "cmd": ["C:/Program Files/LOVE/love.exe", "${folder:${file_path}}"],
 +
        "shell": true
 +
    },
 +
    "osx": {
 +
        "cmd": ["/Applications/love.app/Contents/MacOS/love", "${folder:${file_path}}"]
 +
    },
 +
    "linux": {
 +
        "cmd": ["love", "${folder:${file_path}}"]
 +
    }
 
}
 
}
 
</source>
 
</source>
(This is assuming that your love.app is in the Applications folder)
 
  
Now you can use CMD + B to run your love project.
+
Save it in the suggested location as <code>love-run.sublime-build</code>.
 +
 
 +
Now you can use Ctrl+B or Cmd+B to run your love project.
 +
 
 +
=== Issues ===
 +
 
 +
* This build system depends on the location of your LÖVE binary. Check the path in the <code>"cmd":</code> line.
 +
* This build system doesn't seem to work if you have spaces in your <code>$file_path</code>.
 +
 
 +
== Console output ==
 +
 
 +
By default the console in Sublime Text will not display any output, such as print() calls, until the LOVE application has been closed.
 +
 
 +
To make the console output display live add the following code to the top of your <code>main.lua</code> file, or inside <code>[[conf.lua]]</code>:
 +
<source lang="lua">
 +
io.stdout:setvbuf("no")
 +
</source>
 +
 
 +
== Jumping to errors ==
 +
 
 +
If there was an error during execution, you can use the F4 (next error) and SHIFT-F4 (previous error) to go through the errors that lua encountered.
  
 
== See also ==
 
== See also ==
* [http://www.sublimetext.com/2 Sublime Text 2 Website]
+
* [http://www.sublimetext.com/ Sublime Text Website]
 
* [http://sublime-text-unofficial-documentation.readthedocs.org/en/latest/reference/build_systems.html Sublime Text 2 Build Systems]
 
* [http://sublime-text-unofficial-documentation.readthedocs.org/en/latest/reference/build_systems.html Sublime Text 2 Build Systems]
 +
* [http://stackoverflow.com/questions/16338523/live-console-output-in-sublime-text-2 Stack Overflow question about console output in Sublime Text 2]
  
 
[[Category:Software]]
 
[[Category:Software]]
 +
[[Category:Editor integration]]
  
{{#set:Name=Sublime Text 2}}
+
{{#set:Name=Sublime Text}}
 
{{#set:Description=Source Code Editor}}
 
{{#set:Description=Source Code Editor}}
 
{{#set:Type=Editor}}
 
{{#set:Type=Editor}}

Revision as of 10:08, 21 June 2020

The following instructions work both in Sublime Text 2 and 3 unless mentioned otherwise.

Lua Love

The Lua Love Package provides syntax highlighting, snippets, autocompletion and build rules.

  1. Install Package Control, restart Sublime.
  2. Press Ctrl+Shift+P to open the command palette and use the Package Control: Install Package command.
  3. Wait until another input field appears and install the Lua Love package.
  4. In the command palette enable syntax highlighting with Set Syntax: Lua (Love).
  5. In Sublime 3, you can use Ctrl+Shift+B to select the build system LuaLove - Love2D which from then on you can start using Ctrl+B.
  6. In Sublime 2, you have to manually edit the build script (C:\Users\....\AppData\Roaming\Sublime Text 2\Packages\Lua Love\LuaLove.sublime-build in Windows):
{
	"file_regex": "^(?:(?:\t)|(?:.+: ))(.+):([0-9]+): (.*)$",
	"selector": "source.lua",
	"shell": true,
	"cmd": ["love", "${project_path:${file_path:.}}"],

	"variants": [
		{
			"name": "Love2D",
			"shell": true,
			"cmd": ["love", "${project_path:.}"],
			"osx":
			{
				"cmd": ["love $project_path"]
			}
		},
		{   "name": "ldoc: File",
			"shell": true,
			"cmd": ["ldoc -d $project_path/doc/$file_base_name -f markdown -t $file_base_name $file"]
		},
		{   "name": "ldoc: Project",
			"shell": true,
			"cmd": ["ldoc -d $project_path/doc -f markdown -t $project_base_name $project_path/src/"]
		}
	]
}

Both Sublime 2 and 3 require the directory of your LÖVE binary to be part of your PATH variable. You can avoid this by changing the "love" path in the build script. This is more complicated in Sublime 3.

Simple Build System

Create a new Build System: Tools -> Build System -> New Build System and use the following code.

{
    "selector": "source.lua",
    "file_regex": "^Error: (?:[^:]+: )?([^: ]+?):(\\d+):() ([^:]*)$",
    "windows": {
        "cmd": ["C:/Program Files/LOVE/love.exe", "${folder:${file_path}}"],
        "shell": true
    },
    "osx": {
        "cmd": ["/Applications/love.app/Contents/MacOS/love", "${folder:${file_path}}"]
    },
    "linux": {
        "cmd": ["love", "${folder:${file_path}}"]
    }
}

Save it in the suggested location as love-run.sublime-build.

Now you can use Ctrl+B or Cmd+B to run your love project.

Issues

  • This build system depends on the location of your LÖVE binary. Check the path in the "cmd": line.
  • This build system doesn't seem to work if you have spaces in your $file_path.

Console output

By default the console in Sublime Text will not display any output, such as print() calls, until the LOVE application has been closed.

To make the console output display live add the following code to the top of your main.lua file, or inside conf.lua:

io.stdout:setvbuf("no")

Jumping to errors

If there was an error during execution, you can use the F4 (next error) and SHIFT-F4 (previous error) to go through the errors that lua encountered.

See also