Alright, time to fix some bugs 😅

Damn users, breaking my things! (thank you for breaking my things ❤️)

* Autocompletion will now just silently fail when you don't have a connection or the server doesn't support it now. (@sergiusz) * I've moved "view source" and the *e *1 *2 *3 mappings to a v prefix for "view" since they weren't really to do with eval anyway. (@nate, avoids conflicting with your mapping too) * Fixed and improved interrupt so now it'll interrupt the right eval on the right session and then fallback to sending a generic interrupt to your session. This allows you to kill long running evals that Conjure doesn't know about that may be running in the session. (this is mapped to <prefix>ei) * I can't reproduce the log printing out of order or whatever when there's lots of output, will keep trying. * I can't reproduce the HUD getting stuck open when connection is lost, again, will keep trying. (@nate for those last two)

I can't see how the HUD / log can get into these race conditions since access to the state is restricted to the logging module via access functions which are all running in a single thread.

Obviously it can get messed up, I just have no idea how right now. Something about all the async callbacks involved with the Clojure client I guess.

Hey @olical I was reading the docs, before trying out the develop version I have two questions (sorry I'm dumb) • The ["K"] means that is doesn't need localleader for using this command? I mean, I usually remap conjure's K and gd to use localleader as well and let the default ones for the LSP which load faster. So if I what to let this behaviour I can just configure "K" and "gd" to get this? • The conjure config is saved in ~/.config/conjure/conjure.edn ? I didn't found anywhere in the docs saying where the config is saved.

i'm in the process of trying out the develop branch now, loving it so far! i'm curious, at this point, what are the features missing when your nrepl doesn't include the cider middleware?

i noticed that gd doesn't work and there is a message "Unsupported operation: info", whereas K does work

ah, i guess those are two different things, look up docs vs. go to definition

i'm really loving having the nrepl session persist after i restart neovim! very handy if i'm messing with my vim config and i get into a weird state and want to nuke neovim and start over

i also really like the new config system, well done

sharing my personal tweaks here in case they're helpful to anyone:

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
" => conjure
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
function! ToggleConjureLog() abort
  if expand('%:t') =~ ".*conjure-log-.*"
    execute 'Bclose'
  else
    " Ideally I could call some function provided by Conjure directly to do
    " this, but I wasn't able to figure out how to do that. This mapping will
    " need to be adjusted if I ever configure Conjure to use a different mapping
    " to open the log in a tab, or if Conjure ever changes the default mapping.
    " I think those two things are both pretty unlikely to happen, so meh.
    "
    " Another thing worth noting: normal apparently doesn't work with <leader>
    " and <localleader>, so you have to do some hackery like what's going on
    " here () or just give up and type
    " your actual (local)leader key in the mapping. I'm doing the second one.
    normal \lt
  endif
endfunction

augroup additional_conjure_bindings
  autocmd!

  autocmd FileType clojure
        \ nnoremap <buffer>
        \ <localleader>cc :call ToggleConjureLog()<CR>

  " mnemonic: eval prompt
  " (like how <localleader>ee is eval expression)
  autocmd FileType clojure
        \ nnoremap <buffer>
        \ <localleader>ep :ConjureEval<space>

  " press q to close the log buffer
  autocmd BufEnter conjure-log-*.cljc nnoremap <buffer> q :Bclose<CR>
augroup END

Bclose is another custom thing i have in my vimrc. it basically just closes a buffer in the way that i like to do that

with the tweaks above, i can press <localleader>cc to show the conjure log in a tab (i.e. fullscreen) and then press it again to close it. it toggles showing/hiding the log, in other words

@dave thanks for sharing!

That should be captured perhaps on the github page as User Submissions? Or on the Wiki?

As an example

eh, i'd hesitate to share it out in the open like that. it's very particular to my own preferences and vim setup 🙂

like maybe there are some issues with making q close the buffer on some people's vim setups. who knows?

Well, how will you record a macro!

see? case in point 😄

for the record, i do use macros extensively, i've just also gotten used to pressing q to close certain types of buffers that i consider more ephemeral. i would never think to define a macro in those buffers

probably a bad idea to recommend this practice to others

q works in some temp buffers for fugitive, so I think it's not a bad idea

yep, that's how i got used to pressing q

i found myself doing it all the time and almost defining macros 😄

so i was like "fuck it, i'll just define a mapping that closes the buffer when i press q"

fugutive has deprecated that key though, they use gq now

it's too late, i'm already used to pressing q!

haha