mirror of
https://github.com/rivo/tview.git
synced 2026-04-26 21:35:54 +03:00
[GH-ISSUE #476] Application colors changed after using app.Suspend() to call Neovim #345
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tview#345
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @khughitt on GitHub (Jul 19, 2020).
Original GitHub issue: https://github.com/rivo/tview/issues/476
Greetings!
Apologies for the barrage of issues over the past few days.. 😅
One more issue I noticed that I thought I would report is a change colors after using
Suspend()to temporarily launch a Vim/Neovim instance:The above video shows the issue for both Vim/Neovim.
To Reproduce
In a separate application where I am using go-term-markdown to render a markdown document inside a grid element, the effect is even more pronounced.
There, the background color for all "blank space" areas in between text changes to black, which starkly contrasts against the grey background in areas where this is text, resulting in an uneven "striped" pattern.
In both cases, it seems like after exiting Nvim/Vim and returning to tview, the original true colors are swapped for something like 256-bit color equivalents.
Any ideas what could be causing the issue / if there is any way to workaround this?
Any advice would be greatly appreciated!
System Info
@rivo commented on GitHub (Sep 15, 2020):
I don't know what's causing this. It's also beyond the scope of
tview. You may want to get in touch with the maintainer oftcell(@gdamore) and ask how running a different application inbetweentcellsessions (whichtviewis built upon) affects terminal colours.@gdamore commented on GitHub (Sep 15, 2020):
There have been API improvements in tcell v2 which should help here.
@khughitt commented on GitHub (Sep 15, 2020):
Okay great! I'll keep an eye out for that. Just let me know if you would like any help with testing.