Fork me on GitHub
#spacemacs
<
2017-12-11
>
clojer16:12:24

I have SBCL installed and running but after adding common-lisp to my .spacemacs I can’t get a connection inside Spacemacs.

clojer16:12:53

My Helm bar shows “Lisp [email protected]” so Slime is loaded.

vuuvi16:12:16

@clojer sorry I don’t know that much about SBCL - I’d suggest checking out the spacemacs glitter channel?

vuuvi16:12:38

and I just got exposed to the magit log mode, wow it’s awesome do you guys use it here?

jeff.terrell16:12:37

Like when you hit l l in a magit status buffer? Oh yes, I use that all the time. simple_smile

vuuvi16:12:09

do you know if there’s a keybinding for avoiding having to open the status buffer?

jeff.terrell17:12:43

I did a describe key, poked around the source a bit, and it looks like M-x magit-log-current will do what you want.

vuuvi17:12:27

oh that’s a good idea

clojer16:12:52

Fixed. I had a file open in Spacemacs while attempting to start the REPL.

vuuvi16:12:30

oh that’s a funny problem.

grzm21:12:07

I'm trying out Spacemacs and smartparens (coming from bare-bones Emacs and paredit). I'm a bit surprised by the behavior of sp-forward-slurp-sexp. (foo [|] bar) => (foo [ |bar]) (| is point) Is there a way to get it to close up that space before bar?

eggsyntax21:12:24

No easy way that I'm aware of, short of writing a custom fn and changing your keybinding to point at that.

grzm21:12:47

Is this something you've encountered? If so, do you just type backspace and move on?

eggsyntax21:12:54

Yep. Doesn't bother me that much. Someone else may have a solution, though.

grzm21:12:09

Thanks for confirming.

eggsyntax21:12:07

I definitely get identical behavior on the same case.

eggsyntax21:12:43

Makes me think it would be really nice to have a generalized "tighten up extra spaces" fn...

grzm21:12:26

That's the stock behavior in paredit

ag22:12:01

interestingly in emacs-lisp it does the right thing

grzm22:12:49

Oh? I see the same behavior: (foo bar (|) baz) => (foo bar (| baz))

ag22:12:48

oh wait... hmm... strange. I didn't see it the first time...

ag22:12:56

let me try again

ag22:12:44

oh shoot, yeah you're right... sorry I thought it worked for me first time

ag22:12:11

okay... it seems paredit-forward-slurp-sexp does the right thing, and sp-forward-slurp-sexp leaves the space

ag22:12:00

what do you use to slurp? Do you use SPC k s? or some other key?

ag22:12:01

you basically can redefine that key for lispy to use paredit-forward-slurp-sexp instead of default one.

ag22:12:18

- first you need to wrap the function, make it "lispy", so you can continuously keep slurping, e.g. SPC k s, s, s... etc.

ag22:12:42

(evil-lisp-state-enter-command paredit-forward-slurp-sexp)

ag23:12:11

that macro would create a function named evil-lisp-state-paredit-forward-slurp-sexp

ag23:12:15

- then you just bind/re-bind the key: (spacemacs/set-leader-keys "ks" 'evil-lisp-state-paredit-forward-slurp-sexp)

grzm23:12:17

@ag thanks for digging into this. When I'm using smartparens, I'm using sp-forward-slurp-sexp. I figure if I'm going to use smartparens, I should be using the smartparens commands: having two packages that do pretty much the same thing seems a step backwards to me. AFAIK, I'm not using any of the evil-mode stuff. Though, at this point (maybe it's too early to call? been trying for a week or so) I'm not sure what smartparens gives me over paredit. I like the fact that it's actually maintained, and I hear it's much more configurable, but the teething period is getting to me.