Timeline for Vim over SSH problem when connecting from a RHEL 8 to a remote macOS Sonoma
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 11, 2024 at 6:47 | history | edited | Fravadona | CC BY-SA 4.0 |
deleted 31 characters in body
|
| Dec 10, 2024 at 9:30 | vote | accept | Fravadona | ||
| Dec 10, 2024 at 9:30 | history | edited | Fravadona | CC BY-SA 4.0 |
added 1714 characters in body
|
| Dec 9, 2024 at 12:18 | comment | added | Fravadona |
@terdon The default TERM on macOS Sonoma is also xterm-256color, so it is overwritten to screen when I open a Terminal... A local Vim doesn't doesn't display junk characters but the colors are a little awful...
|
|
| Dec 7, 2024 at 13:35 | history | edited | Fravadona | CC BY-SA 4.0 |
edited body
|
| Dec 7, 2024 at 13:18 | comment | added | Fravadona | @terdon No I'm not using any terminal multiplexer here | |
| Dec 7, 2024 at 13:18 | comment | added | Fravadona |
@terdon Well, I'm also using that computer directly (not through SSH). Next week I'll check what TERM is set when I open a Terminal on it; I'm pretty sure it isn't screen.
|
|
| Dec 7, 2024 at 13:11 | comment | added | terdon♦ |
Why not just TERM=screen? Why only do it if it is set to one specific value? And are you using screen or tmux here? I get the same issue when I open an existing screen (byobu, actually, but using screen as a backend) session. Are you getting it without screen being involved?
|
|
| Dec 7, 2024 at 13:03 | history | answered | Fravadona | CC BY-SA 4.0 |