Running AngryOxide under screen utility is not nice

[PSLLSP]

I tried to run AngryOxide v 0.8.28 under screen command on Linux Mint 22.1 and I see that console is not redrawn correctly, there are characters left from the past and the output is not clean, UI is "broken".

When I run AngryOxide directly from the console, I do not see those issues.

Other interesting point is that when I connect to this machine from other PC over ssh and then "hijack" screen session with AngryOxide (screen -dx), I see clean output, the issue is not there. BUT, when I stop and start AngryOxide in this remote session, I see the issue! It looks like the issue is related to start of AngryOxide...

Another interesting point is that when I try to start AngryOxide under tmux session then I do not see this issue.

Steps to replicate:

1. from terminal console start screen
2. start AngryOxide from screen session, sudo ./angryoxide --interface wifixyz
3. watch console for defects in the user interface
4. wait some time, observe terminal
5. resize terminal, AngryOxide is forced to redraw screen and the look of UI is fixed!

Advantage of screen is that it can be controlled from remote computer, it is easy to switch between local session and remote session... screen tutorial on YouTube.

$ screen -v
Screen version 4.09.01 (GNU) 20-Aug-23

$ ./angryoxide --version
AngryOxide 0.8.28

$ tmux -V
tmux 3.4

AngryOxide started directly from the console, UI is nice:

AngryOxide started from screen session, UI is "broken":

---

When terminal window with AngryOxide is resized, AngryOxide redraws screen and the UI after this step look nice. This could be a key to address this issue.

https://stackoverflow.com/questions/34913611/ncurses-good-practices-clear-screen-with-windows

Many other applications based on ncurses running know that key CTRL+L should redraws the screen. AngryOxide ignores this key combination...

---

Resizing console windows triggers other issue. It is visible at "Status" page, color attribute could be applied to wrong place, after this many areas in the terminal have wrong color. It looks like some race condition bug...

Several examples of situation when wrong color attributes were applied when terminal window was resized:

[Ragnt]

Something about how screen is rendering (or parsing/proxying) seems to not be compatible with how crossterm-rs (the underlying library that is being used for the TUI) is doing things. The fact that running it inside of SSH works is strange, however.

Even other applications that use rawmode, alternate screen, and ANSI color break inside of screen (albiet, not as badly). This leads me to recommend avoiding it, and just utilizing a different multiplexer (such as tmux) instead to meet this use case. I personally run AO inside a remote detached session using tmux all the time.

AngryOxide is at a dev-stop (with the exception of universal breaking bugs) while I work other projects and chip away at the rewrite. I would not consider this universally breaking as this is the first time it has come up and there are alternatives.

Despite this, I do appreciate your detailed bug report.

[PSLLSP]

Other issue with AngryOxide UI is that I cannot use mouse to select text and copy it to a mouse clipboard. I run terminal on Linux...

[Ragnt]

Try to hold shift while you drag/select. As a TUI that updates the UI rapidly, there are limitations. I try to mitigate them by implementing the c/C key binds and having the UI pause to freeze it in position, but some terminal emulators still require you hold shit to select raw characters.

…

On Thu, Feb 13, 2025 at 8:51 AM, PSLLSP ***@***.***(mailto:On Thu, Feb 13, 2025 at 8:51 AM, PSLLSP <<a href=)> wrote: Other issue with AngryOxide UI is that I cannot use mouse to select text and copy it to a mouse clipboard. I run terminal on Linux... — Reply to this email directly, [view it on GitHub](#52 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AF4YMEVYAAGMJZYHTKRUCC32PSPO7AVCNFSM6AAAAABW65E2DSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJWGY3DENBYGY). You are receiving this because you commented.Message ID: ***@***.***>