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

"doom install" stuck on windows. #2513

Closed
skywind3000 opened this issue Feb 10, 2020 · 3 comments
Closed

"doom install" stuck on windows. #2513

skywind3000 opened this issue Feb 10, 2020 · 3 comments
Labels
invalid Unactionable, unrelated, inappropriate, or a pilot error module:core:cli Pertains to the `$ doom` script os:windows Pertains specifically to Windows re:networking Has to do with connection issues or proxies

Comments

@skywind3000
Copy link

What did you expect to happen?

doom install should work on windows.

What actually happened?

it was unresponsive after:

Installing Doom Emacs!
> Creating .doom.d/
   Created .doom.d/
- Creating .doom.d/init.el
Done!
- Creating .doom.d/config.el
Done!
- Creating .doom.d/packages.el
Done!

Additional details:

Last night for sleeping, I cloned a fresh doom into ~/.emacs.d and ran doom install:

freeze

And this morning, it still stucked at this point. CPU usage of emacs.exe keeps at a high level of 12% (8 cores).

Than I pressed CTRL+C and gave up.

How to acquire a backtrace:
https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#how-to-extract-a-backtrace-from-an-error

Steps to reproduce:

  • windows, follow the installation instruction:
git clone https://github.com/hlissner/doom-emacs ~/.emacs.d
~/.emacs.d/bin/doom install

System information:
Windows 10, Emacs 26.3

@skywind3000 skywind3000 added the is:bug Something isn't working as intended label Feb 10, 2020
@hlissner hlissner added help wanted Cannot be resolved without outside help module:core:cli Pertains to the `$ doom` script re:install Has to do with installing or setting up Doom for the first time os:windows Pertains specifically to Windows labels Feb 10, 2020
@hlissner
Copy link
Member

This is an odd one. I'm not sure how to go about debugging it, since I don't have a windows machine handy. I pushed a fix for a separate issue in #2556. Could you update and see if that resolves this one?

@skywind3000
Copy link
Author

skywind3000 commented Feb 21, 2020

Yes, it was my fault. I was running emacs behind a firewall, then, following code fixed the problem:

set HTTP_PROXY=127.0.0.1:1080

But I could realize network and try this earlier if doom can warn me http timeout.

@skywind3000
Copy link
Author

skywind3000 commented Feb 21, 2020

Currently, it works very well.
It can be closed now.

@hlissner hlissner added invalid Unactionable, unrelated, inappropriate, or a pilot error re:networking Has to do with connection issues or proxies and removed help wanted Cannot be resolved without outside help is:bug Something isn't working as intended re:install Has to do with installing or setting up Doom for the first time labels Feb 21, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
invalid Unactionable, unrelated, inappropriate, or a pilot error module:core:cli Pertains to the `$ doom` script os:windows Pertains specifically to Windows re:networking Has to do with connection issues or proxies
Projects
None yet
Development

No branches or pull requests

2 participants