From 3d8dbf6ffdc09fdecb10b428e8d69ed62c6d3795 Mon Sep 17 00:00:00 2001 From: Jonathan Daugherty Date: Thu, 5 Mar 2020 14:27:41 -0800 Subject: [PATCH] UnicodeWidthTable.Query: significantly raise testing upper bound --- src/Graphics/Vty/UnicodeWidthTable/Query.hs | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/src/Graphics/Vty/UnicodeWidthTable/Query.hs b/src/Graphics/Vty/UnicodeWidthTable/Query.hs index 7f6cc19..8b7abdb 100644 --- a/src/Graphics/Vty/UnicodeWidthTable/Query.hs +++ b/src/Graphics/Vty/UnicodeWidthTable/Query.hs @@ -53,14 +53,8 @@ mkRanges pairs = -- The uppermost code point to consider when building Unicode width -- tables. --- --- This only covers some of the possible Unicode range and is sure to --- become stale eventually. Granted, at the time of this writing, even --- the latest version of Unicode (13) totals 143,859 characters and that --- only gets us to code point 0x231f3 or so. But it's only a matter of --- time before this bound is too low. unicodeTableUpperBound :: Char -unicodeTableUpperBound = '\x2FFFF' +unicodeTableUpperBound = '\xe0000' -- | Construct a unicode character width table by querying the terminal -- connected to stdout. This works by emitting characters to stdout