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
Failures from EnvironmentSpec.hs tests #6
Comments
Hello, I would say this is not a problem unless you use environment variables. It seems getEnv or getEnvironment on Windows has a different behavior (and Pandoc sees LaTeX formula in their values). I can not reproduce this on Linux and I haven't used Windows for decades (literally, unless when forced at work ;-). Could you run this Haskell script (e.g. with runhaskell)? Be sure there is no confidential or private information in your environment variables before posting the result ;-)
|
I get the following when running on Git Bash (comes with Git
|
Sorry. Yet another copy/paste error...
|
Using Git Bash, I get the following:
Using Powershell Core, I get the following:
|
Well, everything looks fine. I don't understand why Pandoc sees LaTeX formulas in variable values such as "\foo\bar".
|
I get the following using Pandoc
|
ok, with pandoc 2.9.1.1 I have a different behavior. I'll check the latest version of pandoc. |
BTW, did you build abp with stack and LTS-15.12? |
No differences with Pandoc 2.10 (Linux).
|
I'm sorry, I don't know Haskell and am not familiar with the terminology. I like and use |
Here is my Stack version:
|
Same results with the Windows binaries on wine:
|
Okay. Git Bash is the cause of the problem. Powershell Core gives the following:
Using Command Prompt (
|
|
The folder doesn't exist. I didn't create it. For reference, the directory is |
You said PS and cmd.exe works as expected:
but it seems the double slash is not interpreted as in bash.
|
I'm sorry I gave that impression. Yes, it's not what you're getting. Git Bash
Powershell Core
CMD
|
At least, it is more homogeneous ;-) |
Git Bash and Powershell Core give the same result. CMD is on some other planet. I doubt anyone would use CMD to build |
Ok, I finally got the same behavior by disabling the shell interpretation:
So the problem is actually the Windows path separator. I can change the test to put the expected value in a code block so that Pandoc won't interpret it. |
This is due to a default extention of the Pandoc markdown format. Without this it works as expected:
|
I made a quick fix. |
Running
Since it was already installed and I was just making sure the change didn't affect anything, I ran
|
It seems there is a bug in ghc. You can try an older ghc version by changing the repository version in stack.yaml:
|
Now I get this:
The part of
|
Greetings.
I'm using Pandoc
v 2.10
on Windows 10. Runningstack test
gave me the following errors:The rest of the tests ran smoothly. Is this a cause for concern?
The text was updated successfully, but these errors were encountered: