Skip to content
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

Smart mode #6

Open
sindresorhus opened this issue Sep 29, 2015 · 7 comments
Open

Smart mode #6

sindresorhus opened this issue Sep 29, 2015 · 7 comments
Labels
💵 Funded on Issuehunt This issue has been funded on Issuehunt enhancement help wanted

Comments

@sindresorhus
Copy link
Owner

sindresorhus commented Sep 29, 2015

Issuehunt badges

Currently there's a lot of useless processes in interactive mode that I would never care to close. Like all the Chrome helper processes. These makes it harder to find processes I actually want to close. With some simple heuristics I think we could hide away most of those useless processes.

Should smart mode be default when using the interactive UI?

What processes needs hiding?

  • Google Chrome Helper (done)
  • 2BUA8C4S2C.com.agilebits.onepassword-osx-helper
  • -zsh

There is a $40.00 open bounty on this issue. Add more on Issuehunt.

@sindresorhus
Copy link
Owner Author

Maybe we could group processes with the same name into one? And when selected, it would open a menu with an option to kill all or select individual processes.

@ishanjain28
Copy link

I think I found something that can help but It'll probably need some changes in ps-list.

Chrome creates a seperate process for every tab and extension and all these processes run with some options as shown in image.
But it also starts one process that runs without any options and killing this process closes Google Chrome Completely.

I was thinking that may be we can modify the ps-list a bit and send another parameter in response that contains the arguments of a process.
And then in fkill we can remove all chrome processes that were started with some argument and only show the ones that weren't started with an argument.

If the user kills this process it'll close chrome and it'll not show 50 chrome processes and close the window associated with that process.

screenshot from 2017-03-02 15-37-15

@sparty02 sparty02 mentioned this issue Mar 2, 2017
@sindresorhus
Copy link
Owner Author

I was thinking that may be we can modify the ps-list a bit and send another parameter in response that contains the arguments of a process.

ps-list already returns that.

And then in fkill we can remove all chrome processes that were started with some argument and only show the ones that weren't started with an argument.

It's possible for users to start Chrome with arguments, like specifying where to put the profile data or open Incognito directly, so that wouldn't work, but I guess we could easily special case Chrome and detect its helper processes and hide them.

@sindresorhus
Copy link
Owner Author

but I guess we could easily special case Chrome and detect its helper processes and hide them.

This is done in 3.5.0. It now hides any helper processes.

@IssueHuntBot
Copy link

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

@stroncium
Copy link
Contributor

What is the status of this issue?

@issuehunt-oss issuehunt-oss bot added the 💵 Funded on Issuehunt This issue has been funded on Issuehunt label May 10, 2019
@sindresorhus
Copy link
Owner Author

@stroncium The following needs to be resolved: #6 (comment)

Having a sub-menu for identically named processes would also let us add an entry to delete all processes with the same name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💵 Funded on Issuehunt This issue has been funded on Issuehunt enhancement help wanted
Projects
None yet
Development

No branches or pull requests

4 participants