Ryan

Physics Programmer @ Warwick Uni, working on Pandora Reconstruction for @Microboone, and SWIFT-HEP. He/Him.

[Ryan @RyanCrosss]

@that_anokha_boy @paulg @garrytan The more interesting part to me is how they are using the VSCode Marketplace. The Terms of Use is very clear it is only for VSCode & other MS products. There is a reason VSCodium can't use it, even as a fork.

Same goes for the WSL extension they talk about in their blog.

[Lucas Pluvinage @TheLortex]

How to find the minimum of a list in OCaml, thanks to Github Copilot. True OCaml proficiency happening here

[Ryan @RyanCrosss]

@flukejones @oni_vim We've got the basics of this hooked up (https://t.co/dgBv5Rj1N7) for format on save. If there is other on save actions, I think we'd need to check them.

Instructions for that PR can be found in the docs under formatting.

[Ryan @RyanCrosss]

@matdsoupe @oni_vim Its actually built in to Oni2! Its under the command palette as "Key Displayer".

[Deep Underground Neutrino Experiment @DUNEScience]

Our first collaboration meeting of 2021 draws to a close. We had a record turnout. The progress in this challenging year has been nothing but impressive. Now, time to get back to it. #dunescience #neutrinos #international #pandemicmeetings

[Ryan @RyanCrosss]

@jordwalke Especially so if you can use all the vim magic with multiple cursors, like . repeat, macros etcetc!

[Ryan @RyanCrosss]

@jordwalke Multiple cursors are great. I wish more people looked at their usage as an alternative to macros/substitutions etc, rather than a direct competitor. Some problems are just more intuitive with them, regardless that a vim macro can do it as well.

[Ryan @RyanCrosss]

@ajinkyax @oni_vim We support them both via the VSCode extension host.

Current features and setup instructions are here: https://t.co/zUvrYxypWZ.

There is also instructions in there for building if you wanted to try it out.

[Ryan @RyanCrosss]

@maxwedwards @oni_vim @bryphe I think this is the first blog post on the website, the previous release notes have been on Patreon.

Once that PR is merged, the site should be updated to inlcude it.

[Ryan @RyanCrosss]

@fasterthanlime I would expect that to work the same as VSCode! We recently swapped to using https://t.co/IE5N4KEyoU to power the search, which has similar results to Code/FZF and similar (though is in C, which is much easier for us to wrap and use).

[Ryan @RyanCrosss]

@fasterthanlime Huh! A bug report for the separator would be nice, I don't believe we have one. I admittedly never search for them, I just use the folder names alone, so I hadn't thought to check it when adding it!

We would like to swap to a file name first UI too, to help the overflow issue.

[Ryan @RyanCrosss]

@sfermigier @oni_vim I stuck a comment in our subreddit about this: https://t.co/lQ7rpUmbPr

You can also jump in our Discord if you want to see @bryphe talking about this rather than a random link.

[Ryan @RyanCrosss]

@davydog187 @thomassyy @oni_vim There is steps in the User manual for how to build, a license is only required for commercial work (and right now, a license also gets you a pre-built copy).

We ship with a set of languages, but since we use VSCode extensions, its easy enough to install one for a new lang.

[Ryan @RyanCrosss]

@jimeno0 @oni_vim @bryphe Its somewhat recent, you'd have to check your commit hash in :version, or up date to the latest builds.

Looks like it was added last month: https://t.co/BaK78TZcu1

That should also give you an idea of the binds etc (shown in the corner of the GIF)

[Ryan @RyanCrosss]

@glarses1 Licensing is a giant pain, which is why stuff like the nice!nano (bluetooth pro micro-ish for kb kits) are sold as modules, the licensing is different when not attached.

Then once you get past that, you hit the issues with QMK not being the best for BT (which is why ZMK exists).

[Ryan @RyanCrosss]

@rahulballal7 @oni_vim Its free for non-commercial work, and we've got some instructions to build it from source (https://t.co/4KzXqWG5Xf)

That is how I usually recommend people try it out at first.

When we get our MVP finished, free builds should go up on the site as well.

[Ryan @RyanCrosss]

@tkolleh_ @avsm @oni_vim That said, we do need to improve the docs around the Oni2 specific binds, since there is some cases where they need to be defined in Oni2, not Vim (usually due to match behaviour in other parts of the UI).

[Ryan @RyanCrosss]

@tkolleh_ @avsm @oni_vim The hope is that a lot of those keybinds don't need porting, and the usual "nnoremap"/"map" etc you already use will just work!

Current work is to improve the Vim portion of OniVim, which includes mappings and some plugins. So hopefully soon there won't need to be any porting.