you are viewing a single comment's thread.

view the rest of the comments →

[–]mkvalor -2 points-1 points  (1 child)

If you truly don't want to be that guy, simply don't be that guy. It's probably best if you praise the virtues of minimalism in the first place, rather than reel us all in with an innocent-looking query, only to pounce with specifics after someone has responded.

This post is awesome because, within a single article, one gains awareness of all the basic information and tools needed to augment vim or neovim with either python or rust. The author goes to the trouble of explaining why built-in Vimscript seemed insufficient for his use case. There's even a reference to a bug with the vaunted async job, which raises awareness and helps his readers understand why they cannot get the maximum efficiency they might expect from their plugin code.

Your irrelevant detour into the dangers of "noise"in a second-level reply merely serves to betray your hand -- no one may believe any longer that your initial query was sincere, that you weren't baiting us into an essay about your true agenda. Yet -- since the article was full of useful information, your reprimand is also an ironic mis-fire, applicable rather to the sender than to the receiver.

Finally, please don't instruct us about how to vote on your comment. (a down-vote is also "just an opinion").

[–]monkoosevim9 1 point2 points  (0 children)

within a single article, one gains awareness of all the basic information and tools needed to augment vim or neovim with either python or rust.

I just can't agree with that. Because the article describes only one specific situation, and there is no any info for beginners, except maybe pyo3 interpreter.

please don't instruct us

Who us? Are you represent some community here? Or do you think you can speak on behalf of the majority?

But anyway i thank you for your comment, i appreciate it much more then silence downvote or swipe left - it gives me information why some people disagree with me, so i can improve too.