Johannes Altmanninger

We could also have left the behavior of `cancel-commandline` intact but my assumption is that it's a net positive. I don't know if the "keep abandoned commands in scrollback" workflow...

I see that makes sense. I would probably use the kill ring (`ctrl-k` etc.) for that, or a separate window with a text editor, since using the mouse to access...

better naming at least. Actually I think it would be preferrable to make the default binding something like `bind ctrl-c 'commandline ""'` (because that's the most obvious way). Today it's...

On Sat, Jan 11, 2025 at 02:18:01AM -0800, Fabian Boehm wrote: > So, what we could do here is either rename the things or back out #10213 entirely. I don't...

Yeah I agree. Changing `cancel-commandline` was quite reckless, in that change I mainly focused on matching pre-existing behavior; (though again the `fish_cancel` event should probably be phased out)

thanks for the great bug report, the reproduction steps will be handy. > panicked at src/text_edit.rs:376:22: This is very likely fixed in 5fedebd0 (Better name for converting LSP character to...

I don't have a complete solution yet but we could at least allow colons in filenames that don't collide with `(\d+):(\d+)?`. I.e. `/sys/class/devlink/platform:PNP0C32:00--wmi:64AB4FE5-E5DA/`. Does this happen to work for your...

Right that scenario is not fixed. My (manual) workaround is a wrapper around `gf` that 1. automagically selects the surrounding word (delimited by whitespace) 2. tries to match filename with...

foot implements the "explicit-width" part of that protocol. I'm interested in that because it could allow us to get rid of some `wcwidth()` glitches.

On Tue, Jan 21, 2025 at 07:45:11PM -0800, Screwtapello wrote: > The "cycle through completion candidates" keys (`` and `` by default) also cycle through the "no completion selected" state....