This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (6)
- # arachne (3)
- # beginners (66)
- # boot (84)
- # braveandtrue (1)
- # cider (84)
- # cljs-site (1)
- # cljsjs (3)
- # cljsrn (2)
- # clojure (138)
- # clojure-austin (2)
- # clojure-czech (1)
- # clojure-gamedev (6)
- # clojure-germany (15)
- # clojure-italy (2)
- # clojure-russia (26)
- # clojure-uk (51)
- # clojurescript (97)
- # css (1)
- # cursive (1)
- # datascript (13)
- # datomic (6)
- # devcards (2)
- # docker (1)
- # emacs (5)
- # hoplon (9)
- # immutant (5)
- # jobs (4)
- # leiningen (6)
- # luminus (27)
- # mount (4)
- # om (16)
- # om-next (4)
- # onyx (15)
- # other-languages (36)
- # overtone (1)
- # proton (3)
- # quil (1)
- # re-frame (11)
- # reagent (24)
- # rum (4)
- # spacemacs (3)
CIDER is available on the two major package.el community maintained repos - MELPA Stable and MELPA.
I made a thing to help me regularly learn new Cider commands - http://cider.surrealanalysis.com/ - changes every day
Definitely needs some improvements, as some of the shortcuts are worthless without context (e.g. the fact that http://cider.surrealanalysis.com/#/11 only works in
cider-debug) but hopefully will be useful to some as is
Definitely. Longer term it needs to really have a datasource that I update, or is relatively consistent. Right now it just hits GitHub, looking for things like
<kbd>..</kbd>… | …. which is the format the docs are written in.
But I think some of the keys need context, like s to show stack traces in the stack trace pop up...
Yeah, definitely. Longer term I think the main things that should be added are mode (e.g.
cider-debug, or others), Emacs function (e.g.
C-c M-j), links to readthedocs, and ideally source links. But to the best of my knowledge, there’s no way to generate that programmatically, so I started with something simple I could scrape. Within the next few weeks, I’ll try documenting all the cider functions in a csv or something. Anyone have suggestions for fields other than: keybinding, description, named command, mode, documentation source, and elisp source?
You can use this to scrape until the upper level of the key map and spit this as its info
but once again, I can’t find it… I didn’t read the docs since a while :simple_smile:
hoping to get a little help - since upgrading to 0.12.0 I get this when I use cider-connect:
CIDER's version (0.12.0) does not match cider-nrepl's version (nil). Things will break!
I’ve tried deleting my
profile.boot and updating it to read
(require 'boot.repl) (swap! boot.repl/*default-dependencies* conj '[cider/cider-nrepl "0.12.0"])
I think cider now injects all of this himself, maybe you shall try avoid any referring to nrepl or cider-nrepl
i must be missing something but I have no idea what… thanks for confirming what the problem probably is though
@surreal.analysis: you should be able to export all of that straight from emacs. That would also be a good opportunity to improve the docstrings of these functions. Happy to help with emacs-lisp!
at the bottom left of the Cider documentation page there is a "Read the Docs" link and if you click it an option to download a PDF of the Cider documentation pops up http://cider.readthedocs.io/en/latest/
looks like the issue was that I was using cider-connect, which doesn’t do the auto injection
you are right, it does not. as cider does not start up the repl it can’t really control the middlewares
@nonrecursive: Sorry for the confusion. In the current snapshots this warning will link you to a more informative page in the manual:
@malabarba: thanks! the docs were actually helpful and are what led me to find the solution :simple_smile: I just had to take take the time to read them carefully
@brian_mingus: That appears to be true of all the downloads (pdf, html, epub)
Does anyone else use refactor-nrepl when they start their own nrepl server? It seems to confuse cider, because I get the version mismatch warning, and cider-nrepl’s version is
e.g. something like this:
(nrepl/start-server :port nrepl-port :handler (refactor/wrap-refactor cider/cider-nrepl-handler))
Right now I think the solution (to the incorrect links, not your wanting a PDF) is to add a readthedocs.yml - https://read-the-docs.readthedocs.io/en/latest/yaml-config.html - and use
none as in the first example for
@surreal.analysis: yeah, when I adopted mkdocs I didn’t know how broken the support for it was
@brian_mingus: someone should either fix readthedocs or rewrite the manual in rst :simple_smile:
I think (but definitely do not know) that it’d be a minor transition of only some files. ReadTheDocs should support markdown and rst with Sphinx, based on this - http://docs.readthedocs.io/en/latest/getting_started.html. But it also seems like they might devalue some tech over others based on MkDocs vs Sphinx. If I get a chance, I’ll try to see if I can make a simple migration.
Yeah, based on “How we build documentation” I don’t think my markdown comment was correct
asciidoctor is also an option. They have a java library https://github.com/asciidoctor/asciidoctorj
any idea why I sometimes get stack traces that only show up in the Messages buffer and are hardly scrutable?
@brian_mingus: That I know of, stacktraces only go to the
*Messages* buffer on one condition: if they happen during REPL startup and kill the REPL.
If they happen somewhere entirely outside cider's control (like a background thread) they stay on the
*nrepl-server ...* buffer.
Could you post the contents of the
*nrepl-messages ...* buffer immediately after connecting?
@jcsims: that's all? @bozhidar don't we log the first few messages exchanged with a repl?
@brian_mingus: I'd love to speed up the repl startup. But how does it work and what are the tradeoffs?
@malabarba: yup, that’s all. Let me restart the app and get the very first connection to it - would that have any extra log messages?
i think we'll need some kind of dependency tracking system that detects when we need to create a new core dump
I’ll take a look later at the proper way to wrap with refactor - like I said, it seems to work fine right now, so I haven’t looked into the issue much at all yet