Joe Moon

i think we're gonna need some input from @dmaloney01

well, i think this shows that there could be a compositional way to tackle this problem. I'm thinking along the lines of simply passing through the `Target`'s children component in...

but i agree we don't necessarily need to rush a fix for this, just wanted to track it somewhere

I think there's an emerging composition model that handles this, but i'd like to keep this ticket open until we can collect that somewhere.

pretty trivial to have an intermediate warning period before deprecating `up` and `down`

completion would definitely be nice, but the experience of being able to see the live output of your query is hard to describe  I do recognize that this would...

fwiw, I agree that this is an orthogonal use-case to vim-anywhere's, and something that a clipboard manager like [clipy](https://github.com/Clipy/Clipy) solves quite well.

in fact, i can't think of any reason why we'd want `.jsx.flow` files so maybe an option would be wrong, it should just always rename to `.js.flow`?

I'm not an .mjs user and I'm not sure what the story is for how people use .mjs. I expect for publishing libraries, people still rename to .js, though? Always...

@aerosol i don't think that's related to this issue, pretty sure it's https://github.com/jwilm/alacritty/issues/607, as `winit`'s multiwindow example has the same behavior.