Fork me on GitHub
#vim
<
2020-08-03
>
eraserhd14:08:34

Hey, I have a few Vim issues on parinfer-rust. Since I'm no longer using Vim as my daily driver, I'm getting less familiar with how to fix things. Is anyone here interested in investigating these issues?

timo14:08:50

🙂 @U0ECYL0ET you don't use vim anymore? what do you use?

eraserhd14:08:10

heh, kakoune.

eraserhd14:08:56

It's kind of like Vim, except completely different.

timo14:08:24

😎 but vim!

timo14:08:11

I would certainly be interested in working on a fix for the history. but afaik it is vim related and not a problem with parinfer-rust, right?

eraserhd14:08:19

which issue is that? Kakoune has bad undo history issues, but Vim largely worked AFAIK.

dominicm14:08:55

I thought you had to file an issue with vim @U0ECYL0ET?

timo14:08:54

a bit like https://github.com/eraserhd/parinfer-rust/issues/14 where undo does stop undoing but incrementing the counter and redo is not possible anymore

eraserhd14:08:59

Oh, the one where some Vim builds on Mac OS have entitlements set so that Vim cannot load dynamic libraries?

timo14:08:23

I do experience this on arch linux

timo14:08:41

and a friend of mine as well on macos

dominicm14:08:43

I was thinking of this

eraserhd14:08:25

AFAIK, that's all been resolved?? I was not aware it was happening again.

timo14:08:15

Should I open an issue where we can discuss a possible solution? I could maybe help

eraserhd14:08:46

Someone recently reported something that suggests brand new Neovim is not working. That's the kind of thing I was thinking would be nice to have help on.

eraserhd14:08:31

Oh, I see that's you on #14.

eraserhd14:08:45

Let's reopen it, if it is happening again.

timo14:08:04

:thumbsup:

timo14:08:06

thanks @U0ECYL0ET for reopening. I will try to improve my vimscriptfu and help where I can

eraserhd14:08:24

np. I commented on the PR about finding Vim's regression. We should figure out if it was intentional.