-
-
Notifications
You must be signed in to change notification settings - Fork 91
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revise handling of paths between Emacs and Racket
Two goals: - Avoid adjusting paths from Racket to Emacs style (on Windows) down in the Racket back end. Do any such adjustment up in Emacs. This adjustment is to do the thing where c:\path\to\foo.rkt is regarded by Enacs as c:/path/to/foo.rkt. - Support the scenario where someone is running Emacs on Windows Subystem for Linux, but instead of running Racket for Linux wants to run Windows Racket.exe. In that case, a Windows path like c:\path\to\foo.rkt is a Linux path /mnt/c/path/to/foo.rkt. In this scenario, we want to adjust paths in both directions. When we tell the Windows Racket.exe to run a .rkt file, we want to translate it from /mnt/c* to c:\*. In the other direction, we want to translate c:\* paths in the response from the `path+md5` command, as well as when using compilation-mode to make error messages and #<path> structs navigable. Fortunately this is easy to do using the WSL command-line utility `wslpath`. - While reviewing compilation-mode, fix and simplify the regexps. They were failing to handle Windows paths starting with drive letters.
- Loading branch information
Greg Hendershott
committed
Feb 21, 2019
1 parent
d1e5a35
commit 978fb68
Showing
10 changed files
with
226 additions
and
83 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.