This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-11
Channels
- # beginners (2)
- # boot (97)
- # cider (58)
- # cljs-dev (10)
- # cljsrn (7)
- # clojure (79)
- # clojure-austin (4)
- # clojure-brasil (1)
- # clojure-france (1)
- # clojure-russia (42)
- # clojure-spec (12)
- # clojure-uk (22)
- # clojurescript (150)
- # clr (1)
- # conf-proposals (7)
- # core-matrix (2)
- # cursive (4)
- # datomic (9)
- # jobs (2)
- # klipse (28)
- # leiningen (3)
- # lumo (8)
- # nrepl (1)
- # off-topic (28)
- # om (18)
- # om-next (2)
- # perun (17)
- # planck (9)
- # rdf (1)
- # re-frame (18)
- # reagent (7)
- # ring (2)
- # rum (1)
- # specter (11)
- # test-check (3)
- # untangled (1)
- # yada (7)
very experimental but these are the things you can achieve in emacs thanks to code you can find in cider
clojure-mode
or clj-refactor
actually i was envying the capabilities of clj-refactor and the clj formatter libraries. it's a pity u cant rely on these when using intellij...
yes they are fundamentally two ways of thinking about editors
@onetom what's the emacs version?
M-x emacs-version
will give you that from within emacs, in case you weren't aware of that
but is it possible you're on a network or you have yourself accepted or rejected the certificate issuing authorities?
> The gnutls-trustfiles variable is a list of trustfiles (certificates for the issuing authorities). This is global, not per host name (although gnutls-negotiate supports a trustfile per connection so it could be done if needed). The trustfiles can be in PEM or DER format and examples can be found in most Unix distributions. By default the following locations are tried in this order: /etc/ssl/certs/ca-certificates.crt for Debian, Ubuntu, Gentoo and Arch Linux; /etc/pki/tls/certs/ca-bundle.crt for Fedora and RHEL; /etc/ssl/ca-bundle.pem for Suse; /usr/ssl/certs/ca-bundle.crt for Cygwin; /usr/local/share/certs/ca-root-nss.crt for FreeBSD. You can easily customize gnutls-trustfiles to be something else, but let us know if you do, so we can make the change to benefit the other users of that platform.
im on regular macOS installations. browsers didnt complain about anything, though i cant remember any letsencrypt protected site now to doublecheck
and if i were to recommend this setup to friends they would have the same questions and i wouldnt know what to answer
seems relevant. I guess OS X uses some system keychain for SSL certs that is opaque to Emacs. Perhaps it should learn to understand it, if that's even possible. There's a suggested workaround related to libressl there.
and i think they are saying that os x is being a little secretive with its accepted certs
I have the vague recollection of running into the same issue some time ago. I think I just switched to accessing MELPA via http instead of https
(setq package-archives '(("gnu" . "http://elpa.gnu.org/packages/") ("marmalade" . "http://marmalade-repo.org/packages/") ;; ("tromey" . "http://tromey.com/elpa/") ("melpa" . "http://melpa.milkbox.net/packages/") ("melpa-stable" . "http://stable.melpa.org/packages/") ("org" . "http://orgmode.org/elpa/")))
Hi, sorry for the newb question but does cider/nrepl get the same log messages as lein repl does?
@donavan if I understand you correctly, the answer depends on what version of cider you're using. A bug was recently fixed that caused messages logged to stdout or stderr to get put in the server process buffer instead of the repl buffer.
hmm, my installation names it *nrepl-server {ID}*
, but I'm not sure if that's configurable
it contains messages like:
(<--
id "237"
session "881875ca-f549-4d02-8778-f15514c7e38c"
status ("done")
)
ah, yes, so logging stuff would show up there, I think, but it would be within those message blocks
Maybe this is all academic till I use v0.15... I'm currently using lein repl
and cider-connect
okay, I see. 0.15.0-SNAPSHOT should do what you want then, if you'd rather be jacking in