[sorry, obligatory rotten emacs user who has to turn everything into a minor mode or at least configure emacs-like keyboard nav everywhere on my workstation]
Thanks for this.
I did some cursory poking around, and I'm glad to say, pinrail does not appear to be completely hopeless.
Obviously, (a lot) more work is needed for even a starter emacs-flavored keymap or an emacs-native package to integrate with something like org-agenda.
But again, I'm glad that it does not (initially) appear to me that pinrail has painted itself into a corner in a way that would prevent that work from coming to fruition. And OP even seems amenable to FOSS contributions.
Watching for changes is the agent's job by design. Pinrail doesn't know about your repo. It's a generic review surface for whatever the agent sends, whether that's a diff, an email or an image. The agent knows when its input has changed, so it's the one that resubmits or withdraws the previous submissions. And you can instruct your agent to do so with a prompt, or if you wish do it automatically with a custom script
If you're in the Claude ecosystem, Artifacts can fill a similar purpose. They've gotten really good, if you haven't checked back on them in a while. The recent Docs and Slides update especially is fantastic for working on deliverables in those formats.
very nice. ive been hopping around threads and browser windows trying to find the right PLACES to unblock the ai, its useful to have it in a single app
17 comments
[ 0.28 ms ] story [ 36.2 ms ] threadThanks for this.
I did some cursory poking around, and I'm glad to say, pinrail does not appear to be completely hopeless.
In particular,
- https://pinrail.dev/docs/building/settings-and-keys/#keyboar... suggests the possibility of potentially adding support for emacs-like keymap rebindings (e.g. <n>/<p> to move up and down, rather than <j>/<k>).
- https://pinrail.dev/docs/concepts/trust/#everything-is-on-yo... suggests that the system is meaningfully-pluggable and https://pinrail.dev/docs/building/design/#the-design-languag... suggests to me that that pluggability is not accidental.
Obviously, (a lot) more work is needed for even a starter emacs-flavored keymap or an emacs-native package to integrate with something like org-agenda.
But again, I'm glad that it does not (initially) appear to me that pinrail has painted itself into a corner in a way that would prevent that work from coming to fruition. And OP even seems amenable to FOSS contributions.
I might have to try it.