-
-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PID column to processes table #159
Comments
Hey @llchan, thanks for the suggestion. I must admit I'm a little weary of adding stuff like this. I feel these sorts of features are something that could be implemented "on top" of bandwhich. Either requiring it as a library or using raw_mode. If you're looking for something to work on, I'd be happy to suggest some issues that need work, or maybe come up with something together? |
Totally understand. Feel free to stick a help-wanted label on this and leave it for the community to add. I was mostly filing an issue for visibility before tinkering. I'll look into the raw mode or library mode, but given that you've already set up the TUI bits I'd prefer to add it in there rather than starting a new project. Just thinking out loud here, but maybe if you want to set different maintenance expectations for the bandwhich core library and the bandwhich TUI/CLI app, you could consider splitting it into two packages, with a more community-supported workflow for the app layer? |
@imsnif It would be good to see process id (PID) in the table. And for some processes it shows |
Alright - I'd be open to adding the PID to the process table as a separate column. I'm putting a "Help Wanted" on this, but if one of you wants to implement it, let me know and I'll remove it. |
Is this likely to be fixed as part of this issue or would you like a separate issue for this? |
Hey @hulleyrob - I think in cases where we see |
Any news on this? 🤞 |
It would be useful to be able to toggle/flag into a process-level mode to group by pid and display more process-level information like the full command line.
I can give this a shot. I've been looking for a small PR to get some exposure to Rust anyways.
The text was updated successfully, but these errors were encountered: