dylanaraps/sowm

1 && will forever be here. But why?

astier opened this issue · 1 comments

Hallo dear @dylanaraps. I was reading your code and was wondering why you have added 1 && to the event-loop.
The commit which added it had no explanation. I am just curious. Are there cases when !XNextEvent(d, &ev) for some reason quits and terminates sowm although it shouldn't?

sowm/sowm.c

Line 275 in 95596f4

while (1 && !XNextEvent(d, &ev)) // 1 && will forever be here.

No, it does nothing. Funny mistake I made once, just wanted to remember it.