Ooooh
I'm glad they arrived okay! Although I'm very sorry they're not super sticky at the edges, I think the firmness of the stickers doesn't lend itself to staying put. If you wanna just keep them as little historical things I suppose that's nice too π
Yup. Don't worry, they will be perfect next time π
also, a bit of pritt stick can help π
True! Although it's only right at the edges in like 1-2 corners where it lifts up a little bit, so they stay on fine, it's just not totally flush on some of them at the edges.
So it's not actually that bad tbh I don't think
I wonder how long all of the others will take to arrive, one is on it's way to Brazil π
mine arrived yesterday, I think. I just found the envelope on the hall : )
If it's got a five year olds hand writing on it, it's mine :D
Is anyone else using deoplete with Conjure? Iβm finding it very laggy. Itβs not just that the completions take some time to come up, but Vim seems to periodically hang for short amounts of time (like half a second) while Iβm typing. Typing a space makes it happen pretty predictably, e.g. if I quickly type (ab c
the editor hangs at (ab
for a split second before spitting out the c
.
Iβve tried this in a few other languages and they donβt seem have the same problem.
I donβt know whether this is a problem with my config or just the nature of deoplete+Conjure.
I think if you let g:conjure#client#clojure#nrepl#completion#with_context = v:false
it'll all go away
And I might make this the default soon
As you type I'm having to grab the surrounding forms to give to the completion tooling to find local variables, but that's slow because of how vim searches for pairs
I think it's arguably not very useful either, so I think I'm going to turn this off since it's slow for me in some envs too.
> I think if you let g:conjure#client#clojure#nrepl#completion#with_context = v:false
it'll all go away
(from thread for others that find typing slow)
interesting
Wow, awesome, it works! Thanks!
The long result folding is great, I missed that since the rewrite. I did find one small issue.
sometimes, my data has high levels of nesting
and then the ending marker (`}}}`) shows up in the data itself
and so the folding cuts off earlier
example:
#_{:foo1 1
:foo2 2
:foo3 3
:foo4 4
:foo5 {:bar1 1
:bar2 2
:bar3 3
:bar4 4
:bar5 {:baz1 1
:baz2 2
:baz3 3
:baz4 4
:bar5 {:baz1 1
:baz2 2
:baz3 3
:baz4 4
:baz5 5}}}
:ff :ff}
the }}} on the second to last line is seen as the ending marker
perhaps using \\\
and ///
as markers would have less potential for conflict?
hacking my log.lua
file and using slashes and backslashes seems to work
Ah of course! That's just the default folding marker in vim, I'll swap it to something a little more unique
I'll probably perform that with_context = v:false
by default in the next version, I think it's not very useful but it hits performance hard due to the way nvim searches for matching characters in large buffers. Again, this thing will be super easy and fast once tree sitter is everywhere since I can delete all of the slow character by character hunting code.
I think vim-sexp is pretty quick though, so maybe I could look at how they're doing things for now :thinking_face:
More things for the todo pile!
awesome, thank you
with_context
is now false by default for Clojure completion, you probably won't notice a difference other than your typing will be faster, so, yay!?
Also fixed the fold markers on develop
(both of these changes are on develop) @nate, it's now ~~~%{,}%~~~
and it's configurable.
Through let g:conjure#log#fold#marker#start/end = "..."
@olical just tried it out, works great! nice choice of marker, I doubt that will ever show up in data.
thank you
I hope not π it's the most interesting I could think of without it being toooo over the top
~~~attn-this-is-a-fold-created-by-conjure%{,}%that~is~all~thank~you~~~