This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-05
Channels
- # all-the-channels (1)
- # announcements (3)
- # asami (13)
- # beginners (227)
- # calva (2)
- # chlorine-clover (8)
- # cider (7)
- # clj-kondo (4)
- # cljs-dev (21)
- # cljsrn (8)
- # clojure (64)
- # clojure-europe (39)
- # clojure-france (2)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-nl (20)
- # clojure-uk (8)
- # clojurescript (24)
- # conjure (12)
- # datalog (9)
- # datomic (24)
- # emacs (8)
- # figwheel-main (1)
- # fulcro (15)
- # jobs-discuss (1)
- # malli (5)
- # meander (3)
- # off-topic (26)
- # re-frame (15)
- # reagent (10)
- # reitit (1)
- # reveal (1)
- # sci (15)
- # shadow-cljs (25)
- # spacemacs (7)
- # sql (3)
- # xtdb (1)
Yes, unfortunately Chlorine development is a little bit slower for now, lots of thing needing my attention, but I believe this issue will be simple to fix. Or, at least, I hope so đŸ˜†
OK submitted as: Unparseable code error failing to result in any error message being presented #207
Going out for lunch now, wish everyone a great day đŸ˜‰
@flyingpython all right, found the problem... the issue is not exactly on parsing the number, but on parsing the top-level form
(to be honest, I don't know how's the right way to solve this issue đŸ˜„. To be able to identify where blocks start/end in Clojure, I need to somehow parse the code... currently I'm using rewrite-cljs to do most of the job, and when I can't find a form I just ignore it and continue with the new form. In this case, the code (valid-isbn 05967)
is failing to parse, and it's being ignored.
For example, if you try to select the whole block and run Evaluate Selection
, it behaves as expected (shows an error "Invalid number: 05967")
Perhaps popup a warning when you can't identify a block to be evaluated?
Yes maybe that'll help. Or can confuse even more users because they can see the block but Chlorine can't đŸ˜… Maybe I'll publish the next version with it, and if it ends being confusing, I remove on a later release :)
"Unable to parse expression at cursor" ?