Fork me on GitHub

In my understanding, that's how CIDER works. It runs in your repl, but instead of connecting to a web server from your browser, you connect to the nrepl from emacs


@dominicm I think CIDER and nightlight are different. Nightlight's approach is to make the ide a dependency of your code. In other words, you have to open up some kind of basic text editor so you can set nightlight as a literal dependency of your project. Then when you run your project, nightlight steals the process and gives you an IDE. It literally runs inside the process.


@bcbradley CIDER is a dependency, in your profile.clj. When you run your repl, it jumps in and provides a IDE api. I'm not sure it's a good idea for a project to include nightlight by default, I'd be inclined to put it in my profile file.


to be more precise @bcbradley and @dominicm the backend for cider is a dependency (called cider-nrepl) which is implemented as an nrepl middleware. there is an emacs lisp part of cider as well, even possible that some functionality is available in cider without the middleware and repl running. that’s said in cider we eventually decided to inject the cider dependencies using the command line options to add deps in both leiningen and boot


so you only need add cider deps to your profile.clj or project file if you plan to start up a repl process and then connect to it with cider. if you jack in, so cider controls the repl process therefore can inject deps you don’t need to do that anymore


As a vim user, I do not use that feature. 😛 It would be too magic for me.


fair enough… is not there a fireplace related plugin (sorry if use the wrong vim lingo) which gives you embedded repl?


feature would make sense there


@benedek not sure if you know of it takes advantage of the editor agnostic API you guys designed, and it allows my life to be much better because of it. Thought it might show what this tiny foresight allows.


yup i am aware might have even starred it on github 😉


really happy it happened too 🙂


There isn't. For two reasons: - in plain vim, it's technically difficult due to lack of great async (though this may change) - vim doesn't have a way to display terminal ops inside a buffer afaik There's also a social problem: Vim users hate magic. I don't think auto injection would be appreciated. Vim isn't an IDE, an OS or a terminal multiplexer. It's an editor. Also, vim tends to be an editor you kill often as part of a workflow, so having applications inside it turns out badly.


fair. i guess slight differences between emacs and vim view of the world 😉


It very much is! I think my favourite example is this: Emacs 25 will ship with an embedded copy of webkit, presumably for things like markdown preview. Vim was embedded inside electron to achieve a similar thing:


I feel like the approach is inverted, which isn't bad, just a different means to the same goal. Not entirely incompatible either.


well emacs is a bit chaotic, messy I guess.. I love that chaos tho obviously 😉


@benedek also way more "kitchen sink" Everything is a plugin in vim. Usually several. And you've often got to stick them together (or use another plugin which has...). It's another form of chaos!


haha, i prefer these to any IDE tho