Add new properties for the path and arguments separately

[sindresorhus]

Currently there's process.cmd, but it includes both the path and arguments. Would be useful for sindresorhus/fkill-cli#16 to have separate process.path and process.args properties.

Context:

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.

---

IssueHunt Summary

Backers (Total: $40.00)

• issuehunt ($40.00)

Submitted pull Requests

• #29 Add process.path and process.args
• #1 feat: add process.args output

---

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[sindresorhus]

@coffeedoughnuts @alextes Thoughts on this? Does it make sense? If not, any better suggestions?

[dnbkr]

I think that makes sense; and it's an additive change yes? No won't break anything if theres an issue with it.

[alextes]

Hmm, I'm not that familiar with ps. It has a long manual. I would like to give it another once over to see if there are options to get the distinction command/arguments into one column.
Less is more 😄.

[IssueHuntBot]

@IssueHunt has funded $40.00 to this issue. See it on IssueHunt

[stroncium]

command from ps output can be changed by the process, in which case it usually won't contain arguments and the name might not be what you expect. So I think it's impossible to do do it without causing a lot of pain to devs(and bug reports from them).

Can be done with different API, but that would require using more than just ps and would require writing a whole article on what is what for linux(/similar) process.

[sindresorhus]

I think the conclusion from the issue and many others here is that ps is just junk for programmatic access.

[sindresorhus]

Can be done with different API, but that would require using more than just ps and would require writing a whole article on what is what for linux(/similar) process.

What other API? And why would it require writing a whole article?

[sindresorhus]

Ideally, someone would write a cross-platform binary for this in Rust and we could just bundle some binaries for each platform, and fall back to ps if those fail or something.