You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 19, 2023. It is now read-only.
I'm sorry, this is the worst kind of bug report but figured I should pass it on: we had one user with a Windows 8.1 laptop of unknown prior state who ran the Windows installer but did not end up with nano installed in the normal path under ~/.swc. Uninstalling and rerunning the installer worked to resolve it.
I suspect what may have happened is that the installer encountered an error while downloading the various packages because the attendee's laptop dropped off of the guest wifi at some point in the middle of this process. I was thinking that one way to handle this better could simply have been preventing the installer's terminal window from closing if any stage fails to exit cleanly so the error would have been more obvious.
The text was updated successfully, but these errors were encountered:
I was thinking of the same. At a recent workshop we had several instances of sqlite3 not being added to PATH (swcarpentry/sql-novice-survey#177), and at least one case where the installer didn't install anything. Of course we were a bit stressed, since we tried to get the workshop started, so we didn't get to dig into why things failed, but if the terminal window had remained open it might have provided an opportunity to quickly get a hint of what went wrong.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm sorry, this is the worst kind of bug report but figured I should pass it on: we had one user with a Windows 8.1 laptop of unknown prior state who ran the Windows installer but did not end up with
nano
installed in the normal path under~/.swc
. Uninstalling and rerunning the installer worked to resolve it.I suspect what may have happened is that the installer encountered an error while downloading the various packages because the attendee's laptop dropped off of the guest wifi at some point in the middle of this process. I was thinking that one way to handle this better could simply have been preventing the installer's terminal window from closing if any stage fails to exit cleanly so the error would have been more obvious.
The text was updated successfully, but these errors were encountered: