-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
orgmode.org is down #3270
Comments
Melpa seems down too |
I think there should be a timeout on the package repositories so that the basic bootstrap installation works even when orgmode is down. The only way I could fix my attempt at "Update" was by commenting the orgmode repo in core-configuration-layer.el. Without bootstrap, the rollback function does not work either btw., spacemacs never got to a state where the button was active. |
It's back up -- so I am closing this. |
Shall I open a new issue for the timeout? Right now spacemacs' update / rollback mechanism does not work if any of the package sources is down. |
I suppose...i'm just a guy who cares about the project :) |
I think some handling of this eventuality would enhance the spacemacs experience. It's nice when your editor can roll with the punches instead of error out during the first install. Even just a 'don't mind all the red errors, package update is not expected to work right now' to indicate this issue isn't one to spend time diagnosing |
emacs won't start when you have a package marked for install and the repository is down. That's not expected from a text editor.
for a couple of minutes now, and and I can't even quit or do anything with C-c. |
again?
|
Yeah, the same here |
But I also have problems with installing some other packages:
|
FWIW, the usual "quit" key in emacs is C-g. |
Thanks! I was using it for closing menus and canceling actions, but I was not sure if that's the right key 😄 So you can even cancel running functions? |
This is known. Nothing we can do. I am opening this issue if for no other reason, so others do not.
The text was updated successfully, but these errors were encountered: