Reverted base to patch 814.
resubmitting as new PR. I gotta learn to use git better...
Problem: Vim does not restore the screen buffer corectly on exit in the new Windows Terminal
Solution: CONPTY is now stable, can use the built in alternate screen buffer.
Problem: Windows Terminal had unstable color control, see issue #11373
Solution: Dont try and read the old command prompt colortable, use modern VT sequences instead.
https://github.com/vim/vim/pull/11450
(2 files)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@k-takata do the tests just use the changes in my PR, applied to the same faulty 815 in master? If so, then they will still fail, or do the tests somehow also ignore 815?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Ah, the CI checkouts the code with refs/remotes/pull/11450/merge
, so the CI tests the code that is merged with the top of the master branch, which means v9.0.0815 is included.
Sorry for wasting your time. It would be better to rerun the tests after Bram is back.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
OK, thanks, I will dig deeper to see how the testing works, if I can replicate it against my own repo, it could reveal what I want to see for this.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.
@k-takata all good on my end.
https://github.com/zewpo/vim/actions/runs/3336651545
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
closes #11373
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Merging #11450 (9da8298) into master (03d6e6f) will decrease coverage by
0.64%
.
The diff coverage is50.00%
.
@@ Coverage Diff @@ ## master #11450 +/- ## ========================================== - Coverage 81.83% 81.19% -0.65% ========================================== Files 162 152 -10 Lines 189739 179638 -10101 Branches 43134 40776 -2358 ========================================== - Hits 155269 145849 -9420 + Misses 21896 21096 -800 - Partials 12574 12693 +119
Flag | Coverage Δ | |
---|---|---|
huge-clang-none | 82.72% <50.00%> (-0.01%) |
⬇️ |
huge-gcc-none | ? |
|
huge-gcc-testgui | ? |
|
huge-gcc-unittests | 0.29% <0.00%> (ø) |
|
linux | 81.19% <50.00%> (-1.33%) |
⬇️ |
mingw-x64-HUGE | ? |
|
mingw-x86-HUGE | ? |
|
windows | ? |
Flags with carried forward coverage won't be shown. Click here to find out more.
Impacted Files | Coverage Δ | |
---|---|---|
src/term.c | 73.37% <50.00%> (-0.31%) |
⬇️ |
src/if_perl.xs | 54.85% <0.00%> (-17.93%) |
⬇️ |
src/regexp_nfa.c | 80.57% <0.00%> (-9.14%) |
⬇️ |
src/arabic.c | 85.86% <0.00%> (-8.70%) |
⬇️ |
src/typval.c | 84.97% <0.00%> (-8.28%) |
⬇️ |
src/regexp_bt.c | 78.48% <0.00%> (-7.48%) |
⬇️ |
src/vim9execute.c | 83.14% <0.00%> (-7.16%) |
⬇️ |
src/json.c | 77.84% <0.00%> (-5.47%) |
⬇️ |
src/vim9compile.c | 87.07% <0.00%> (-4.73%) |
⬇️ |
src/vim9instr.c | 77.31% <0.00%> (-4.73%) |
⬇️ |
... and 135 more |
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Converting this PR to draft.
There is still some incorrect behavior occuring between some combinations of tgc and nors on the various windows terminal consoles.
I'm assuming set nors
on windows is supposed to act the same as set t_ti= t_te=
on linux. Someone please correct me if I am mistaken.
Well, it is not acting the same as linux in quite a few versions of the windows consoles. I want to make sure it does for this PR, so I will take it out of draft after I have fixed it.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
The issue mentions this PR fixes the problem. I'll await it is no longer marked as draft though.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@brammool Sorry about all the noise from the CI tests. Every time I do a commit to my own branch, it triggers these in your master vim branch, because of this PR. Lesson learned. Will keep it a bit more quiet after this one.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo commented on this pull request.
OK, ready for review
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo pushed 3 commits.
You are receiving this because you are subscribed to this thread.
@zewpo commented on this pull request.
PR ready for review again. Just made another commit, because testing revealed some issues with screen restore still occurred on win 10 - fixed now. tested to be working on win 7, 8, 10, 11 and 11_insider.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo commented on this pull request.
and.. same fix for windows 10 command prompt. Now command prompts restore nicely on all versions of windows 7,8,10,11 & 11_insider, as well as all windows terminals for win 10, 11 and 11 insider. I cant think of what else to test right now. happy for suggestions.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo commented on this pull request.
fixed compile TINY; _rgb warnings [-Wunused-variable], and error: 'p_tgc' undeclared
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
This PR #11450 is failing test Test_popup_and_window_resize() on windows HUGE with non-gui vim. But, this test is passing in my dev environment, which is in sync with this PR. I also installed a fresh win2022, and my code is passing this test on that also. So I am not sure how to debug what is happening here in this CI testing. Any suggestions?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo commented on this pull request.
so... reverted all the screen-restore changes. and just leaving the color fix, to see if that is enough to make CI testing pass.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo commented on this pull request.
OK, so I have simplified this PR, now I'm only submitting changes that fix the color issue. And, I will work on the screen restore separately to tihs PR because it is more complex, and that has been holding me back from finishing this PR.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
I believe this PR is finally ready. I dont know why the macos (huge) build is failing ci test. I dont think that is related to this PR. All other CI tests are now passing.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo commented on this pull request.
fixed regression of Windows 10 Command Prompt rgb color issue, same as WT fix.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@zewpo commented on this pull request.
Able to use vtp_working in more places independent of tgc. No need to check for Win 11, because Win 10 behaves the same.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@brammool It's like rolling dice, trying to get all the CI tests to pass. I'm confident this PR is ready to go. It solves the issue linked. Is there anything else you'd like to see done for this PR?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.