This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-04
Channels
- # 100-days-of-code (8)
- # announcements (4)
- # beginners (77)
- # boot (11)
- # business (13)
- # cider (69)
- # clara (2)
- # cljdoc (51)
- # clojure (59)
- # clojure-dev (18)
- # clojure-italy (4)
- # clojure-nl (11)
- # clojure-spec (54)
- # clojure-uk (115)
- # clojurescript (33)
- # core-async (4)
- # cursive (95)
- # datomic (27)
- # duct (1)
- # emacs (58)
- # figwheel (22)
- # figwheel-main (63)
- # garden (1)
- # graphql (10)
- # hyperfiddle (1)
- # leiningen (1)
- # luminus (6)
- # off-topic (12)
- # planck (7)
- # portkey (1)
- # quil (3)
- # re-frame (3)
- # reagent (5)
- # ring-swagger (3)
- # shadow-cljs (34)
- # slack-help (19)
- # spacemacs (57)
- # testing (2)
- # timbre (2)
- # tools-deps (42)
- # yada (6)
@dpsutton There was some ticket about this back in the day - I think @malabarba had found there was some security problem with this, but I don’t remember the details.
Generally there are so many security wholes that I wonder if we should care about who can set what in their local setup. 😄
Should be somewhere after this PR https://github.com/clojure-emacs/cider/pull/1552/files
i think this is just generic how you should handle local vars in emacs thing. ref https://www.gnu.org/software/emacs/manual/html_node/emacs/Safe-File-Variables.html
@benedek Yeah, I get this but we already eval so much code on behalf of the user anyways, so I don’t know how practical of a concern this is.
Probably we can just make all of those defcustoms and leave people to do with them whatever they want.
I’m just trying to figure out if we consider this implementation detail or something customizable.
Given how people often touch those they don’t seem like an implementation details to me.
Hi. Not sure where's a good place to ask, but since this error pops up in *cider-error*
...
How can this run file if you’re getting an exception? 🙂 Maybe the command got routed to the cljs connection, but it doesn’t work over it or something like this? I’m curious what’s triggering the cljs evaluation that’s in your stacktrace.
@bhauman What would be an ideal interface for you? Predefined profiles you aliases you can select from or something like this perhaps?
I think just being able to provide the extra flags at launch would be the most natural/flexible interface
We used to have special support for lein profiles in the early days but we dropped it in favour of being able to pass whatever you want.
(defun cider-jack-in-clj (params)
"Start an nREPL server for the current project and connect to it.
PARAMS is a plist optionally containing :project-dir and :jack-in-cmd.
With the prefix argument, prompt for all these parameters."
(interactive "P")
(let ((params (thread-first params
(cider--update-project-dir)
(cider--check-existing-session)
(cider--update-jack-in-cmd))))
(nrepl-start-server-process
(plist-get params :project-dir)
(plist-get params :jack-in-cmd)
(lambda (server-buffer)
(cider-connect-sibling-clj params server-buffer)))))
Just tried it and it works fine for me - first it asks about the project and afterwards about the command to run.
the support is fantastic if you place your libs at the top level of deps.edn, but if you isolate it gets much trickier
Got it. File a ticket for this and I’ll see what we can do. Should be relatively straightforward to tweak the existing approach. Maybe some defcustom controlling what to prompt for or a different behavior if you use two prefix args. The UX for this is the hard thing for me to figure out - implementing something will be easy.
yeah, the only reason I bring it up is because when you use the clojure tools on the command line you normally add some aliases of some kind to scope your classpath. And folks are quite used to that, using a configuration cuts that expressivity and brevity.
Would folks be ok with a patch to clojure-mode
that unifies the colors of the two s/
top level entries there?
Is it even possible?