2015-05-20 07:06:59 +08:00
|
|
|
_ = require 'underscore'
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
ChildProcess = require 'child_process'
|
|
|
|
{Emitter} = require 'event-kit'
|
|
|
|
path = require 'path'
|
|
|
|
|
|
|
|
# Extended: A wrapper which provides standard error/output line buffering for
|
|
|
|
# Node's ChildProcess.
|
|
|
|
#
|
|
|
|
# ## Examples
|
|
|
|
#
|
|
|
|
# ```coffee
|
2015-11-12 02:25:11 +08:00
|
|
|
# {BufferedProcess} = require 'nylas-exports'
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
#
|
|
|
|
# command = 'ps'
|
|
|
|
# args = ['-ef']
|
|
|
|
# stdout = (output) -> console.log(output)
|
|
|
|
# exit = (code) -> console.log("ps -ef exited with #{code}")
|
|
|
|
# process = new BufferedProcess({command, args, stdout, exit})
|
|
|
|
# ```
|
|
|
|
module.exports =
|
|
|
|
class BufferedProcess
|
|
|
|
###
|
|
|
|
Section: Construction
|
|
|
|
###
|
|
|
|
|
|
|
|
# Public: Runs the given command by spawning a new child process.
|
|
|
|
#
|
|
|
|
# * `options` An {Object} with the following keys:
|
|
|
|
# * `command` The {String} command to execute.
|
|
|
|
# * `args` The {Array} of arguments to pass to the command (optional).
|
|
|
|
# * `options` {Object} (optional) The options {Object} to pass to Node's
|
|
|
|
# `ChildProcess.spawn` method.
|
|
|
|
# * `stdout` {Function} (optional) The callback that receives a single
|
|
|
|
# argument which contains the standard output from the command. The
|
|
|
|
# callback is called as data is received but it's buffered to ensure only
|
|
|
|
# complete lines are passed until the source stream closes. After the
|
|
|
|
# source stream has closed all remaining data is sent in a final call.
|
|
|
|
# * `data` {String}
|
|
|
|
# * `stderr` {Function} (optional) The callback that receives a single
|
|
|
|
# argument which contains the standard error output from the command. The
|
|
|
|
# callback is called as data is received but it's buffered to ensure only
|
|
|
|
# complete lines are passed until the source stream closes. After the
|
|
|
|
# source stream has closed all remaining data is sent in a final call.
|
|
|
|
# * `data` {String}
|
|
|
|
# * `exit` {Function} (optional) The callback which receives a single
|
|
|
|
# argument containing the exit status.
|
|
|
|
# * `code` {Number}
|
|
|
|
constructor: ({command, args, options, stdout, stderr, exit}={}) ->
|
|
|
|
@emitter = new Emitter
|
|
|
|
options ?= {}
|
2015-05-20 08:02:46 +08:00
|
|
|
@command = command
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
# Related to joyent/node#2318
|
|
|
|
if process.platform is 'win32'
|
|
|
|
# Quote all arguments and escapes inner quotes
|
|
|
|
if args?
|
|
|
|
cmdArgs = args.filter (arg) -> arg?
|
|
|
|
cmdArgs = cmdArgs.map (arg) =>
|
|
|
|
if @isExplorerCommand(command) and /^\/[a-zA-Z]+,.*$/.test(arg)
|
|
|
|
# Don't wrap /root,C:\folder style arguments to explorer calls in
|
|
|
|
# quotes since they will not be interpreted correctly if they are
|
|
|
|
arg
|
|
|
|
else
|
|
|
|
"\"#{arg.toString().replace(/"/g, '\\"')}\""
|
|
|
|
else
|
|
|
|
cmdArgs = []
|
|
|
|
if /\s/.test(command)
|
|
|
|
cmdArgs.unshift("\"#{command}\"")
|
|
|
|
else
|
|
|
|
cmdArgs.unshift(command)
|
|
|
|
cmdArgs = ['/s', '/c', "\"#{cmdArgs.join(' ')}\""]
|
|
|
|
cmdOptions = _.clone(options)
|
|
|
|
cmdOptions.windowsVerbatimArguments = true
|
2015-05-20 08:02:46 +08:00
|
|
|
@spawn(@getCmdPath(), cmdArgs, cmdOptions)
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
else
|
2015-05-20 08:02:46 +08:00
|
|
|
@spawn(command, args, options)
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
|
2015-05-20 08:02:46 +08:00
|
|
|
@killed = false
|
|
|
|
@handleEvents(stdout, stderr, exit)
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
|
|
|
|
###
|
|
|
|
Section: Event Subscription
|
|
|
|
###
|
|
|
|
|
|
|
|
# Public: Will call your callback when an error will be raised by the process.
|
|
|
|
# Usually this is due to the command not being available or not on the PATH.
|
|
|
|
# You can call `handle()` on the object passed to your callback to indicate
|
|
|
|
# that you have handled this error.
|
|
|
|
#
|
|
|
|
# * `callback` {Function} callback
|
|
|
|
# * `errorObject` {Object}
|
|
|
|
# * `error` {Object} the error object
|
|
|
|
# * `handle` {Function} call this to indicate you have handled the error.
|
|
|
|
# The error will not be thrown if this function is called.
|
|
|
|
#
|
|
|
|
# Returns a {Disposable}
|
|
|
|
onWillThrowError: (callback) ->
|
|
|
|
@emitter.on 'will-throw-error', callback
|
|
|
|
|
|
|
|
###
|
|
|
|
Section: Helper Methods
|
|
|
|
###
|
|
|
|
|
|
|
|
# Helper method to pass data line by line.
|
|
|
|
#
|
|
|
|
# * `stream` The Stream to read from.
|
|
|
|
# * `onLines` The callback to call with each line of data.
|
|
|
|
# * `onDone` The callback to call when the stream has closed.
|
|
|
|
bufferStream: (stream, onLines, onDone) ->
|
|
|
|
stream.setEncoding('utf8')
|
|
|
|
buffered = ''
|
|
|
|
|
|
|
|
stream.on 'data', (data) =>
|
|
|
|
return if @killed
|
|
|
|
buffered += data
|
|
|
|
lastNewlineIndex = buffered.lastIndexOf('\n')
|
|
|
|
if lastNewlineIndex isnt -1
|
|
|
|
onLines(buffered.substring(0, lastNewlineIndex + 1))
|
|
|
|
buffered = buffered.substring(lastNewlineIndex + 1)
|
|
|
|
|
|
|
|
stream.on 'close', =>
|
|
|
|
return if @killed
|
|
|
|
onLines(buffered) if buffered.length > 0
|
|
|
|
onDone()
|
|
|
|
|
|
|
|
# Kill all child processes of the spawned cmd.exe process on Windows.
|
|
|
|
#
|
|
|
|
# This is required since killing the cmd.exe does not terminate child
|
|
|
|
# processes.
|
|
|
|
killOnWindows: ->
|
2015-05-20 08:02:46 +08:00
|
|
|
return unless @process?
|
|
|
|
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
parentPid = @process.pid
|
|
|
|
cmd = 'wmic'
|
|
|
|
args = [
|
|
|
|
'process'
|
|
|
|
'where'
|
|
|
|
"(ParentProcessId=#{parentPid})"
|
|
|
|
'get'
|
|
|
|
'processid'
|
|
|
|
]
|
|
|
|
|
2015-05-20 08:02:46 +08:00
|
|
|
try
|
|
|
|
wmicProcess = ChildProcess.spawn(cmd, args)
|
|
|
|
catch spawnError
|
|
|
|
@killProcess()
|
|
|
|
return
|
|
|
|
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
wmicProcess.on 'error', -> # ignore errors
|
|
|
|
output = ''
|
|
|
|
wmicProcess.stdout.on 'data', (data) -> output += data
|
|
|
|
wmicProcess.stdout.on 'close', =>
|
|
|
|
pidsToKill = output.split(/\s+/)
|
|
|
|
.filter (pid) -> /^\d+$/.test(pid)
|
|
|
|
.map (pid) -> parseInt(pid)
|
|
|
|
.filter (pid) -> pid isnt parentPid and 0 < pid < Infinity
|
|
|
|
|
|
|
|
for pid in pidsToKill
|
|
|
|
try
|
|
|
|
process.kill(pid)
|
|
|
|
@killProcess()
|
|
|
|
|
|
|
|
killProcess: ->
|
|
|
|
@process?.kill()
|
|
|
|
@process = null
|
|
|
|
|
|
|
|
isExplorerCommand: (command) ->
|
|
|
|
if command is 'explorer.exe' or command is 'explorer'
|
|
|
|
true
|
|
|
|
else if process.env.SystemRoot
|
|
|
|
command is path.join(process.env.SystemRoot, 'explorer.exe') or command is path.join(process.env.SystemRoot, 'explorer')
|
|
|
|
else
|
|
|
|
false
|
|
|
|
|
|
|
|
getCmdPath: ->
|
|
|
|
if process.env.comspec
|
|
|
|
process.env.comspec
|
|
|
|
else if process.env.SystemRoot
|
|
|
|
path.join(process.env.SystemRoot, 'System32', 'cmd.exe')
|
|
|
|
else
|
|
|
|
'cmd.exe'
|
|
|
|
|
|
|
|
# Public: Terminate the process.
|
|
|
|
kill: ->
|
|
|
|
return if @killed
|
|
|
|
|
|
|
|
@killed = true
|
|
|
|
if process.platform is 'win32'
|
|
|
|
@killOnWindows()
|
|
|
|
else
|
|
|
|
@killProcess()
|
|
|
|
|
|
|
|
undefined
|
2015-05-20 08:02:46 +08:00
|
|
|
|
|
|
|
spawn: (command, args, options) ->
|
|
|
|
try
|
|
|
|
@process = ChildProcess.spawn(command, args, options)
|
|
|
|
catch spawnError
|
|
|
|
process.nextTick => @handleError(spawnError)
|
|
|
|
|
|
|
|
handleEvents: (stdout, stderr, exit) ->
|
|
|
|
return unless @process?
|
|
|
|
|
|
|
|
stdoutClosed = true
|
|
|
|
stderrClosed = true
|
|
|
|
processExited = true
|
|
|
|
exitCode = 0
|
|
|
|
triggerExitCallback = ->
|
|
|
|
return if @killed
|
|
|
|
if stdoutClosed and stderrClosed and processExited
|
|
|
|
exit?(exitCode)
|
|
|
|
|
|
|
|
if stdout
|
|
|
|
stdoutClosed = false
|
|
|
|
@bufferStream @process.stdout, stdout, ->
|
|
|
|
stdoutClosed = true
|
|
|
|
triggerExitCallback()
|
|
|
|
|
|
|
|
if stderr
|
|
|
|
stderrClosed = false
|
|
|
|
@bufferStream @process.stderr, stderr, ->
|
|
|
|
stderrClosed = true
|
|
|
|
triggerExitCallback()
|
|
|
|
|
|
|
|
if exit
|
|
|
|
processExited = false
|
|
|
|
@process.on 'exit', (code) ->
|
|
|
|
exitCode = code
|
|
|
|
processExited = true
|
|
|
|
triggerExitCallback()
|
|
|
|
|
|
|
|
@process.on 'error', (error) => @handleError(error)
|
|
|
|
return
|
|
|
|
|
|
|
|
handleError: (error) ->
|
|
|
|
handled = false
|
|
|
|
handle = -> handled = true
|
|
|
|
|
|
|
|
@emitter.emit 'will-throw-error', {error, handle}
|
|
|
|
|
|
|
|
if error.code is 'ENOENT' and error.syscall.indexOf('spawn') is 0
|
|
|
|
error = new Error("Failed to spawn command `#{@command}`. Make sure `#{@command}` is installed and on your PATH", error.path)
|
|
|
|
error.name = 'BufferedProcessError'
|
|
|
|
|
|
|
|
throw error unless handled
|