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
  • 10 years ago
  • 13 minutes ago
  • 11 years ago

Installs

  • Total 3K
  • Win 1K
  • Mac 984
  • Linux 491
Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14 May 13 May 12 May 11
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