A command-line tool that parses bash output, presents a UI to select files, and lets you open them or run commands.
PathPicker is a command-line tool that parses bash output to extract file paths, presents them in an interactive UI for selection, and allows users to open those files in an editor or execute commands with them. It solves the problem of manually picking files from command output like git status, grep results, or find commands.
Developers and system administrators who frequently work in the terminal and need to efficiently select files from command output for editing or batch operations.
It saves time by automating file selection from noisy command output, offers a visual interface in the terminal, and provides flexibility to either edit files directly or run custom shell commands on selected files.
PathPicker accepts a wide range of input -- output from git commands, grep results, searches -- pretty much anything. After parsing the input, PathPicker presents you with a nice UI to select which files you're interested in. After that you can open them in your favorite editor or execute arbitrary commands.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Parses output from diverse commands like git, grep, find, and more, as shown in the examples, making it versatile for terminal workflows.
Provides a curses-based interface for visual file picking from noisy output, enhancing usability over manual parsing.
Allows executing any shell command on selected files using tokens like $F, demonstrated in the advanced functionality section.
Works with Bash, ZSH, and other shells, though with noted limitations in non-Bash environments per the README.
Admits in the 'How PathPicker works' section that it can fail to match valid files like 'test' without directories or extensions, due to restrictive regex.
ZSH lacks features like alias expansion, and other shells may require manual environment variable setup, causing integration headaches.
For systems without package managers, installation involves cloning the repo and creating symbolic links, which can be error-prone compared to one-click installs.