command to return just the keys about feedback HOT 6 CLOSED

@locallycompact I think I'm not really understanding your use-case here.
Are you saying you use multiple feedback loops in the same project and are feeling friction restarting them?
I'd like to see an example of that so I can understand it better.
Running feedback with no arguments already shows you the available loops.

from feedback.

Here is the README from horizon-plutus

You can get live feedback using the feedback tool and
running the following commands in three separate terminals

feedback build

feedback check

feedback gen

feedback gen here will actually retrigger the other two with generated nix code. All three need to be in different windows and concurrently to respond to all events before committing. I can make one nix app button to do this, but ideally without hardcoding the keywords here.

from feedback.

It's common that these repos are checked out on a remote machine as well because the builds are quite heavy, so to resume this project from a laptop, it's four terminals worth of ssh, but programatically a nix app could return the shell command you need to run to do it from one terminal.

from feedback.

@locallycompact

1. I think I get it now. This'll be a common use-case I think so let's think about this together.
2. It looks like we have an opportunity to design composite loops so this can handle all of this inside a single window.
3. We can definitely add some porcelain commands like keys

from feedback.

I think composite loops would suit some people some of the time, but deferring control of the windows to the tiling window manager has other quality of life benefits, like being able to keep one relevant window mirrored in the heads up display of a domain expert or mirrored to a 100 inch screen.

from feedback.

Running feedback with no arguments already shows you the available loops.
You can use yq to do what you want.

from feedback.