You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I think this program is very necessary but in my case I found multiple problems.
I have run PowerSession with the shell (Nushell), when I give exit, the console crashes leaving it unusable (When using pwsh the console does not crash).
I think the main use of this is not only for recording command executions, but also programs or text editors like helix or neovim.
When running helix, there is a panic in the program (record.rs:134:72), String::from_utf8 section (I have tried with neovim and the same thing happens), rarely in the buffer invalid utf8 sequences are received (but when running normally these programs, the terminal has no complaints, also helix is written in rust, and everything is supposed to be utf8 ).
I changed from String::from_utf8 to String::from_utf8_lossy, to try to run helix again.
When running, it works, but the program is completely distorted, which makes it unusable.
Same procedures with pwsh, the only thing is that when you exit powersession, the terminal still works fine and does not break.
Os: Windows 11
Terminal Emulator: Windows Terminal
Shell: Nushell
Rust version: 1.62.1
The text was updated successfully, but these errors were encountered:
Hello, I think this program is very necessary but in my case I found multiple problems.
When running helix, there is a panic in the program (
record.rs:134:72
),String::from_utf8
section (I have tried with neovim and the same thing happens), rarely in the buffer invalid utf8 sequences are received (but when running normally these programs, the terminal has no complaints, also helix is written in rust, and everything is supposed to be utf8 ).String::from_utf8
toString::from_utf8_lossy
, to try to run helix again.Os: Windows 11
Terminal Emulator: Windows Terminal
Shell: Nushell
Rust version: 1.62.1
The text was updated successfully, but these errors were encountered: