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

Node​Eval

by mediaupstream ST2

A Sublime Text Plugin that "evals" a selection/document with NodeJS

Details

  • 2014.01.02.23.47.49
  • github.​com
  • github.​com
  • 11 years ago
  • 6 minutes ago
  • 12 years ago

Installs

  • Total 3K
  • Win 1K
  • Mac 984
  • Linux 491
Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

NodeEval Sublime Text 2 & 3 Package

Use the NodeJS binary to evaluate a document or selection(s) and print the results

Screenshots

Install

Installation via the Package Control (Search for NodeEval)

To install manually clone this project into your Sublime Text 2\Packages folder:

OSX

git clone git://github.com/mediaupstream/SublimeText-NodeEval.git ~/Library/Application\ Support/Sublime\ Text\ 2/Packages/NodeEval

Windows

git clone git://github.com/mediaupstream/SublimeText-NodeEval.git "%APPDATA%\Sublime Text 2\Packages\NodeEval"

Usage

After installation you will have:

  • Context Menu and Tools Menu items:
    • NodeEval - evaluate the current selection(s) / document with node
    • NodeEval - Continuous (Toggle) - Continually evaluate the current selection(s) / document with node. This command is a toggle for the current document / selection(s) only. You can set the refresh rate in the Sublime settings (see below)
  • Default keyboard shortcuts:
    • ctrl+n,e
  • Package Settings: Preferences > Package Settings > NodeEval
{
      // The absolute path to your nodejs executable
      // e.g. "/usr/local/bin/node" or "C:\\bin\\node.exe"
      "node_command": "/usr/local/bin/node",

      // How to output the results, options include:
      // - new [default] "send output to a new file"
      // - console       "send output to a new Panel (Console) view"
      // - replace       "overwrite the current file/selection with the output"
      // - clipboard     "there is no output, output copied to clipboard"
      "output": "new",

      // if output type is "new" the output is overwritten, set to false to append the output
      "overwrite_output": true,

      // if set to true the output is copied to the clipboard
      // if `output` is set to "clipboard" this value is ignored
      "copy_to_clipboard": false,

      // refresh rate threshold for "continuous" mode (in milliseconds)
      "threshold": 200,

      // Set any extra ENVIRONMENT Variables as an object
      // @example
      //    "env": {
      //      "NODE_PATH":"/path/to/node",
      //      "NODE_MODULES":"/path/to/node_modules"
      //    }
      // @note: if you start sublime from a terminal using `subl` your normal environment
      // variables should be available to you 
      "env": {}

    }

The commands work on a selection, multiple selections or if nothing is selected the whole document. Your script will be eval'd through nodejs in it's own thread.


Why not just use the NodeJS plugin, or the nodejsLauncher plugin ?
the NodeJS plugin is awesome, but it's also really bloated. also the nodejsLauncher only works on Windows.

Contributors

Derek Anderson
Shane Walker
Shesh
akira-cn
Jakub Gutkowski

License

MIT License