#910: add support for --node flag to pass arguments to node

[michaelficarra]

Usage as follows: coffee --print -e --node "--debug -v --whatever" --lint -b

--node argument takes a string containing an argument list to be passed to node and can be placed anywhere in coffee's argument list.

Documentation will have to be written, I have neither the time nor the patience for that right now.

[satyr]

Isn't it confusing with --nodes?

[michaelficarra]

Eh, the name of the argument doesn't matter to me. --node wouldn't confuse me, but it's an easy change. Have any suggestions?

[TrevorBurnham]

Well, -a/--arguments isn't taken.

[michaelficarra]

That doesn't exactly convey anything about how they're passed to node. arguments is definitely too general of a name.

[TrevorBurnham]

Right, but every single letter in the phrase "node options" is already taken as a single-char flag... and I thought the name of the argument didn't matter to you?

I guess you could call it --argsfornode. People will just use -a anyway.

[michaelficarra]

It doesn't, but if we're trying to pick one that's better than what we have, we should pick an appropriate one. How about --nodejs? --args-for-node isn't bad either. Really, though, it's arbitrary. It could be literally anything at all and I wouldn't have a problem with it.

[jashkenas]

Thanks for the patch, Michael. I've merged (a greatly simplified version of) it to master there:

bc4498e

Closing the ticket.