ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Better Java​Script

by int3h ST2/ST3

Fixes to Sublime Text's JavaScript symbol list

Details

Installs

  • Total 28K
  • Win 14K
  • OS X 9K
  • Linux 5K
Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30 Mar 29 Mar 28 Mar 27 Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9
Windows 4 3 4 2 3 5 6 0 0 7 2 5 3 6 3 2 5 4 2 6 6 3 2 6 7 6 2 8 9 7 1 4 11 9 6 6 2 1 6 7 6 8 5 1 2 8
OS X 0 0 1 1 0 2 3 2 0 0 1 0 3 1 0 1 1 0 2 1 1 0 1 3 1 1 1 2 0 2 1 1 1 1 3 1 0 0 0 2 3 0 4 2 3 3
Linux 0 2 0 0 0 1 1 0 1 3 0 0 2 2 1 1 1 6 1 1 1 0 2 1 1 0 0 1 2 1 1 1 0 1 2 3 0 0 0 2 1 1 1 0 0 2

Readme

Source
raw.​githubusercontent.​com

Sublime Better Javascript

This package is an improved version of Sublime Text's JavaScript package, focused mainly on improving symbol navigation.

The default JavaScript language definition in Sublime Text has quirky symbol identification, and fills your symbols list with noise like anonymous functions, object instantiation, and even calls to console.log().

Useless Symbol List

This project fixes Sublime so only named function definitions and function prototype attributes show up in the symbol list. It also fixes how these symbols are displayed in the symbol list, so that only the function names are shown.

Improved Symbol List

This package has been tested on Sublime Text 2 and 3.

Installing

Install via package control (search for 'Better JavaScript').

Alternatively, cd to you Sublime packages directory, then:

git clone git@github.com:int3h/sublime-better-javascript.git 'Sublime Better JavaScript'

Refreshing the symbols of existing files

In some cases, especially with Sublime Text 3, the symbols list of files that have been previously opened may not refresh with the improved symbols.

The most reliable way I've found to fix this is to close all open JavaScript files and quit Sublime (it's important that all JS files are closed when Sublime exits.) Then delete the Index and Cache subdirectories in your Sublime user data directory (the parent of the Packages directory.) In Mac OS X, I've also had to delete ~/Library/Caches/com.sublimetext.3 (or com.sublimetext.2).

Uninstalling

Before uninstalling Better JavaScript, be sure close all open JavaScript/JSON files, and remove “JavaScript” from the “ignored_packages” list in your Sublime user settings. You can now safely uninstall the Better JavaScript package.

It's normal to see a few errors from Sublime about not being able to find syntax files. Just exit Sublime and re-open it, and everything should be fixed.

Details

The default JavaScript.tmLanguage makes some… odd decisions on what namespace to put certain tokens in. Specifically, it puts a lot of tokens in the entity.name.* namespaces that probably shouldn't be.

There is a file, Symbol List Banned.tmPreferences, in the JavaScript package which ostensibly is supposed to filter out some specific sub-namespaces from the symbols list, but it doesn't really work. I modified Symbol List Banned.tmPreferences to specifically match object instantiation and console.log calls, and set them to not show up in the symbol list.

I also modified Symbol List Function.tmPreferences to do additional processing of function names with regexes, to strip out extraneous characters (like “function” and “= function()”) before showing them in the symbol list. An additional file, Symbol List Prototype.tmPreferences, was added to include function prototype attributes in the symbol list.