cider 2023-10-24 | Slack Archive

hifumi12306:10:03

was the change in syntax highlighting for some? intentional? using modus-vivendi theme on my end, i see a purple color now where previously itd be pink. the color of other functions, like nil? didnt change, it seems. i dont really consider this a bug, just curious also: the macro indentation inference in 1.8.0 is awesome

vemv06:10:19

With:

(setq cider-font-lock-dynamically '(macro deprecated
                                       core ;; for a repro
                                       )

I see some? and nil? highlighted as core. JVM clojure (edit: also with clojurescript)

vemv06:10:25

One thing noticed just now is that some? nil? both get highlighted, but only when they look as a function call (i.e. they have the parentheses)

👍 1

nivekuil07:10:14

cider trying to decrypt authinfo.gpg has been annoying for a while now, seems I'm not the only one going by slack history. should be an easy fix, add a defvar guarding https://github.com/clojure-emacs/cider/blob/master/cider.el#L1768. should I just send a PR?

vemv08:10:15

feel free to :)

nivekuil08:10:48

sent a pr, the infra runs eldev right? I can't even figure out how to install it 😞

vemv08:10:36

Yep, it does. Thanks for the pr!

Carsten Behring18:10:46

We could in my view simplify the documentation of (remote) containers / devcontainers here: https://github.com/clojure-emacs/cider/blob/master/doc/modules/ROOT/pages/basics/up_and_running.adoc#working-with-containers-docker-or-others by only referring to a new tool for this: https://github.com/loft-sh/devpod From an Emacs point of view devpod unifies the concrete "place" of the container (local or remote or inside Kubernetes or ....) and creates for all cases a working ssh connection entry in ".ssh/config" and tunnels configured remote ports automatically to "localhost" and makes the code available with a "simple" TRAMP connection 'user@host'. So different docker scenarios "look" the same for Emacs / CIDER.

👀 1

vemv18:10:28

I don't think it's CIDER's job to promote a particular tool - particularly a new one. Knowing the Clojure audience well, most developers will be conservative in their choices and will try to stick to vanilla Docker or such. With that said, if you felt it was necessary we could add a section for it (that would not replace existing sections). But preferably, CIDER / its doc would be correct enough that one can use newer tools with minimal adaptations.

➕ 1

Carsten Behring18:10:33

Yes, I do agree. Maybe a single phrase saying that "the above" gets simplified using "devpod" is fine, What we say stays correct, just that for the "lower level" devcontainer-cli we still need to say "from here2 we run it and devpod does more automation in port forrwarding (including creation of '.ssh/config' entries. "more magic" you could say....

vemv18:10:10

I see! I don't enjoy saying 'no', but that would sounds like a tutorial to me... in my mind, a tutorial is something pretty detailed, that describes a particular stack (here: devcontainers + devpod?), step by step. Tutorials tend to bit-rot relatively quickly. A "reference documentation" is less easy but also less opinionated and more stable. That's IMO what our docs should aspire to be.

Carsten Behring11:10:47

agree, to much for CIDER docu. But I have one other question related, but will start a new thread.

2023-10-24

Channels