Philip Waritschlager

Results 359 comments of Philip Waritschlager

it should work, perhaps your keycode is wrong or your numlock/capslock was active? ```crystal # ... modifiers = (ControlMask | ShiftMask).to_u32 keycode = display.keysym_to_keycode(XK_A.to_u64) display.grab_key(keycode, modifiers, grab_window: root, owner_events: true,...

However, `display.next_event` is a blocking action that does also never `Fiber.yield`, which prevents any kind of concurrency code... Any idea on how to solve that? :/ Edit: The solution is...

I agree with almost everything @GeoffreyBooth says. It is so refreshing to see a popular project being maintained by such a rational, receptive and reflective person! Do we even want...

@robert-boulanger found a similar issue with comment blocks above fat arrow class methods: https://github.com/phil294/coffeesense/issues/1#issuecomment-1019522762

> Possible current workaround (pretty ugly): > ```coffee > # > ###* > # @param a {string} > ### > method1 = (a) -> Side note: I found another, slightly...

I just finished implementing a VSCode IntelliSense extension / LSP implementation for CoffeeScript based on its JavaScript compilation output, as I keep writing a lot of CoffeeScript and miss good...

I noticed the following translation, not mentioned above or in the test cases: ```coffee [ x = '', y = '' ] = [] x = x.slice(0) ``` becomes ```js...

Hi @GeoffreyBooth, maybe this should be reopened: The above comments said narrowing down the scope tracking would be unnecessary. However, @robert-boulanger brought up a very valid use case, explained [here](https://github.com/phil294/coffeesense/issues/5):...

What sets CoffeeScript still apart from modern ES2018 Javascript is its ease of readability. Since YAML has become so popular, I think the specified syntax would be greatly appreciated by...

I've been working with this repo a lot, and I have never experienced any issues in big files like you suggested. (However, I added 2-3 missing instructions frmo the manual...