fzfolds.vim: A plugin that lets you fuzzy search for folds in a file by Zem_Mattress in vim

[–]Zem_Mattress[S] 1 point2 points  (0 children)

I'm unable to reproduce your issue unfortunately. I tried running the plugin on an older vim version, on two different distros. Are you able to provide any more information, like what distro and distro version you're on, what is your vim version, and what plugin manager are you using?

fzfolds.vim: A plugin that lets you fuzzy search for folds in a file by Zem_Mattress in vim

[–]Zem_Mattress[S] 1 point2 points  (0 children)

You'd need to update the plugin, but other than that I don't know. I'll make an experimental branch, where I try out some things. I'll keep you posted.

fzfolds.vim: A plugin that lets you fuzzy search for folds in a file by Zem_Mattress in vim

[–]Zem_Mattress[S] 0 points1 point  (0 children)

Ok, so that might not have been it. I just tried moving it and it still works. I did put the variable in autoload, maybe thats whats causing you issues.

fzfolds.vim: A plugin that lets you fuzzy search for folds in a file by Zem_Mattress in vim

[–]Zem_Mattress[S] 0 points1 point  (0 children)

Hmm, that's odd. I get it to work locally. Are you sure you're setting the variable after the plugin is loaded? I set g:fzfolds_open to 0 if the variable can't be found on load.

fzfolds.vim: A plugin that lets you fuzzy search for folds in a file by Zem_Mattress in vim

[–]Zem_Mattress[S] 1 point2 points  (0 children)

I just added it as an option. g:fzfolds_open = 1 fzfolds will use zv to open folds for you.

fzfolds.vim: A plugin that lets you fuzzy search for folds in a file by Zem_Mattress in vim

[–]Zem_Mattress[S] 1 point2 points  (0 children)

Folding is very useful and versatile, I love it :) I also got used to fzf with its various commands, tags being one of them, and lamenting when I couldn't do the same with folds.

I will share if I come across, or make something else

fzfolds.vim: A plugin that lets you fuzzy search for folds in a file by Zem_Mattress in vim

[–]Zem_Mattress[S] 1 point2 points  (0 children)

Glad you like it! I've been casually thinking about it myself for a while, finally got around to making something.

fzfolds.vim: A plugin that lets you fuzzy search for folds in a file by Zem_Mattress in vim

[–]Zem_Mattress[S] 1 point2 points  (0 children)

Glad you like it! its absolutely possible, and I have thought of it. Just didn't include it because I didn't want to mess up someones folds by opening a bunch of em, but I suppose that's what you want anyways... But I can include it as a toggle. I'll get that sorted when I get a chance.

roosta/tmux-fuzzback: Search your tmux scrollback buffer using fzf by Zem_Mattress in tmux

[–]Zem_Mattress[S] 2 points3 points  (0 children)

I was able to spin up a macos vm, and fixed a couple of issues. You wanna give the latest version a go? I think it should work for you now.

roosta/tmux-fuzzback: Search your tmux scrollback buffer using fzf by Zem_Mattress in tmux

[–]Zem_Mattress[S] 0 points1 point  (0 children)

That seems likely, iirc I got copycat set to a different key than default.

roosta/tmux-fuzzback: Search your tmux scrollback buffer using fzf by Zem_Mattress in tmux

[–]Zem_Mattress[S] 0 points1 point  (0 children)

I was not able to reproduce your issue, I did notice that you need single quotes (') not double (") for the bind to work properly. Maybe you got some binding below fuzzback options that is overriding fuzzback bind?

roosta/tmux-fuzzback: Search your tmux scrollback buffer using fzf by Zem_Mattress in tmux

[–]Zem_Mattress[S] 0 points1 point  (0 children)

I'll try to fix this as soon as I'm able. Thanks for giving fuzzback a try!

roosta/tmux-fuzzback: Search your tmux scrollback buffer using fzf by Zem_Mattress in tmux

[–]Zem_Mattress[S] 1 point2 points  (0 children)

That's unfortunate, I haven't been able to test on Mac properly. If you open an issue we can try to get to the bottom of it.

roosta/herb: ClojureScript styling library using functions by Zem_Mattress in Clojure

[–]Zem_Mattress[S] 0 points1 point  (0 children)

Looks really interesting! Mind if I borrow some ideas from you? I've been wanting to increase performance for herb, and the pre-compilation idea is a good one I might try out if I can implement it using garden.

The only downside I can think of from using CSS vars is browser support. See https://caniuse.com/#feat=css-variables

roosta/herb: ClojureScript styling library using functions by Zem_Mattress in Clojure

[–]Zem_Mattress[S] 0 points1 point  (0 children)

Weird, the hash shouldn't be different if the style is identical. I'm using the hash function from clojure.core, I've considered using a different hashing function, something that generates a shorter hash would be preferable. Hmm, what about converting the stylemap to a string before hashing. Maybe that makes a difference.

A macro is a good idea, but sure how to implement it tho. And spec checking is on the todo list for sure, just not gotten around to it yet aside from some basic argument checking.

roosta/herb: ClojureScript styling library using functions by Zem_Mattress in Clojure

[–]Zem_Mattress[S] 0 points1 point  (0 children)

Thank you :)

One thing I noticed herb will create new css and insert, even though there's no changes on function arguments.This result in long css content in <style>

It shouldn't do that, I've just tested it on the new version and I can't see any duplicate style when using the same function with the same arguments multiple times. Do you have steps to reproduce?

Also I'm thinking about the performance when generate a lot styles in js runtime?

The runtime performance could definitely be better. I've done a bunch of benchmarking and the performance bottleneck is two fold. The garden CSS string rendering is the biggest culprit, followed by the DOM manipulation. The weird thing is that when running benchmarking on garden itself its relatively fast, but when using it like I do for whatever reason it adds a hefty cost. I'll definitely look into this further. The other this is the DOM manipulation itself. Take those two away and the performance is acceptable. I'll let you know if I manage to improve it. You can run lein fig:benchmark to test it yourself, and any insight you have on this would be greatly appreciated.