Albert Safin 83c7aff089 Limit workspace numbers within 0..INT32_MAX
Before this commit, large workspace numbers treated oddly:

   $ i3-msg 'rename workspace to 1234567890'
   # displayed in i3bar as `0`

   $ i3-msg 'rename workspace to 4294967200'
   $ i3-msg -t get_workspaces | jq '.[]|select(.focused).num'
   -96 # int32_t overflow

   $ i3-msg 'rename workspace to 99999999999999999999'
   $ i3-msg -t get_workspaces | jq '.[]|select(.focused).num'
   -1 # treated as unnumbered

This commit puts a consistent limit on workspace numbers.  Now
workspaces with numbers beyond INT32_MAX are treated as unnumbered.
2020-02-21 02:07:04 +00:00
..
2019-10-14 03:31:24 +03:00
2018-03-15 19:57:30 +02:00
2017-09-30 11:41:57 +02:00
2018-11-12 18:45:00 +02:00
2017-09-30 11:41:57 +02:00
2017-09-30 11:41:57 +02:00
2017-09-30 11:41:57 +02:00
2019-07-19 21:10:40 +02:00
2018-12-12 13:09:15 +02:00
2019-10-14 03:31:24 +03:00