Fork me on GitHub
#vim
<
2018-05-15
>
mynomoto14:05:54

I'm trying https://github.com/SevereOverfl0w/clj-refactor.nvim and getting Error: console.debug is not a function when using clean-namespace (crcn). I also tried introduce let and that is working.

dominicm14:05:14

Hmm, not sure why off the top of my head. Let me try rebuilding.

dominicm14:05:15

there are changes on rebuild, but none related to a debug.

dominicm14:05:23

Oddly, crcn worked for me, so I am not entirely sure why.

dominicm14:05:03

hmph, getting nil as an error now

dominicm14:05:42

The thing is, console.debug is always defined, that's the point of console.debug!

dominicm15:05:28

@mynomoto looks like it was my change to insert a newline!

dominicm15:05:22

(by removing it)

dominicm15:05:49

@mynomoto pushed, please try šŸ™‚

dominicm15:05:22

oh, I force pushed, sorry, that will give you issues.

dominicm15:05:27

didn't think of that.

mynomoto15:05:31

Plug didn't mind the force push šŸ˜®

mynomoto15:05:43

Oh, actually it did

dominicm15:05:46

ah šŸ™‚

dominicm15:05:51

I thought so, mine does

dominicm15:05:06

ugh, forgot to push the properly compiled assets

dominicm15:05:22

one sec, lemme do the real force push

dominicm15:05:48

bb6286c23d3fb3b1c0990876fa064de9c7b43a78 is the real MVP

dominicm15:05:04

I'll have to figure out the newline thing later, gah, that's a shame.

mynomoto15:05:12

Ok, got that now.

mynomoto15:05:00

Same error.

dominicm15:05:26

@mynomoto just to be clear, you've removed node-host from your init.vim?

mynomoto15:05:12

Yeah, no node-host there. I did npm install -g neovim

dominicm15:05:31

what's the output of:

āÆ neovim-node-host --version

dominicm15:05:41

āÆ node --version too

mynomoto15:05:18

$ neovim-node-host --version
4.0.1
$ node --version
v6.13.1

dominicm15:05:15

Did you definitely restart neovim after updating? Sorry, I'm just checking obvious things, because I have no idea why console.debug wouldn't be available!

mynomoto15:05:39

Just did it again to be sure, no difference.

mynomoto15:05:52

No problem, usually is something obvious.

dominicm15:05:53

@mynomoto if you do:

NVIM_NODE_LOG_FILE=/tmp/node.log nvim test/bidi/cider_testxxx.clj
perform the crcn, and then send me /tmp/node.log, that might help (or scan it yourself)

dominicm15:05:58

definitely missing something

mynomoto15:05:29

Also did :UpdateRemotePlugins again. Will do, just a moment.

lxsli15:05:58

@eraserhd does parinfer-rust turn itself off when in paste mode?

eraserhd15:05:46

I think so. I'm pretty sure I implemented that.

lxsli15:05:25

Hmm, something is behaving badly šŸ˜ Thanks

lxsli16:05:35

FWIW - editor takes over a minute to paste in a thin page of JSON

mynomoto16:05:00

Just to circle back on the problem I was having (`Error: console.debug is not a function`, when using https://github.com/SevereOverfl0w/clj-refactor.nvim) it was because I was using node 6 and console.debug was added on 8. @dominicm tracked the error and fixed it šŸŽ‰

ghadi17:05:33

How do I control the next line's indentation after an s/fdef with a global setting?

dominicm17:05:42

Also see :help clojure.txt

ghadi17:05:24

thanks @dominicm -- do you have any helpful settings handy? I am trying to provide my team with common config snippets for Emacs and Vim

dominicm17:05:27

@ghadi afraid not much, I gave up on having us all use the same indentation ages ago. All the editors work differently. Here's what I do have, covering a little core.async:

let g:clojure_special_indent_words = 'deftype,defrecord,reify,proxy,extend-type,extend-protocol,letfn,defcomponent'
setlocal lispwords+=go-loop,try-n-times,fdef
You can probably find more with a github search for lispwords or something