Fzf – the basics part 1 – layout

Re:Fzf – the basics part 1 – layout by jugjug on Friday February 05, 2021 @08:57AM (#26036339)

I love fzf as well. I use it with the npm package manager to select the script to run (we have an app with 20+ scripts):

    npmrf () {
        local script
        script=$(cat package.json | jq -r '.scripts | keys[] ' | sort | fzf)  && npm run $script
    }

Another usecase is tracking hours with Clockify. I was frustrated opening up the web everytime, so I wrote a script using fzf, httpie and jq. Love it now. [1]

[1]: https://marcel.is/tracking-hours/

[ Parent | on HN ]

Re:Fzf – the basics part 1 – layout by mssundaram on Friday February 05, 2021 @09:54AM (#26036913)

That's a great idea, thanks. Do you know how to get it to show the preview window with the script value? Sometimes I need to explore which script task I need based on what it does

[ Parent | on HN ]

Re:Fzf – the basics part 1 – layout by zjmil on Friday February 05, 2021 @02:32PM (#26040257)

You could do something like this (not super thoroughly tested):

  npmrf () {
    local script
    script=$(jq -r '.scripts | to_entries[] | "\(.key) => \(.value)"' < package.json | sort | fzf | cut -d' ' -f1) && npm run "$script"
  }

It uses jq's to_entries to pull out the script/command key pairs and then just cuts out the script name after you choose the command (assumes the command name doesn't have spaces).

[ Parent | on HN ]

Re:Fzf – the basics part 1 – layout by jugjug on Friday February 05, 2021 @11:07AM (#26037774)

Yeah, that would be nice. I don't know though from the top of my head.

[ Parent | on HN ]