This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (3)
- # babashka (130)
- # beginners (73)
- # calva (22)
- # cider (46)
- # cljdoc (18)
- # cljs-dev (196)
- # cljsrn (18)
- # clojure (255)
- # clojure-europe (2)
- # clojure-finland (8)
- # clojure-gamedev (1)
- # clojure-germany (2)
- # clojure-losangeles (6)
- # clojure-nl (1)
- # clojure-spec (16)
- # clojure-uk (33)
- # clojurescript (32)
- # community-development (1)
- # conjure (40)
- # core-logic (11)
- # cursive (4)
- # datascript (8)
- # devcards (17)
- # emacs (21)
- # exercism (2)
- # fulcro (29)
- # funcool (15)
- # graalvm (18)
- # jobs (17)
- # jobs-rus (1)
- # lambdaisland (1)
- # lumo (1)
- # malli (19)
- # off-topic (15)
- # pathom (22)
- # quil (7)
- # re-frame (3)
- # reagent (3)
- # shadow-cljs (14)
- # spacemacs (41)
- # specter (2)
- # sql (5)
- # tree-sitter (1)
- # unrepl (16)
- # vscode (3)
- # xtdb (11)
- # yada (1)
@olical Just tested this, it’s awesome! I did need to install
fennel.vim for it to work.
Oh of course! Maybe I should bundle that with it. Having second thoughts about this though
But if this interactive style taught people the basics really well maybe it's worth it
I think you’ll always want something static for people as reference but the interactive thing is super nice to get started
I like the interactive idea; it also shows it actually working as expected introducing the mappings etc.
I’d maybe suggest to check if
fennel.vim is installed and just print a note to install it when
:ConjureSchool is ran
Perhaps, although I think if I provide the language file in my source vim will use it if it's not install globally anyway
Or perhaps something like vim.fzf, that go ahead and just install the dependencies.
@olical I remapped the conjure map prefix
let g:conjure_map_prefix = ","; will you be adding that option ?
Was going to check for fennel support them prompt you to go get it if you don't have it already.
I suppose I could just copy the syntax / indent / ftdetect in from the vim fennel repo.
I think I'll stick to static docs for now and might implement an interactive thing as a separate optional path. There's just too much added complexity for something important.
at this stage static seems like the best choice; add interactive at a later stage once it is bedded down
Yeah, I agree, I could do it but it's a lot of work to get it right. And then there's so much room for the buffer getting messed up and confusing the new user.
I still like the idea of it though and might do it one day! Maybe I'll run it through babashka instead so you get Clojure instead of Fennel 👀
it’s a great idea and there is huge potential to make this an interactive lisp teaching framework
I have the urge to name it Unseen University after Discworld when I get around to it too. https://en.wikipedia.org/wiki/Unseen_University
If I run out of features in Conjure, writing interactive learning plugins on top of it could definitely fill up my time 😅
just recorded this for a friend, maybe it’s interesting for people curious about
develop, dunno 🙂 https://www.loom.com/share/1ca81032ec204cfb8cf85b6191420537
That's awesome! Thank you for making it, it's so exciting to see other people use it really 😄
I'm trying to keep develop stable, but yeah, there's no buffer between my commits and your machine, so there's a chance I could mess up. I'm being as careful as I can but there's not that extra layer of protection that master gives.
The help is beginning to take shape,
:h conjure-mappings has the full mappings list now. (doesn't include clojure specific mappings since they'll be in
Config and how language modules work coming up. Then specific files for how the Fennel and Clojure language support can be used.
I need to come up with a nice interface for configuring things from VimL. And add more ways to connect to an nREPL!
If the wording / structure / anything sucks about these docs so far, please do let me know so I can make them better. I'm not sure how hand holdy I should be, I feel like presenting all the info and letting you grep across it will be the best thing. But we'll see! I'm adding optional wordy sections that explain in depth how the log behaves for example, but that's not essential so it's near the bottom.