thiagowfx
commented
3 years ago It turns out this feature already exists today, but it is not very discoverable. I wrote this FR and then surprisingly found it right afterwards, but I decided to write it anyway for discoverability purposes:
-ko, --keep-open keep PathPicker open once a file selection or command is performed. This will loop the program until Ctrl-C is used to terminate the
process.In my example above, just do pacman -Ql fpp | fpp -ko.
Let's repurpose this FR instead:
It is trivial to find this feature with fpp --help, which is nicely formatted:
optional arguments:
-h, --help show this help message and exit
-r, --record Record input and output. This is largely used for testing, but you may find it useful for scripting.
--version Print the version of fpp and exit.
--clean Remove the state files that fpp uses when starting up, including the previous input used and selection pickle. Useful when using fpp in
a script context where the previous state should be discarded.
-ko, --keep-open keep PathPicker open once a file selection or command is performed. This will loop the program until Ctrl-C is used to terminate the
process.However, it's very hard to find this feature with man fpp, which is not nicely formatted:
FPP(1) FPP(1)
NAME
fpp - Facebook PathPicker; a command line tool for selecting files out of bash output
SYNOPSIS
usage: fpp [-h] [-r] [--version] [--clean] [-ko] [-c COMMAND [COMMAND ...]] [-nfc]
optional arguments: -h, --help show this help message and exit -r, --record Record input and output. This is largely used for testing, but you may
find it useful for scripting. --version Print the version of fpp and exit. --clean Remove the state files that fpp uses when starting up, including
the previous input used and selection pickle. Useful when using fpp in a script context where the previous state should be discarded. -ko,
--keep-open keep PathPicker open once a file selection or command is performed. This will loop the program until Ctrl-C is used to terminate the
process. -c COMMAND [COMMAND ...], --command COMMAND [COMMAND ...] You may specify a command while invoking fpp that will be run once files have been
selected. Normally, fpp opens your editor (see discussion of $EDITOR, $VISUAL, and $FPP_EDITOR) when you press enter. If you specify a command here,
it will be invoked instead. -nfc, --no-file-checks You may want to turn off file system validation for a particular instance of PathPicker; this flag
disables our internal logic for checking if a regex match is an actual file on the system. This is particularly useful when using PathPicker for an
input of, say, deleted files in git status that you would like to restore to a given revision. It enables you to select the deleted files even though
they do not exist on the system anymore.All flags are in a single line, which makes them hard to read.
So I am repurposing this FR to the following:
Make man page easier to read, put each flag in its own line.
KapJI
Original title: Feature Request: Fpp persistent mode, for opening files in $EDITOR, one-by-one.
This FR is a bit hard to describe, so I'll give a concrete example which is probably easier to understand.
Consider
pacman -Ql fppwhich prints the list of all files installed by thefpppackage in Arch Linux:Now let's say I want to use
fppagainst this very output:This does what you expect: It opens
fppagainst the output above.Now here's my use case: I'd like to interactively navigate that output to open detected files one by one with my favorite
$EDITOR:/usr/bin/fppand pressEnter. That opens it in my$EDITOR.Now here's my feature request:
Observed behavior: After 2), I get back to the command prompt.
Wanted behavior: After 2), I would like to get back to the previous
fppexec, as if I had runpacman -Ql fpp | fppagain. My next action would be to use thefppselection tool to open another file in my$EDITOR(say,/usr/share/doc/fpp/README.md), then close it, then open another file, and so on.In other words, the idea is to maintain the output of a given command fixed, and then make
fppgo continuously back to that output whenever the editor is closed.In that scenario, it would be best if
fppdidn't execute the command (pacman -Ql fpp) again, but rather just saved the output once and then kept going back to it.This could be used for running commands multiple times as well; in my use case above, I open my
$EDITORmultiple times, but I could also want to run different commands several times in a row, with the same output.