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

command-line is broken on Windows 10 #826

Open
pogrmman opened this issue Dec 27, 2018 · 0 comments
Open

command-line is broken on Windows 10 #826

pogrmman opened this issue Dec 27, 2018 · 0 comments

Comments

@pogrmman
Copy link

pogrmman commented Dec 27, 2018

I'm using Larceny 1.3 on Windows 10 (64-bit), and I've found that the (command-line) procedure from (scheme process-context) only gives (larceny), no matter what the command line arguments are and no matter whether I'm using ordinary command prompt or powershell. (I'd test it on git bash too, but I can't seem to get Larceny to run properly on it).

Here's a quick demo script:

(import (scheme write)
        (scheme process-context))
(display (command-line))

Whether it is invoked on my system with larceny -r7rs test-args.scm -I "%LIBDIR%" -A "%LIBDIR2%" or larceny -r7rs test-args.scm, the only output is (larceny), which is not what it's supposed to do. Even when I associate .scm files with Larceny and invoke it as follows: test-args.scm one two three, I just get (larceny). It also does the same when invoked directly with larceny.bin.exe.

I don't have Larceny on any of my linux systems to test, but I assume it's not broken there.

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

No branches or pull requests

2 participants