Darren Schroeder
Darren Schroeder
Sounds good. Thanks for the suggestion.
Good idea. They should be mentioned.
ya, that would be cool to have space expand it. i really wish we could combine this stuff with an fish abbrev-like functionality. they're very similar, one gets that last...
@orr721 I believe this works ``` { name: insert_last_token modifier: alt keycode: char_. mode: [emacs vi_normal vi_insert] event: [ { edit: InsertString, value: " !$" } { send: Enter }...
> yes! I'm on a mac though, so I had to change the modifier to control and keycode to other key. but finally it works, thank you!👍 been there. done...
My guess is that this was related to redrawing the prompt with every keystroke, which reedline also probably shouldn't be doing. On Wezterm on Windows I don't think it matters,...
That's why I think this is similar to WezTerm on Windows. It's something to do with the pty iirc but I think the main culprit is nushell drawing the prompt...
Technically `path` is not a type. You can see the nushell types here: https://github.com/fdncred/nushell/blob/main/crates/nu-protocol/src/ty.rs#L9-L37 It is a `SyntaxShape` as you can see here: https://github.com/fdncred/nushell/blob/main/crates/nu-protocol/src/syntax_shape.rs#L7-L119 and here: https://github.com/fdncred/nushell/blob/main/crates/nu-parser/src/parser.rs#L2685-L2765 I'm not sure...
> In the default config the example keybindings all use lower case names for event stuff, but keybindings list uses PascalCase for things. I agree with this point. When I...
I "borrowed" that code from a crossterm example and it's super helpful because, like you say, all terminals don't see all keystrokes, which is why I added it moons ago....