Add process.path and process.args

[yaodingyd]

fix #7

[sindresorhus]

Can you confirm this follows the description in #7:

I looked into this more, and I might have a solution to get the arguments without the full path. It seems ps -o pid -o comm returns the full path without arguments and ps -o pid -o command returns with arguments. So we could get both columns and just diff them to get the arguments. I think this should be added as a new property in ps-list. So we could add an args property with just the arguments and a path property with the full path to the binary without arguments, just for completeness.

[sindresorhus]

This is missing docs and TS definitions.

[yaodingyd]

Yes, my implementation follows the suggestion:

1. use comm for path is pretty straightforward
2. args is alias for command. I use value.args.split(value.comm)[1].trim() to achieve diff between comm and args results.

[sindresorhus]

// @stroncium

[sindresorhus]

I would prefer using startsWith and slice here. The current way will fail if the args contain an argument that is the same as comm.

[yaodingyd]

I don't get you. 1) comm only returns the path name; 2) if they are the same, that means there is no argument and it returns empty string

[stroncium]

It doesn't have conflicts with master in terms of code text, but does have them in terms of functionality atm.

[yaodingyd]

@stroncium Could you elaborate?

[stroncium]

@yaodingyd 285f434

Tests fail after merge. And since the changes are only to the case of multiple ps runs(which is left in place for the moment in case parsing single ps run output fails), your code won't even be executed normally.