sindresorhus/fkill-cli

Smart mode

Open

#6 opened on Sep 29, 2015

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (6,764 stars) (211 forks)batch import
:dollar: Funded on Issuehuntenhancementhelp wanted

Description

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

Backers (Total: $40.00)

Submitted pull Requests

Become a backer now!

Or submit a pull request to get the deposits!

Tips

Contributor guide

Tech stack
javascriptnodejs
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.js basicsfkill cli codebaseProcess management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by reviewing the current interactive mode implementation in the fkill cli codebase. The linked PR #1 attempted to group duplicate processes, which may provide insight. Examine how processes are listed (likely using the 'fkill' package) and identify where to filter out helper processes like Google Chrome Helper. The issue suggests a 'smart mode' toggle, so consider whether it should be default and how to implement the toggle.