You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
macOS ps has a -T flag which is "Display information about processes attached to the device associated with the standard input" (it also has a -t which is "Display information about processes attached to the specified terminal devices.", so -T is basically -t /dev/stdin).
This is really useful, as a way to easily see the parent process list up to the root (login). I use it rather often. And I don't see any way to replicate this in procs. It won't even search on the TTY field even if I pass the exact name shown by procs for my current shell.
I know procs isn't offering flags for filtering, instead doing a "search on keyword", but it really should support this use-case. Either passing a terminal device as a keyword should show all processes associated with that device, or it should support an explicit "search on this field" with e.g. procs tty=/dev/stdin. Probably both.
The text was updated successfully, but these errors were encountered:
macOS
ps
has a-T
flag which is "Display information about processes attached to the device associated with the standard input" (it also has a-t
which is "Display information about processes attached to the specified terminal devices.", so-T
is basically-t /dev/stdin
).This is really useful, as a way to easily see the parent process list up to the root
(login)
. I use it rather often. And I don't see any way to replicate this inprocs
. It won't even search on the TTY field even if I pass the exact name shown byprocs
for my current shell.I know
procs
isn't offering flags for filtering, instead doing a "search on keyword", but it really should support this use-case. Either passing a terminal device as a keyword should show all processes associated with that device, or it should support an explicit "search on this field" with e.g.procs tty=/dev/stdin
. Probably both.The text was updated successfully, but these errors were encountered: