Fork me on GitHub

Conjure v2.1.0 is out with support for evaluating a form at any given Neovim mark! This means you can evaluate things from other parts of your buffer while you work elsewhere, or even in different files and namespaces! - intro guide > x-post from #announcements


oh damn that's sweet


Thatโ€™s an awesome feature!


i'm super stoked about this feature. i think it could be a game changer


while we're talking about marks, i've been using lately and finding it indispensible

๐Ÿ˜Ž 4

it's really handy being able to see where my marks are


it also provides some very useful bindings for dealing with marks, like like m, to place the next available mark, so you don't have to think about what marks you've placed already


I used that for a long while. It didn't survive a rewrite of my vimrc, because I don't use marks often enough.


i keep forgetting that marks are a thing ๐Ÿ˜„


i'm so used to just remembering what buffers things are in and using / to search for the place i want to go


or jumping to definitions via vim-fzf's :Tags


marks are occasionally very handy though, for those situations where you're jumping back and forth between implementation and usage

Jan K16:11:51

I use vim-cljfmt often and sadly it wipes away marks when reformatting ๐Ÿ˜ž

๐Ÿ˜ฒ 4
๐Ÿ˜ข 4

That's terrible!

Jan K17:11:15

Yeah it's not great. Since reformatting can collapse lines, even if it kept marks they might point to a different place after a reformat, unless there was some magic. Even so I prefer on-demand reformatting to parinfer.


Marks track movements. They aren't pinned to a particular line number.


I wonder if the nvim api resolves some of that.

Jan K17:11:36

(vim-)cljfmt formats the whole file at once, it clears the buffer and puts the formatted version in place, so vim can't map the marks


Seems like it could easily do a line by line comparison. Only set the new stuff.

Jan K17:11:25

Maybe, I would use that kind of a plugin ๐Ÿ™‚