This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # alda (1)
- # aws-lambda (23)
- # beginners (27)
- # boot (156)
- # business (2)
- # carry (4)
- # cider (1)
- # cljsjs (2)
- # cljsrn (29)
- # clojure (170)
- # clojure-austin (35)
- # clojure-czech (8)
- # clojure-dusseldorf (5)
- # clojure-italy (4)
- # clojure-nl (1)
- # clojure-quebec (2)
- # clojure-russia (45)
- # clojure-spec (49)
- # clojure-uk (12)
- # clojurescript (81)
- # component (5)
- # datomic (24)
- # devcards (26)
- # emacs (4)
- # hoplon (4)
- # jobs (1)
- # juxt (5)
- # leiningen (6)
- # luminus (14)
- # mount (26)
- # om (27)
- # om-next (2)
- # onyx (22)
- # pedestal (2)
- # planck (3)
- # proton (5)
- # re-frame (19)
- # reagent (2)
- # ring-swagger (60)
- # spacemacs (12)
- # specter (8)
- # untangled (119)
- # vim (61)
- # yada (36)
@dominicm Have you seen this error: https://github.com/clojure-vim/async-clj-omni/issues/7
closed connection = trying to connect to a dead nrepl? Not on a dry connection (should just be a try/catch, I've just never hit that because of usage I guess?). But it does if a connection dies beneath you whilst being watched.
In some cases deoplete just blows up while working, while repl is just fine still (fireplace works etc.)
But could be related to other completions maybe, I feel like it often happens when switching to Less files...
Hmm, not sure on the cause of that. I don't use deoplete for much outside clojure tbh. Get me the stacktrace if you can, I'd be interested in seeing it.
The watchable branch is my daily driver now, the only thing holding me off merging to master was waiting to see if cemerick would merge my patch or not.
I guess not.
I need to play and see if
git submodule update or whatever the command is, will change the submodule url if it changes (my cursory google said no)
I can safely point it at my branch of
python_nrepl_client, we might want to move that into
clojure-vim if we use it though.
Possibly not. I just don't understand licenses at all. I want something people can do whatever they want with pretty much. I don't want future people to worry about falling foul of a license by forking our library and including it in their repo to fix things.
I kinda understand that building on a fork is okay though, which is why submodules are okay. So building on https://github.com/SevereOverfl0w/nrepl-python-client is probably okay.
Problem with the more permissive licenses like WTFPL and CC0 is that they are probably not valid in many jurisdictions
> It's not global. It doesn't make sense outside of a commonwealth ecosystem, is explicitly illegal in some places (Germany), and of unclear legality in others (Australia)
MIT looks pretty similar based on the summaries anyway. The only real restriction is retaining copyright notices. Which is fine by me.
> Its applicability is unpredictable The license is short, clearly expressing intent, at the cost of not carefully addressing common license, copy-right and warranty issues. It leaves a lot of leeway interpretation - meaning that, in the US, it will take a few trials before you can reliably know when the license is applicable, and how.
MIT looks pretty good now I'm comparing it to something that tries to be public domain. I don't care much for the copyright notice, I assume it only applies to the source code it's included in though.
nrepl-python-client is MIT too. So we can build on it. I could copy/paste it into clj-async-omni too if needed, as there's no copyright notices.
I wonder how MIT applies with contributors (is each intended to add their copyright?). I should probably buy a book on license laws for developers.
Can I use MIT-licensed code in closed-source software? Yes, however the copyright notice and permission notice must be included in the documentation or EULA of your Software. For example: "This software uses <library name> - see library-license.txt". How do I display the MIT License if my project has no documentation or “about” feature? Contact the author. If the author agrees, a notice on your product website may suffice as documentation.
https://www.quora.com/If-I-make-a-project-with-the-MIT-license-do-contributors-own-the-code-that-they-commit this is my concern I guess
> One might argue in court that by submitting a pull request, that person has granted you an implicit license, and that's what a lot of open source projects rely on
I've seen a project where a developer went back and revoked his code as it was still under his copyright. To kill a project.
Having read that FAQ, I think using Cemerick's library via copy/paste would be easy. We just have to add a line somewhere.
like https://github.com/adzerk-oss/boot-cljs#license, just another line "Copyright ©2013 Chas Emerick and other contributors, for original nrepl-python-client code"
does anyone know of anything equivalent to vim-clojure-highlight for clojurescript?
my current vim setup for clojure is near-perfect but not having highlighted local/referred vars for cljs is annoying 😛