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
racket--cmd-disconnect: Always set racket--cmd-connecting-p to nil
I noticed when testing on Windows, that sometimes the connection would
not succeed, and furthermore get stuck in a state where
racket--cmd-connecting-p was left non-nil.
This commit fixed that for me.
Although this might have some bearing on issue #344 and issue #348, I
don't have any reason to think this fixes those.
-----------------------------------------------------------------
PROVENANCE: Today I noticed commit 98bb9c7 and commit cedf4ba linked
to from the above issues. But I do not have either commit in any of my
local repos, not even according to `git fsck --lost-found`. WAT.
I suspect what happened was that I made a topic branch and pushed a
commit, which is why GitHub got it (and apparently will keep it
indefinitely because of the link from comments). But then I deleted
the branch without merging. Or possibly that commit was rebased away
before merging the branch.
Probably this happened on a new Windows laptop. In my defense,
mid-January I was moving between Mac and Windows, as part of an effort
to improve racket-mode support on the latter. And then, a Linux laptop
got added to the mix, as well.
In any case I'm going to recover and use this commit, now. The bit
above the horizontal line is the commit message.
0 commit comments