Darren Schroeder

Mitchell's prompt is from fish. My prompt is from oh-my.nu in the nu_scripts/modules/prompt folder and this is in the config.nu. ```nushell # prompt use "modules/prompt/oh-my.nu" git_prompt $env.PROMPT_COMMAND = {|| (git_prompt).left_prompt...

Further research from fish-shell's `fish_handle_reflow` environment variable. The reflow issue: https://github.com/fish-shell/fish-shell/issues/7491 The reflow PR: https://github.com/fish-shell/fish-shell/pull/7623 And the latest version of these changes. https://github.com/fish-shell/fish-shell/blob/b1a1a3b0a72211310e96d5f14631519df8bd3438/share/functions/__fish_config_interactive.fish#L240-L267 Interesting enough, this is all handled in...

closed by https://github.com/nushell/reedline/pull/857

On Windows, I get the response from the terminal. Then I can clear the line and type other commands, hitting enter after each one, without issue. Have you tried on...

If you're going to query the terminal you should use the new `term query` command. It's specifically built for this type of thing. However, it's not published yet but you...

I moved it here to reedline.

Indeed, it's a lot of work. If someone wants to volunteer to do this we could add tags.

That looks to be a crossterm error message. https://github.com/crossterm-rs/crossterm/blob/e104a7cb400910609cdde36f322e3905c4baa805/src/cursor/sys/unix.rs#L50

Not really. It looks to me like crossterm is asking the terminal for the cursor position, waits 2 seconds without a response and then times out with that error.

Me either. It may be worth asking on the crossterm repo. I just looks like if crossterm fails to get a lock for the event reader it would fail. I'm...