Please use the following format for the title of this thread (then simply delete/replace this text with the content for the thread):
Title: Hands-on Rust (page number ?? (ePub))
(may not be a problem so much with text of book)
When running examples using Bracket-lib on Mac OS, I always get the following logged out to my terminal…
2020-11-19 15:56:29.649 dungeoncrawl[23603:3643367] NSKeyBindingManager: Bad key binding atom for '$\UF72B' = 'moveToEndOfLineAndModifySelection:'
2020-11-19 15:56:29.650 dungeoncrawl[23603:3643367] NSKeyBindingManager: Bad key binding atom for '$\UF729' = 'moveToBeginningOfLineAndModifySelection:'
2020-11-19 15:56:29.650 dungeoncrawl[23603:3643367] NSKeyBindingManager: Bad key binding atom for '\UF72B' = 'moveToEndOfLine:'
2020-11-19 15:56:29.650 dungeoncrawl[23603:3643367] NSKeyBindingManager: Bad key binding atom for '\UF729' = 'moveToBeginningOfLine:'
2020-11-19 15:56:29.650 dungeoncrawl[23603:3643367] NSKeyBindingManager: Bad key binding atom for '\UF72C' = 'pageUp:'
2020-11-19 15:56:29.650 dungeoncrawl[23603:3643367] NSKeyBindingManager: Bad key binding atom for '\UF72D' = 'pageDown:'
1 Like
Thanks for reporting it! I’ve logged it in the issue tracker. That’s an odd one. Bracket-lib uses winit for keyboard handling, and I haven’t had any reports of Macs doing that (I’ll see if I can borrow one at the weekend to try and reproduce the issue). It’s really curious, because I don’t think we’re even using most of those bindings?
1 Like
related (in that it looks like it’s a bracket-lib issue with MacOS)
Big Sur is now rounding the bottom corner of the terminal window, so characters there are not fully rendered:
I know… that made your day…
2 Likes
Wow, that was unexpected! That’s going to wreak some havoc for quite a few developers who use the corners of windows. I’ll open a bracket-terminal issue on Github tonight and see if I can detect Big Sur and add a gutter.
1 Like
I’ve made some progress on this at the library level. It looks like some of the bindings changed, and OS X spits out warnings as a result. The in-development version binds to a newer winit which resolved that. Still working on the gutter, and newly-discovered issues compiling to Apple’s new M1 chip natively (it’s fixed upstream, but I can’t fix it until upstream publishes a crate on which I can depend). The issues are being tracked at https://github.com/thebracket/bracket-lib/issues/171
2 Likes
