Skip to content

Fix: SET DEFAULT TO command paths and working directory#1884

Merged
RobertvanderHulst merged 2 commits into
devfrom
fix-vfp-setdefault
Mar 30, 2026
Merged

Fix: SET DEFAULT TO command paths and working directory#1884
RobertvanderHulst merged 2 commits into
devfrom
fix-vfp-setdefault

Conversation

@Irwin1985
Copy link
Copy Markdown
Contributor

SET DEFAULT TO would throw a directory not found exception when passed pure drive letters (ej: C:), SYS(5) results, or MS-DOS shorthands.

  • SET DEFAULT TO now correctly updates the process's working directory (Environment.CurrentDirectory).
  • Root prefixes like \ and C:\ ares now protected from being improperly stripped.
  • Ensures SYS(5) and SYS(2003) inherenlty stay in sync with the new default path.

@RobertvanderHulst
Copy link
Copy Markdown
Member

Irwin,
In the code inside Set() you are generating an error when the directory does not exist but you are not throwing the error.

@RobertvanderHulst RobertvanderHulst merged commit be06f3f into dev Mar 30, 2026
@Irwin1985
Copy link
Copy Markdown
Contributor Author

Irwin, In the code inside Set() you are generating an error when the directory does not exist but you are not throwing the error.

Thanks Robert! Good catch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants