Fork me on GitHub
#vim
<
2018-05-24
>
eraserhd16:05:50

Hey, using vim-fireplace, I occasionally, accidentally open function docs (the kind one gets with K) in the preview window. I'd like to do this on purpose, but I haven't been able to figure out how. Anybody here know?

dominicm16:05:18

@eraserhd I don't suppose you're doing that as part of omni-completion?

eraserhd16:05:36

uhhh, maybe?

eraserhd16:05:57

I very rarely use omni-complete, actually... I find ^P sufficient and faster must of the time. But it's possible.

fatihict17:05:54

I also do this with autocompletion. I want to turn it off 😅

fatihict17:05:10

I haven't figured it out yet

dominicm17:05:37

@fatihict I have a compromise I love:

augroup CompletionGroup
  autocmd!
  autocmd CompleteDone * pclose!
augroup END
It closes the preview after completion

dominicm17:05:44

Otherwise modify 'completeopt'

dave17:05:00

^i do this too

dave17:05:07

i found it in the deoplete readme or something

fatihict18:05:53

Oh nice. Thanks!

uwo21:05:49

little question here. with vim-sexp when I create a new pair (f) and then slurp the next expression in, I end up with two spaces between some-fn and the next expression. any way to prevent this?

uwo21:05:51

omg. i’m so silly. ignore the above!!!

uwo21:05:19

I won’t erase it so that I am properly humbled, lol

dominicm21:05:58

@uwo how did you solve it? I may always do this, I'm not sure.

uwo21:05:34

I was typing a space after f, like (f ) and then slurping

uwo21:05:43

all i had to do was not type the space

uwo21:05:29

though here’s another one for you. is there anyway to bind <Plug> bindings in insertmode, like with inoremap?

dominicm21:05:30

I think so, but you use imap for plug mappings

uwo21:05:55

ha! thanks. that was my problem