-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
[0.43] Hugo extended (Windows) doesn't do anything #4919
Comments
So, I have tested that EXE file on Windows 10 (running Parallels on MacOS), so it's at least working for some (me). You can start by telling me what Windows version you are running. Also, judging by havoc the build related troubles this release has given me this weekend and today, I would not hold my breath for a fix from me on this today ... :-) |
Hi. I downloaded the |
But at least it's fast. OK, I will eventually look into it. I may ask one of you for some test help ... |
I'm running Windows 7 SP1 64-bit.
Oh that is totally fine for me. I wasn't expecting a fix today, this week, or even this month. So no problem. :)
I have a flexible schedule so can definitely help with that. Update: I can also loan a Windows 10 computer if needed, so I can test on there as well. Thinking out loud: to isolate the variable that causes this issue, it would probably be more helpful if you (or another contributor) create the builds that we then test? I could try and build Hugo myself, but I haven't done that earlier. So that might introduce more variables/noise than helpful. (Plus I'd be using a different operating system, C/C++ compiler, etc than Hugo's automated releaser uses.) |
OK, I think I know what is happening. I tested the Win binary in Git bash on Windows, where it works. It fails (with an error) in Command. I think I need to compile this as a static binary to make sure everything is there, always. Will update this when you can try. |
It seems you're on the right track. With Git bash I get:
PowerShell gives:
(So nothing happens, a silent fail.) And with command prompt (
And then this prompt pops up: (All these three console tests are with |
@Jos512 I have no pushed a set of new "extended" archives (only the Windows is actually different). I have tested this OK in my "commands console" (where it failed before). Let me know. |
The new archive works for me! Running the Hugo commands in the consoles work (see below). The Sass features themselves also work (the Awesome, thank you very much! 👍 PowerShell:
Git bash:
And the default command prompt (
So 3 out of 3. Great fix, and very fast too! 🙂 (Tested with |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
From the releases page I downloaded
hugo_extended_0.43_Windows-64bit.zip
, unzipped the file, and movedhugo.exe
to my Hugo folder on PATH.However, the
hugo
andhugo server
command don't do anything -- no output nor errors show:The above is the literal output from the console. Since there's no error, Windows does succeed in finding the Hugo executable. But there's no output from the Hugo process.
Things I've tried myself:
hugo.exe
and downloaded zip file. Then download again.hugo_extended_0.43_checksums.txt
(from the releases page), so it doesn't seem the zip file is corrupt.If I download the regular Hugo version (
hugo_0.43_Windows-64bit.zip
from the releases page) and put thathugo.exe
on my PATH, everything seems fine:Perhaps I missed something obvious?
(Sorry to open an issue about Hugo 0.43 so soon after its release. I know how busy you've been. We can put the issue on hold until other Windows users report the same behaviour?)
The text was updated successfully, but these errors were encountered: