652f4d6d09
Side-effect of configuring a Python environment while building the mech spec tooling. Harmless to keep: the scripts are standard-library only and need no venv, so this just stops VS Code re-prompting. Worth knowing that this same file sets files.eol to CRLF workspace-wide, which is right for the game content but also applies to newly created files -- it is why the MECHSPECSHEET scripts were born with CRLF shebangs and had to be normalised to LF before they would execute directly. Co-authored-by: Claude Opus 5 (Anthropic) <noreply@anthropic.com> Co-authored-by: GitHub Copilot <copilot@github.com>
21 lines
766 B
JSON
21 lines
766 B
JSON
{
|
|
// Legacy source files use CP949 (Korean Windows encoding, superset of EUC-KR).
|
|
// VS Code defaults to UTF-8, which silently corrupts the Korean comment bytes
|
|
// on save. Setting encoding to cp949 here preserves them exactly.
|
|
"files.encoding": "cp949",
|
|
|
|
// Let VS Code try to detect encoding per-file, falling back to cp949 above.
|
|
"files.autoGuessEncoding": true,
|
|
|
|
// Preserve the original Windows CRLF line endings (Git's * -text in
|
|
// .gitattributes also prevents conversion, but this keeps VS Code consistent).
|
|
"files.eol": "\r\n",
|
|
"python-envs.pythonProjects": [
|
|
{
|
|
"path": ".",
|
|
"envManager": "ms-python.python:venv",
|
|
"packageManager": "ms-python.python:pip"
|
|
}
|
|
]
|
|
}
|