Alexander Fadeev

Alright, so it somehow depends on the font used in the Terminal. **Not working**: FiraCode NFM (not rendered correctly, also with many other fonts) **Working**: DejaVu Sans Mono

Alright, so it seems to be a [Windows Terminal rendering bug](https://github.com/microsoft/terminal/issues/15592) (duplicate of: https://github.com/microsoft/terminal/issues/13110) for a heavy check mark (`\u2714`, ✔), however, I also found that another checkmark symbol (`\u2713`,...

@andy-haynes @marcinbodnar @hcho112 FYI

@andy-haynes @marcinbodnar @hcho112 Seems like the `near-api-js` 1.1.0, published 1 month ago, doesn't actually contain the changes of 3 months old (https://github.com/near/near-api-js/blob/master/packages/near-api-js/src/contract.ts#L102): the changes in `contract.ts` are not reflected in...

@lemunozm I think `device_query` can be substituted with `crossterm::event`: `poll` + `read`, the events also contain additional information like https://docs.rs/crossterm/latest/crossterm/event/enum.KeyEventKind.html

@lemunozm Hi! A kindly reminder to look at this issue.

@lemunozm Thank you for your feedback! FYI, I use Windows Terminal which, I hope, should be quite standard for WSL2 folks. Although, I haven't found whether it supports/generates "key up"...

👋 Hey, an author of this issue here! :) I had a similar experience ending up with `crossterm` + loop (or such). If ruscii had been implemented via `crossterm` it...

@jakmeier Okay, fix works... Many bugs though :) 1. I had no resources for some reason at the first try. And the paddler didn't wanna move... Refreshed the screen, it...

@jakmeier I didn't realize those are different resources :), logs and sticks. Also, overall, I would've used some game engine that would've taken off the burden of rendering the graphics...