A bare-bones console logger for Sublime Text 2 and 3.
JavaScript Python
Latest commit da3bf5d Mar 29, 2015 @yrammos Update README.me.



A bare-bones console logger for Sublime Text 2 and 3.


Sublime Text 2 and 3 provide a console (accessible via Control-`) for interaction with their Python-based innards and plug-in architecture. This plug-in logs the console contents into a plain-text file ornamented with logger activation/deactivation timestamps.

The log is erased and recreated each time Sublime Text is launched.


The most straightforward installation method is by far via Will Bond's superb Package Control. Alternatively, you may clone (or copy the contents of) this repository into your Sublime Text ./Packages folder:

git clone https://github.com/yrammos/SublimeLog.git


For now SublimeLog supplies a single command that toggles the logger. The default key-binding is Command-Control-C on OS X or Alt-Control-C on Windows/Linux. You may also invoke it via the command palette (⌘-Shift-P on a Mac or Ctrl-Shift-P otherwise): SublimeLog: Toggle logger (on/off)

The key-binding is adjustable in the default JSON file appropriate to your platform:

./Packages/SublimeLog/Default ({OSX | Linux | Windows}).sublime-keymapping

or, to prevent overwrites following plugin updates, in a corresponding file within the User subfolder:

./Packages/User/SublimeLog ({OSX | Linux | Windows}).sublime-keymapping

Retrieving the log

By default, the console is logged in the following plain-text file:


This default destination is adjustable in:


or, preferably, in the User subfolder:


Whatever path-filename you declare for the log is relative to your root folder, so please be sure you have adequate write permissions or the plug-in will complain politely.

Note that Sublime Text no longer needs to be restarted for changes to these settings to take effect.


Due to technical limitations beyond my control, the plug in does not capture "system" messages output to the console by Sublime Text itself. Among them are, for example, Reloading plugin... messages. This should be inconsequential for most users of SublimeLog but Your Mileage May Vary. See this thread if you are interested in further details.

Good news: This limitation appears to have been lifted in the latest betas of SublimeText 3.

Serving suggestion

I wrote this plug-in as a complement to my dissertation LaTeX workflow. Within a dedicated terminal session, or a tmux pane for that matter, I constantly monitor the log file for changes:

tail -f ~/.subl.log

This provides me with a dynamic view of the console stream in a separate window, without the space- and time-consuming tedium of toggling the console view.

Version history


  • NEW: Support for Sublime Text 3.
  • NEW: Logger may now be toggled via the command palette.
  • NEW: Settings modifications no longer necessitate an editor restart to take effect.


  • NEW: Adds preferences menu (Sublime Text 2 > Preferences > Package Settings > SublimeLog).
  • FIXED: Default and user preferences are now honored as expected.



  • NEW: First release.

Copyright © 2012-3 by Yannis Rammos. This work is made available under the terms of the Creative Commons Attribution-NonCommercial 3.0 Unported (CC BY-NC 3.0) license, http://creativecommons.org/licenses/by-sa/3.0/.