Clojurians Log v2

https://clojurians.slack.com/archives/CK143P6D7/p1592061883212600 i gave this a try this morning on a whim, and i like it! it's something i didn't know that i would want, but now that it's here, i totally want it

i didn't realize it, but without this feature, i had developed a habit of avoiding moving my cursor immediately after evaluating something. now i can eval something and then feel free to keep moving, which feels liberating

it's funny how little things like that can make all the difference

Ooo that’s great to hear! Thanks for the feedback! Still not sure about turning it on by default (99% sure no) but glad you like it!

Let me know if you see any weird race condition things where it closes when it shouldn’t or something

will do

i'm trying to test using AnsiEsc in the conjure HUD now, but having trouble getting it to do the thing

i see that i need to run :AnsiEsc manually to get it to interpret the ANSI escape codes, but i think i would need to have the HUD focused in order to do that, right? and i can't seem to focus the HUD

my setup is that i'm using the clojure.term.colors package, (require '[clojure.term.colors :as term]) and then i'm running (println (term/red "hey")) which should print they word "hey" in red

running :AnsiEsc (with my clojure buffer focused, not the HUD) has no effect

Oh you need to open the log buffer

then the hud will have it too

ah, yes - it totally works in the log buffer

It applies to the buffer, not the window, and the HUD is just a small window onto the buffer

aha! then it does work in the HUD too

Yep! 😄

i'm quite happy with this!

it seems like there are some minor kinks to work out with some of the bold escape sequences though

I know some of the colouring bleeds into other things, haven’t worked that out yet… it’s to do with vim syntax contains and containedin logic I think :thinking_face:

so far it at least seems more stable than colorizer 😅

i think i'm probably going to drop colorizer and use this instead

It was like a two hour hack on top of an existing plugin, so could definitely be improved furhter!

And with some event hooks in Conjure you could auto run it, but not just yet

quickie, setting a conjure config variable, it writes into a config file?

also, will nRepl 0.8 with completions and lookup have any effect on conjure?

As soon as it’s released I’m planning on adding backwards compatible support for these things. I think I will have to make some small changes, I don’t think they use the same op names and arguments? If they do it’ll work out of the box.

Hmmmm interesting. Although I can’t think of any other vimmy things that work like this :thinking_face: going to replace the config system with a simple vim table soon anyway.

I’ll give this some thought.

Sorry, that was badly worded

It should have been

When setting a conjure config variable, does it write into a config file (which you’ve implicitly confirmed as no)

So, for example, ConjureConfig log.strip-ansi-escape-sequences-line-limit 0

where is that variable set (permenantly)?

That’s just in memory, like doing let g:…

So no, it doesn’t write anywhere I’m afraid

I’m going to change it all to just be let g:conjure_config.foo.bar = … some time soon

And deprecate the command, I want to make it less special if I can.

kk

Would I be able to get this code as text? Will be useful in stress testing my hacky AnsiEsc fork!

sure!

(doseq [color (keys term/*colors*)
          :let [color-fn (ns-resolve
                           'clojure.term.colors
                           (symbol (name color)))]]
    (println (color-fn color))
    (println (term/bold (color-fn (str "bold " color)))))

and in the ns form, i have (:require [clojure.term.colors :as term])

oh hey, it looks like it does a bunch more stuff too: https://github.com/trhura/clojure-term-colors

i haven't even tried the fancier stuff, like FG vs. BG colors, blinking text (wat?), underlining

I can promise you blink won’t work

😅

i won't be too upset about that, lol

I came here to say the same hahaha

I really liked the old approach of having a .conjure file

Hmm that only existed because Conjure ran a JVM that needed configuring. Now it's all in nvims process that config should be done in the nvim way, which is g:... variables... I think. I don't know another plugin that uses it's own config file and syntax :thinking_face: if I did anything like this again it wouldn't be edn.

I kinda want to say "here's the value you need to set, do that where you normally do for all plugins"

This is now fixed on develop 🙂

Screenshot of hell hahahhaah

Yeaaah, it's worse than it seems. The problem with my error handling system there is that it doesn't show the stack trace. So I just had to find it through intuition and knowledge of the code, I won't be so lucky next time.

I've got to add my own error handling in a bunch of deferred callbacks otherwise they just get swallowed (presumably by libuv?) I think.