Make hologram works on Windows

[gagarine]

Make hologram works on Windows

[gagarine]

I think the issue is on pygments pygments/pygments.rb#110

[jdcantrell]

Ah good to know. We have another open issue regarding windows compatibility. It's on my plate to look at it.

[gagarine]

Can I ask why are you using pygments? I mean where it's used... Can this be an optional dependency?

[jdcantrell]

It's used for syntax highlighting whenever you use a code block in markdown. I'm planning on starting work on a 2.0 release that would remove pygments completely as a dependency (and then those who choose to use it can use a custom renderer with it). That doesn't help in the short term though. I'll look into seeing if/how we can make it be an optional dependency for the 1.1 release.

[gagarine]

Ok. Perhaps also simply changing the version you depend on like pygments/pygments.rb#110

[OlsonAndrewD]

I got this same error with Ruby 1.9.3 on Windows, with no Powershell. I was able to make it go away by changing this:

```html_example
<div class='alert'>Hello</div>
```

to this:

```html_example <div class='alert'>Hello</div> ```

Unfortunately, the "html_example" appears in the generated doc.

[OlsonAndrewD]

Actually my error was a little different.

C:/Ruby/Ruby193/lib/ruby/gems/1.9.1/gems/posix-spawn-0.3.8/lib/posix/spawn.rb:162: warning: cannot close fd before spawn
'which' is not recognized as an internal or external command,
operable program or batch file.
?[32m(?°?°)??[0m?[31m? ??? ?[0m?[31m Build not complete.?[0m
 Could not load config file, try 'hologram init' to get started

[vinayraghu]

+1 Please help fix on windows
Is there any known workaround? @OlsonAndrewD 's solution doesn't work for me.

My error is as follows

c:/Ruby193/lib/ruby/gems/1.9.1/gems/posix-spawn-0.3.8/lib/posix/spawn.rb:162: wa
rning: cannot close fd before spawn
'which' is not recognized as an internal or external command,
operable program or batch file.
←[32m(╯°□°）╯←[0m←[31m︵ ┻━┻ ←[0m←[31m Build not complete.←[0m
 Could not load config file, try 'hologram init' to get started

[thedaviddias]

Please help, I have the same issue on windows with ruby 1.9.3...

[aflanagan]

As @gagarine mentioned, this looks like a problem with the pygments gem (which is a dependency of hologram). It's also affecting jekyll on windows.

We are thinking about moving away from pygments for the 2.0 release, but that is probably a ways off still.

[gagarine]

I think the good way would be to move from pygments.rb to https://github.com/jneen/rouge . This should not be that hard.

[jdcantrell]

I tested this out tonight and with the 1.2 release we now work on windows!

[GaryJones]

I've got this working for Mac, but another user using the same repo setup on Windows is still having trouble, even with 1.2.0.
Getting the same build failed errors as above, and notice about doing hologram init. Also, the documentation_assets, referencing cortana, are not being copied into the styleguide directory, so although it's partly working despite the warnings, the style guide doesn't look like it should.

documentation_assets: assets/bower/cortana doesn't seem to work for Windows (fine on Mac) - case matches the path in the repo.
custom_markdown: assets/bower/cortana/CortanaMarkdownRenderer.rb is copied fine.

Maybe documentation_assets are not having the slashes reversed or something daft to satisfy Windows?

[jdcantrell]

We just released version 1.3.0 to rubygems.org, could you test with the new version and report back? I know there were a few updates that should make Windows users much happier.

[robincornett]

Windows user reporting in. 1.3.0 seems to have helped a lot. The new output looks like:

I do not know what the warning means but hopefully it's helpful to you.

[jdcantrell]

The warning is from hologram parsing your source code, you have two documentation blocks with the same name ('d-small'). That said if your output is what you're looking for it, it's not a big worry.

Thanks for the update though, I'm glad to hear it's working better.

[GaryJones]

Just confirming (Robin and I are working on the same project), and yes, there are indeed two documentation blocks with the name d-small; useful warning!