Fork me on GitHub
#cider
<
2017-11-07
>
jumar09:11:45

@ghaskins c means "continue without stopping" that is ignoring all breakpoints. if you use #break explicitly you can just press n to continue execution until the breakpoint is hit. For example:

(defn break [x]
  (let [y (* x x)]
    (doseq [n (range y)]
      (let [msg (str "Hello " n)]
        #break (println msg)))))

;; just call the function and press "n"
(break 3)

pre19:11:03

Does anyone use flycheck-clojure (https://github.com/clojure-emacs/squiggly-clojure) with cider 0.15.1 and emacs 25.1 on a daily basis? I've attempted to use it on many occasions, but each time I find the typing to be unusuable, as flycheck keeps interrupting every keystroke with false errors.

nooga21:11:11

cider is usually lightning fast for me but there is one file in one relatively small project where fans spin up and even cursor movement makes emacs freeze

nooga21:11:19

I’m not sure what’s going on

admay21:11:17

whats the file look like?

dpsutton21:11:29

m-x profiler-start and then after a bit m-x profiler-report

dpsutton21:11:54

will show you some info. note that you run report before stop. stop throws away the information rather than end the watching period for analysis

nooga21:11:07

the file has a huge (comment ...) section but otherwise it’s just some short defns

nooga21:11:13

ah, and it seems that editing inside (comment ...) is much slower than outside

dpsutton21:11:20

i think i remember searching backwards is especially slow in emacs due to an internal text representation. i bet that function looks back to see if its in a comment

dpsutton21:11:27

is my wild guess

nooga22:11:44

I tend to put unfinished/harmful stuff in huge comment sections so I don’t accidentaly C-c C-k them at some point

dpsutton22:11:10

i love reading through core stuff and seeing hardcode's to rich's machine in comment sections

dpsutton22:11:34

slurp /Users/rich/example-rrb-tree.edn or whatever

nooga22:11:37

yeah, I found some on my own and laughed hard at some of them