Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New yamatanooroti for win #776

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

Conversation

YO4
Copy link
Contributor

@YO4 YO4 commented Nov 4, 2024

This is part of supporting windows for reline CI using yamatanooroti.
This PR follows PR#775.
This PR contains the following test_yamatanooroti changes.

  • Change codepage when needed. (depend to yamatanooroti api change)
  • Changes to avoid affecting the behavior of windows console.
    The merge requires finalizing api changes to the code page settings on the yamatanooroti side.

@YO4 YO4 marked this pull request as draft November 4, 2024 13:16
@YO4 YO4 force-pushed the new_yamatanooroti_for_win branch from 5ab50e3 to f7d6b24 Compare November 7, 2024 13:56
YO4 added 3 commits December 17, 2024 18:47
…BCS chars

test_yamatanooroti: change console condepage on legacy conhost even if only display DBCS characters (no input DBCS)
omit if changing codepage failed
writing DBCS characters to legacy console displays '?' character. confirmed on Windows 11 dev VM (that has no codepage 932 on legacy mode enabled conhost)
omit if changing codepage failed
because of console input (using ansi codepage) that has coderange out of console codepage is useless
Non VT sequence supporting windows console has forced newline output when writing rightmost column of line. This may appear as an additional line break.
Clearing screen to avoid this environment dependent behavior.
@YO4 YO4 force-pushed the new_yamatanooroti_for_win branch from f7d6b24 to b383a37 Compare December 17, 2024 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant