conjure

:neovim:+:clj: https://github.com/Olical/conjure - If you're enjoying Conjure and want to say thanks: https://github.com/users/Olical/sponsorship :smile: (alt https://conjure.fun/discord)
nate 2021-02-15T01:45:06.101300Z

I'm seeing a bit of an odd behavior with the latest Conjure develop branch

Olical 2021-02-15T10:46:02.102800Z

Oh no! So sorry to hear that. Do you happen to have vim-repeat installed?

Olical 2021-02-15T10:51:44.103Z

Hmm, I can't reproduce this with or without vim-repeat :thinking_face: guessing it's something else conflicting.

Olical 2021-02-15T11:32:48.103300Z

Oh! Maybe your prefix / localleader is single quote?

Olical 2021-02-15T11:44:28.103500Z

Is develop any different for you now? I changed how I'm quoting / escaping things, should be safe in all cases now.

dharrigan 2021-02-15T12:16:15.103700Z

Can't say I observed what Nate saw (probably because I didn't pay attention), but so far, for me, if I do ,eb, the buffer is not marked modified

dharrigan 2021-02-15T12:16:46.103900Z

,ef shows no modifications either. Here's hoping it's okay for Nate now 🙂

Olical 2021-02-15T13:52:57.104100Z

I have a feeling it was some vimscript I was concatenating together and evaluating (which included a single quoted string) conflicting with a mapping that included a single quote (thus, closing the string early) and causing weird things to happen. Complete guess and possibly wrong, but I still fixed that string building and escaping so this can't happen. Maybe there's another issue out there, but that was definitely a hole that needed fixing.

nate 2021-02-15T15:21:02.104800Z

hm... I do have vim-repeat installed and , is my leader

nate 2021-02-15T15:21:17.105Z

let me try latest develop

nate 2021-02-15T15:22:53.105200Z

yup, still happens

nate 2021-02-15T15:23:02.105400Z

I'll have to dig through my vim config and see what's causing this

nate 2021-02-15T15:23:55.105700Z

glad to hear it's not happening for others

nate 2021-02-15T15:39:11.105900Z

@olical I was using a very old version of vim-repeat. I updated to the latest and the problem went away

dharrigan 2021-02-15T15:48:44.106100Z

I can recommend using vim plug to update regularly 🙂

nate 2021-02-15T15:51:42.106400Z

ah yes

nate 2021-02-15T15:51:54.106600Z

I'm an old pathogen user still

nate 2021-02-15T15:52:33.106800Z

keep meaning to try out these newer plugin managers

nate 2021-02-15T15:52:45.107Z

I'll check out vim plug

Olical 2021-02-15T16:24:02.107500Z

Oh nice! Well I fixed a potential bug anyway 😅 so I guess vim-repeat changed their API at some point :thinking_face:

nate 2021-02-15T01:46:24.101500Z

If I run ,ef or any other mapping to evaluate code, my buffer is marked as modified

nate 2021-02-15T01:49:50.101700Z

doesn't seem to affect v4.10.0

nate 2021-02-15T01:50:15.102100Z

trying to narrow it down

nate 2021-02-15T01:53:04.102300Z

v4.13.0 is fine too

nate 2021-02-15T01:57:13.102500Z

The first commit that has the bug for me is 4108f7c

2021-02-15T10:19:51.102700Z

Olical 2021-02-15T10:46:02.102800Z

Oh no! So sorry to hear that. Do you happen to have vim-repeat installed?

Olical 2021-02-15T10:51:44.103Z

Hmm, I can't reproduce this with or without vim-repeat :thinking_face: guessing it's something else conflicting.

2021-02-15T10:57:17.103200Z

Olical 2021-02-15T11:32:48.103300Z

Oh! Maybe your prefix / localleader is single quote?

Olical 2021-02-15T11:44:28.103500Z

Is develop any different for you now? I changed how I'm quoting / escaping things, should be safe in all cases now.

dharrigan 2021-02-15T12:16:15.103700Z

Can't say I observed what Nate saw (probably because I didn't pay attention), but so far, for me, if I do ,eb, the buffer is not marked modified

dharrigan 2021-02-15T12:16:46.103900Z

,ef shows no modifications either. Here's hoping it's okay for Nate now 🙂

Olical 2021-02-15T13:52:57.104100Z

I have a feeling it was some vimscript I was concatenating together and evaluating (which included a single quoted string) conflicting with a mapping that included a single quote (thus, closing the string early) and causing weird things to happen. Complete guess and possibly wrong, but I still fixed that string building and escaping so this can't happen. Maybe there's another issue out there, but that was definitely a hole that needed fixing.

nate 2021-02-15T15:21:02.104800Z

hm... I do have vim-repeat installed and , is my leader

nate 2021-02-15T15:21:17.105Z

let me try latest develop

nate 2021-02-15T15:22:53.105200Z

yup, still happens

nate 2021-02-15T15:23:02.105400Z

I'll have to dig through my vim config and see what's causing this

nate 2021-02-15T15:23:55.105700Z

glad to hear it's not happening for others

nate 2021-02-15T15:39:11.105900Z

@olical I was using a very old version of vim-repeat. I updated to the latest and the problem went away

dharrigan 2021-02-15T15:48:44.106100Z

I can recommend using vim plug to update regularly 🙂

nate 2021-02-15T15:51:42.106400Z

ah yes

nate 2021-02-15T15:51:54.106600Z

I'm an old pathogen user still

nate 2021-02-15T15:52:33.106800Z

keep meaning to try out these newer plugin managers

nate 2021-02-15T15:52:45.107Z

I'll check out vim plug

Olical 2021-02-15T16:24:02.107500Z

Oh nice! Well I fixed a potential bug anyway 😅 so I guess vim-repeat changed their API at some point :thinking_face: