pkulak / matui Goto Github PK

We send them, but don't show them, which seems silly.

Currently we just try the first command (which is xdg-open on linux). We should cycle through all of them until one works.

:help or ? or /help or something that shows the keybindings table that's in the README would be great!

Below is the screen log: when crash happened. The screen jumbled up.
OS: ArtixLinux on WSL2.
matui version: 0.4.4.1 from AUR.
terminal: wezterm

thread 'main' panicked at 'byte in
dex 317 is out of bounds of `> <@sharpenedblade:matrix.org> Power?──────────────────────────────────────╯

                           I attempted to replicate the error with> PowerPC (with the backronym Performance Optimization With Enha
nced RISC – Performance Computing, sometimes abbreviated as PPC) is a reduced instruction set computer (RISC) instruction set arch
itecture (ISA) create`[...]', src/widgets/message.rs:405:10
                           ╷                               note: run with `RUST_BACKTRACE=1` environment variable to display a bac
ktrace                     │ Diogenesoftoronto 3 hours ago
      %

Other channels work OK.
Let me know if you need more info.

If I run the app and quit, the terminal seems to be left in a strange stage. It'll show key input codes in stdout randomly as well as pull window focus repeatedly until that terminal is killed.

I'm running sway/wayland on NixOS, it may be particular to my window manager somehow, I'm not sure.

Looking at your exit handling code I can't see any reason why this would be the case so I'll open an upstream bug as well.

Reproduction:
matui -> q -> try to right click in another open window.

Expected:
Right click menu opens and stays open until a selection is made.

Result:
Right click menu either doesn't open at all or opens for just a moment. Typing anything the characters appear in the terminal that shouldn't have focus.