This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-16
Channels
- # ai (3)
- # babashka (3)
- # beginners (252)
- # calva (56)
- # clj-kondo (6)
- # cljfx (7)
- # cljs-dev (2)
- # cljsrn (2)
- # clojure (72)
- # clojure-france (12)
- # clojurescript (13)
- # conjure (60)
- # garden (18)
- # hoplon (16)
- # jobs (1)
- # leiningen (3)
- # off-topic (18)
- # pathom (5)
- # practicalli (1)
- # reagent (4)
- # reitit (1)
- # remote-jobs (1)
- # reveal (3)
- # shadow-cljs (1)
- # spacemacs (7)
- # xtdb (39)
Funny story, I went searching for a scheme plugin and stumbled on this one https://github.com/Olical/vim-scheme by guess who? Hahaha. And he created it to use while working through SICP. Well played @olical
Haha, I am aiming for conjure to massively deprecate that plugin :) but if it works, yay!
And @chase-lambert @dave you can configure the racket repl startup options, see the racket specific help :D
Cool, I will look into that tomorrow. I don't mind using this old scheme tool of yours either though. It is funny seeing the mix of fireplace shortcuts and what were probably your first ideas of conjure commands mixed together
Yeah I'm sure there's some precursor ideas before Conjure plopped into my head 😄 it's also what made me realise how difficult it is to do that sort of thing in VimL, so probably helped kick me towards Aniseed. It may have been the last VimL plugin I tried to write :thinking_face: wondering how much better I could write https://github.com/Olical/vim-enmasse/ now too!
Does Conjure support some sort of jump-to-var type thing?
It's not on gd
(unprefixed) because that can be handy for jumping to files etc and I didn't want to hide core nvim functionality.
Oh, I actually meant more based on a fuzzy search than whats under the cursor
sorry, wasn’t very clear 😅
Like I’d like to use FZF to search for vars in my codebase
currently I use ripgrep and then just def thing-im-looking-for
but I think it might be nice to just give a fuzzy search across vars
another thing where clj-kondo static analysis could shine
I mean, this wouldn't be core conjure functionality because it assumes a few other plugins, but it could be an extra thing / a recipe we work out that others can paste into their config.
personally I’m more interested in the static analysis approach because I mostly do cljs and am not always connected to a REPL
but fair point with involving other plugins for sure
I’m gonna take a look if I can hack this together
I haven’t tried that. Are you using clojure-lsp with Conjure?
I’m still a bit burned from years ago when all these plugins would conflict in one war or the other
I am still kinda trying to keep Conjure clear cut in that it's all about sending code to a process for evaluation then doing something with the result from your live system. Less about analysing code on disk.
clojure
{:private true,
:arglists ([code line column]),
:line 42,
:column 1,
:file "nrepl/middleware/interruptible_eval.clj",
:name source-logging-pushback-reader,
:ns #namespace[nrepl.middleware.interruptible-eval]}
Each of which is a var, so you can get source metadataYMMV in CLJS land, but it may well work. I know var location metadata can be very flaky in CLJS, which is why I relied on nREPL and it's info op.
Error executing vim.schedule lua callback: /home/david/.vim/bundle/conjure/lua/conjure/log.lua:400: Conjure failed to append to log: String cannot contain newlines
Well that's weird... I didn't change anything that would effect that :thinking_face: I'll try and reproduce this tomorrow
thus when that failed (and caused the particular namespace I was evalling a buffer on to fail), caused this
I'll see if I can reproduce this, but in all honesty, this is the first time I've seen this
Hmm I tried to require a file that required another file that had invalid syntax but it worked (as much as you'd expect it to) :thinking_face: not sure if I can repro, I'll read the code and see if I can spot any place a newline could slip through.
Maybe your Clojure is adding new lines into an error message that I never expected or something.
Oh! Actually! The next line after that error should have been the offending lines that caused the issue! Did you see any? It'd be in :messages
if not I guess.