This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-24
Channels
- # admin-announcements (1)
- # alda (22)
- # aws-lambda (1)
- # beginners (9)
- # boot (17)
- # cider (39)
- # cljs-dev (10)
- # cljsjs (1)
- # cljsrn (14)
- # clojure (88)
- # clojure-android (1)
- # clojure-dev (9)
- # clojure-india (1)
- # clojure-russia (271)
- # clojure-spec (5)
- # clojure-uk (101)
- # clojurescript (74)
- # clojutre (11)
- # component (2)
- # cursive (24)
- # datascript (7)
- # datomic (9)
- # dirac (13)
- # docs (3)
- # emacs (4)
- # garden (21)
- # hoplon (9)
- # jobs-rus (5)
- # lein-figwheel (3)
- # leiningen (13)
- # luminus (12)
- # off-topic (1)
- # om (24)
- # onyx (84)
- # proton (3)
- # re-frame (39)
- # reagent (21)
- # rethinkdb (1)
- # slack-help (10)
- # specter (4)
- # test-check (1)
- # untangled (35)
- # yada (2)
Take a look at @AnnaPawlicka's Tweet: https://twitter.com/AnnaPawlicka/status/768143289006559232?s=09
nope. spaces are the same
I do that already with a couple single-space characters (mostly for anonymous fn literals and sets). Might have to try that out
i am happy user of this font after I gave up the fight with prettify symbols for this reason @jcsims
i only prettify (fn
into lambda fixing the indent with the trick recommended by @malabarba
i don't store the why and wherefore of each decision to eliminate complexity or pain in my toolchain.
this was probably the era of getting my erc buffers to use kerned text and my programming buffers to use monospace
you mean @malabarba ’s post. it does. i shyed away from prettify symbols too (see above)
Anyone else still getting that error in process filter: Attempt to shape unibyte text
with the suggested setup? Weirdly just seems to be happening to me when requiring/refreshing source files, not actually stopping me from working.
if you look at Anna’s setup, she’s got a note about that: https://github.com/annapawlicka/org-emacs/blob/master/org/config.org#fira-code
yeah, i commented it out and it works fine now. previously it would keep on showing that error and cider was basically unusable
Yeah, I have that line commented out as well, but I’m still seeing the error occasionally. Definitely not as frequently as to make it unusable though.
Uncommenting that line does make it unusable. So it’s responding, but apparently besides that particular very broken one, there’s another less-broken one lurking in the list.