This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-09
Channels
- # beginners (20)
- # boot (4)
- # cider (2)
- # cljs-dev (25)
- # clojure (45)
- # clojure-dev (1)
- # clojure-greece (5)
- # clojure-italy (20)
- # clojure-nl (12)
- # clojure-russia (11)
- # clojure-uk (256)
- # clojurescript (176)
- # data-science (33)
- # datomic (47)
- # docs (1)
- # duct (13)
- # fulcro (54)
- # graphql (24)
- # hoplon (3)
- # jobs (1)
- # leiningen (32)
- # luminus (3)
- # midje (1)
- # mount (2)
- # off-topic (3)
- # onyx (5)
- # overtone (1)
- # parinfer (12)
- # pedestal (4)
- # re-frame (60)
- # reagent (11)
- # reitit (3)
- # ring-swagger (21)
- # rum (1)
- # shadow-cljs (16)
- # spacemacs (23)
- # tools-deps (19)
- # vim (79)
@eraserhd interesting, so these larger characters should count as two?
(foo "text" (bar
baz))
I suppose it depends on how they’re displayed in monospace
if they’re consistent in displaying two characters wide in monospace fonts, I think the change should be made
and i wonder if firacode users see any similar problems with ligatures
I know Vim displays wide characters in two cells, which freaked me out first time I saw it.
I think firacode should be fine, since the indentation never changes with the ligatures (I used to use it all the time).
@eraserhd thanks, i’ll track this in a github issue, do you have details on what text
is? just special unicode characters that are somehow double wide?
http://unicode-rs.github.io/unicode-width/unicode_width/index.html has some useful info, including a link to a Unicode annex.
I haven't figured out all the details yet, but the rust port fails on compound characters also, so I'm going to fix that first. (see https://github.com/eraserhd/parinfer-rust/issues/26 )