Clojurians Log v2

just tried the latest release of chlorine after upgrading to atom 1.40 and so far it seems to be working fine :thumbsup:

Yeah, it's looking pretty good!

I've been meaning to do some new screencasts but the next thing I want to show is somewhat blocked by REBL not using a dynamic class loader for its REPL, which was a bit of a shock to me...

I want to show building a web app, from scratch, with a single live REPL session, adding dependencies to an empty project (using the add-lib branch of t.d.a.) but that's made a lot harder by REBL not using a DCL 😞

that sounds pretty neat! when you say REBL's repl, are you referring to the top left pane in the REBL ui?

Every entry seems to get its own scroll area. Is this by design?

@henrik no, it is not by design. I'll check it, but by design only the evaluation result should get a horizontal scroll (not vertical)

@seancorfield what does t.d.a stands for? Is it a library?

^ tools.deps.alpha I believe.

It has an add-lib branch

What's your current operating system? Do you have any custom stylesheet applied? What's your current Atom theme?

Also, what's the current Atom version you're using?

MacOS: 10.14.6 (18G95), Theme/Syntax: One Light/One Light, no custom stylesheet. Version: 1.40.1

I'll probably need some debugging on this issue, I can't reproduce on my current machine. I'll see if someone close to me have a mac so I can debug. In the meantime, if you could change some styles in the Atom's devtools and see if changing the font size, overflow, or some other attribute works, so you can help me debug the issue, I'll be glad 🙂

Of course! I’ll have a look and get back to you.

hey all seeing something super weird...

everything was working totally fine yesterday.

today when I connect to the repl and refresh a file (using chlorine's refresh file feature..)

i get a failed to refresh with ☝️

wait, maybe PEBKAC

well it's specific to this project at least.

I think you need clojure.tools.namespace on the classpath for this project. Or, you can "Toggle Refresh Mode" to Simple, and it'll not try to refresh with c.t.n

ah yeah interesting, it's set to full.

there we go

thought I had it defaulting to simple :thinking_face:

🤷

thank you!

ok even with simple

i'm getting it when bringing in a lib :thinking_face:

Same error?

maybe not, 1s let me copy it

(I really need to parse the error better before sending it to the Atom popup...)

oh my I think it's me again.

doh I had clj-http instead of clj-http.client

and didn't notice

PEBCAK again. 🙂

@gerred I find the refresh behavior to be problematic in general so I disable it completely. Both Eric Normand and Stu Halloway recommend against a workflow based on refresh and I'm inclined to agree.

Unless you have a workflow that absolutely requires refreshing namespaces, I'd avoid it.

Currently, the defaults are to use "Simple" refresh, and it is disabled on save

exactly because there are, indeed, multiple issues with some code that would not support any refresh 🙂

@seancorfield @mauricio.szabo I've noticed lisp-paredit enter has an indentation of 1. if I cmd-enter it's fine. have either of you found a nice way to manage that?

it causes random chaos sometimes w/ parinfer when I forget the behavior 🙂

oh, I guess I can disable lisp-paredit's keybindings and rebind the exact ones I want...which is all of them but lisp-paredit:newline 😛

That's what I did in the beginning, too

seems like this issue goes all the way into paredit.js :thinking_face:

you know what.

I think I found the issue, this is specific to comment blocks it seems.

FWIW, I still have enter bound to lisp-paredit:newline and I haven't noticed any problems.

try starting a (comment) form and hitting enter. is it indenting with 1 space or 2 for you?

(and compare to cmd-enter or whatever Editor: newline below is for you)

editor: newline below with language-clojure is indenting correctly

lisp-paredit, newline is not (for me)

lisp-paredit follows some kinda arbitrary rules. For example, (def indents 2 spaces

if that's the same for you, I'll start looking for it to fix it in lisp-paredit or paredit.js

comment indents 1

There's a config for that, I think

Indentation Forms is the config name. Try putting comment there

(comment|) when cursor is at | and I press enter I get an indent of 2.

weird!

i promise I'm seeing it (removing ableist language) 😄

My setting for lisp-paredit has all these forms:

binding, case, /^try/, catch, finally, let, are, /^s\/def/, /^s\/fdef/, /^def.*/, bound-fn, fn, /^cond-.*/, if, if-let, if-not, for, /when.*/, testing, do, doseq, dotimes, loop, ns, /with-/, proxy, reify, extend-protocol, comment, /deftask/, expecting, as->

ah ha

Including comment 🙂

i have most of those but not comment 😄

💥

that did it!

I've modified it quite a bit from the original...

i might fork off my own lisp-paredit and release it as lisp-paredit-noveau or something. i'll open an issue, but looks like the creator is well and inactive and there's some good issues/PRs to fix, and some defaults that could use updating.

i'll let you all know if and when I do that. 🙂