Clojurians Log v2

I pushed another update to Proto REPL that should fix the last of the problems with the latest version of Atom Ink. Code completion works in the console and inline values are displayed correctly.

I'm trying to set up proto-repl the first time and having issues, is this the right place for asking for help?

according to this: https://gist.github.com/jasongilman/d1f70507bed021b48625, one needs to uncheck keybindings for lisp-paredit

Was this your stack overflow question? http://stackoverflow.com/questions/39059778/execute-clojure-block-or-selection-doesnt-work-in-atom-proto-repl

then I seem to be missing slurping (and other) behaviors (i.e. (ctrl-alt-.). Am I on the right track? I wanted to revert to the original version of lisp-paredit to reinstate all the keybindings, but that is not working

yes, that was me as well

Yeah if you want to use the lisp paredit keybindings like slurp etc you should reenable them.

I think that one of them conflicts with a Proto REPL keybinding though but most of them should be ok.

how do I re-enable them? cant seem to figure out

Do you know how to get to lisp paredit settings?

you mean in the file system?

Within Atom

You should open Atom settings then go to Packages, find lisp-paredit, and click on its settings.

ok, I'm there

Toward the bottom should be a checkbox for keybindings.

It should be one click to enable all of them.

no, that was disabled when I followed instructions on that link

and now there's no checkbox

I would uninstall lisp paredit and reinstall it at this point.

I tried it multiple times, that doesn't seem to do it

it persists the change somewhere

I wonder if you changed something on the file system then. After you uninstall it look for a .atom/packages folder

That's in my home directory on my Mac

If lisp paredit is there then delete the lisp paredit folder.

Yes, I found that file, I was watching the filesystem - the reinstall of the plugin reinstalls that folder as well

but it doesn't fix the problem

I think it gets persisted on a higher level than that plugin

Ah I think it might be in another one of the atom config files.

I've seen that before but I can't remember exactly where it is.

yes, I think so

Somewhere in .atom near your user init and keybindings.

I think it's called config.cson

Yeah it's mentioned here http://flight-manual.atom.io/using-atom/sections/basic-customization/

I don't see it there either:

looks like it's same as what I see through Atom, but where's 'the initial setting, how does one revert back?

I think there might be a separate list of keybinding disabled packages in that file but I might be wrong. You can also try removing lisp paredit from that file completely. Restarting Atom between uninstall and install may be a good idea as well.

damn, that is so painful

Sorry 😟

It's not usually like this.

that's why I'm wondering, could it all be working on Mac and now on Win?

I'm pretty sure at least a few people are using it on Windows. I originally did testing on Windows but haven't in a while since recent changes aren't OS specific.

Did you get past the lisp paredit problem?

hm, interesting

no

reading their doc, it says: ctrl-alt-, is for forward slurping , and the same combo plus a 'b' is for sending a block to a repl, would it not be conflicting?

This might be a bit of a hack but you could copy the lisp paredit keybindings into your own keybinding file. https://github.com/jonspalding/lisp-paredit/blob/master/keymaps/lisp-paredit.cson

Yes that would conflict. Keybindings are tricky. I already changed them a few times to avoid conflicts.

I should add a way to choose your own prefix set of keys or alternatives

so seems like you are right in saying that it needs to be disabled, the trick is how to get it back

let me try what you are suggesting with the cson file

I need to go to bed now. Good luck. Please let me know what you're able to figure out. I'm interested in improving it for others who use paredit and/or Windows.

hey, good night, thanks for trying to help!

nah, those mappings are there already