Natalie Klestrup Röijezon
Natalie Klestrup Röijezon
In a green field I think that makes sense, but I don't think it's worth breaking the old config value "just" for this.
Sorry about the delay, got distracted by other stuff.
This issue has been migrated to Codeberg: see https://codeberg.org/natkr/flickboard/issues/230 for any further discussion!
I know. This is about any command running in a `loop`, not just `echo` specifically. Again, the `print` workaround *is there*, it's just a surprising footgun until you find out...
@pplanel You can pipe the `ps` into `print`: ```nushell loop { ps --long | where name == rust-analyzer | print; sleep 1sec } ```
Very :+1: on this from me.
_Why not both?_
Hm, not quite sure I see the intended use case. You'd still need to take a direct dependency on k8s-openapi to set the k8s compat level feature, right? And we...
IMO the k8s-pb saga is another case for reducing the specific coupling to k8s-openapi, but I guess some of that also has to do with how that integration would end...
Hm, I agree that the currently UX for it is far from ideal. It might make more sense to have an explicit drag-and-drop-to-resize-and-reposition UI (like GBoard)...