![]() While I haven't tried every possible Windows terminal software, my usual test scenarios include Windows Terminal (sometimes preview too), Alacritty, and WezTerm. I'm definitely not trying to lay this problem at your feet for fixing and running away, but I wanted to be clear about what I see as it's a little bit different than what is posted above. Out of respect for you, I created this gif to show you what I see in Windows using WezTerm. We haven't seen anything as serious as how WezTerm reacts on windows. We have an issue open already here microsoft/terminal#13710. We definitely see a pretty serious flicker with Windows Terminal Preview but not in Windows Terminal, nor Alacritty. I would recommend opening an issue at to get input from the team that owns ConPTY who can perhaps advise on how to deal with Thanks a bunch for chiming in and giving us your perspective!! Thus, rather than being either a shell, or a programming language, Nushell connects both by bringing a rich programming. ![]() The goal of this project is to take the Unix philosophy of shells, where pipes connect simple commands together, and bring it to the modern style of development. I suspect that if you use that to run a remote nushell with the same configuration you won't be able to reproduce this problem. Hello, and welcome to the Nushell project. In wezterm, you can use wezterm ssh host to use its integrated ssh client to connect to a remote system and bypass using the ConPTY layer. What I suspect may be happening here is that you are tickling an edge case that causes conpty to emit something unexpected that results in the output shown above.Įarlier comments indicate that this isn't a wezterm issue and that it manifests in other windows terminals. That processed stream is what wezterm, conemu and alacritty see. The ConPTY layer needs to translate from the stream of escapes and apply that data to the internal windows console screen model, and then translates from that to a stream of output escapes. Run`, i.e.The way that PTYs work on Windows is a bit different from unix systems. ``, `ls ` and `str ` only work with the second `cargo ![]() `cargo run` to load the user configuration `cargo run -n` to load Nushell without any configĬrates/nu-utils/src/sample_config/default_config.nu -env-configĬrates/nu-utils/src/sample_config/default_env.nu` to load the default The user to use the default config files or add the followingįrom the root of the repo, one can try `` in each of the following This PR should allow tab completion cycling everytime, without requiring Nushell without requiring any user configuration □ I have been annoyed enough by this missing feature, so let's add that to Tried with -config "" to ignore my config, but it is the same behavior. ❯ version | transpose key value | to md -pretty key This was the behavior before version 0.71. Shift + Tab moves in the other direction, but Tab seems to be broken! It should go to the next completion. Tab completion seems to be broken starting with version 0.71.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |