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
Hello,
using version 0.11.3 (from Homebrew on MacOSX Catalina 10.15.7) I can currently filter output using both --only and a keyword but just indipendently.
To clarify the issue I get these outputs for these commands:
But when I ask procs --only PID -- launchd or procs --only PID launchd or procs launchd --only PID or procs --only PID -- '*launchd*' I just get:
PID:▲
I tested it with both bash-3.2 and zsh 5.8 (x86_64-apple-darwin19.6.0) (with on-my-zsh) and both Terminal.app and iTerm2 to ensure that this is not a strange globbing issue.
I tested version 0.11.4-pre building it from source on ArchLinux too (Kernel 5.10.5-arch1-1) and the issue persists (testing it with systemd not launchd ofc)
Apart for this tiny issue everything works flawlessly and I love procs 😍
Thanks!
The text was updated successfully, but these errors were encountered:
I can confirm this issue running on Linux Xubuntu 21.04 and building from source with cargo build .... It would be great to use procs to be able to return the PIDs for targeted processes like ps --no-header --only pid base
Hello,
using version 0.11.3 (from Homebrew on MacOSX Catalina 10.15.7) I can currently filter output using both
--only
and a keyword but just indipendently.To clarify the issue I get these outputs for these commands:
procs launchd
orprocs -- launchd
:procs --only pid
(pid written in any case):But when I ask
procs --only PID -- launchd
orprocs --only PID launchd
orprocs launchd --only PID
orprocs --only PID -- '*launchd*'
I just get:I tested it with both
bash-3.2
andzsh 5.8 (x86_64-apple-darwin19.6.0)
(with on-my-zsh) and bothTerminal.app
andiTerm2
to ensure that this is not a strange globbing issue.I tested version
0.11.4-pre
building it from source on ArchLinux too (Kernel 5.10.5-arch1-1) and the issue persists (testing it withsystemd
notlaunchd
ofc)Apart for this tiny issue everything works flawlessly and I love procs 😍
Thanks!
The text was updated successfully, but these errors were encountered: