Thank you for the nimble fixes!..
Safe travels, friends.
Another thing I can attest to, possibly related—when scrolling through headers with ⌘[ or ⌘], the newly highlighted headers sometimes appear off-screen, above the upper border. This doesn't happen by default, but seems to be triggered in full-screen only, by scrolling through particularly long patches of text within one header (more than one screen worth of lines)?
Also I found the new arrow-key scrolling behaviour (centering cursor in the middle) kinda jumpy and hard to follow, if I may express that opinion. ^_^
Loving your wonderfully handcrafted piece of software, as always! Thought I'd drop some lines on the latest version of Left—some minor things I noticed. Hopefully that will be of help and will not burden you too much!
To get specs out of the way: Left v1.8.7, Mac OS X Yosemite 10.10.5, MacBook Pro (Retina, Mid 2012). Let's go:
1. Performing the Hide command (⌘H) in full-screen mode leaves one with a black screen, the only way to restore it being to switch to another screen (Ctrl–←, no pun intended) and click at the app in the Dock. I'd suggest ⌘H to leave full-screen and minimize the window. I discovered this while using the Insert Header feature (⌘I, H), but sometimes I play the chord too quickly and hit H before I, so originally I thought it was a parsing-induced crash.
2. Selecting the entire file (⌘A) seems to always bring the percentage in the status line a tad over 100%; selecting multiple words or lines of text sends it into exorbitant amounts of thousands. Should the percentage be displayed during selection anyway?
3. The Find and Replace functions ignore the first line of the file (not seeing words in it); Goto ignores the first paragraph (typing «1» sends you to the second, «0» is not parsed). Weirdly specific little thing: if currently highlighted text starts with three non-space characters, then as soon as you type these three in the «find» prompt, it stops, highlighting said three characters only (possibly intended?).
4. The Documentation command (⌘⎋) has ceased to do anything.
5. Text selection sometimes spawns these remnant monoliths at the margins, which blink in unison with the cursor if they choose to, and may or may not be simple to remove. I, for one, welcome their presence.
As you can see, none of these are particularly game-breaking, but I'm here to report anyway.
A very nice vignette! Spent at least a half of an hour on it until I beat it (assuming falling to the left of the wall at the cloudy top counts?)—some parts were quite a struggle and honestly annoyed me a bit, but overall I enjoyed the soothing nightly vibe. I found the mechanics interesting, but they took quite a while to get confident in reproducing, as the exact control scheme behind them is not really apparent. I think that with some mechanical elaboration and more levels this could become a crisp speedrunning game, especially for tight jump enthusiasts—just adding a little non-threatening clock to the game as it is (displayed on second playthrough?) would be sufficient. I found the rhythm of racing through it with a mix of quick long-jumps and small positioning jumps alluring somehow. Glad I went by! Cheers.
Thank you!.. The exploration side was my focus — I'm happy to hear you found it interesting. One of the five endings is incredibly obscure and can only be found through glitch abuse... The others are more accessible!