HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
onivim
oni
TypeScript2016–2021
onivim / oni · Archived

oni

Oni: Modern Modal Editing - powered by Neovim

Developer ToolsWeb DevelopmentMobile & Desktop
Explore on GitHubRead Hacker News discussions
21Distinct people
34Mentions
0Explicit recommenders
11.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Oni: Modern Modal Editing - powered by Neovim

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:01:32 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year34 dated mentions

Observed mentions: 2016-12-05 23:37:12 UTC to 2021-01-13 10:11:01 UTC.

051015202016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 22 mentions; 4 submissions, 18 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC523
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC22418
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

22 sources
rraval·Sep 6, 2018
I would really love to ditch more of my nvim setup for vscode, but this bug [1] from 3 months ago absolutely wrecks my productivity. I rely on splits as the primary means to navigate the codebase and having a single cursor position per file is maddening! The vim bindings aren't perfect and are sometimes slow (you can see a macro insert things character by character) but about on-par with IdeaVim for the IntelliJ side feature wise. Maybe oni [2] will catch up before vscode fixes their issues but I eagerly await a decent language server modal editing setup. [1] https://github.com/VSCodeVim/Vim/issues/2688 [2] https://github.com/onivim/oni
In Python in Visual Studio Code
justinmk·Jun 11, 2018
ActualVim (a plugin for Sublime Text 3) implemented support for the Nvim 0.3 "buffer updates" feature in less than 24 hours: https://github.com/lunixbochs/ActualVim/commit/414e8d4c3feb4... Oni[1] is also expected to use the feature soon. Other features worth noting are - <Cmd> key https://github.com/neovim/neovim/pull/4419 - stdpath() function https://github.com/neovim/neovim/pull/6272 https://github.com/neovim/neovim/pull/7679 and https://github.com/neovim/neovim/pull/8226 are small but nice quality-of-life improvements. There's also many new API features and defaults tweaks listed in the release notes. Oh, and a built-in AST-producing VimL expression parser: https://github.com/neovim/neovim/pull/7234 That's a big one. [1] https://github.com/onivim/oni
In Neovim 0.3 released
bryphe·May 4, 2018
> I hate these posts, because Hacker News is incapable of talking about an Electron based project productively. Oni maintainer here! I agree - I get stressed out sometimes when this gets posted to HN for that reason ;) I'll piggyback here because this is near the top, but I'll give a couple quick reasons why Electron was chosen for this project: - Development speed As mentioned in another comment, the React ecosystem has some excellent development tools around hot-reloading / live-reloading. I never found this sort of 'live-reload' workflow in any of the C/C++ toolchains I've used. (Would be interested if that has changed!) For a very small team, this is an important consideration! It's the difference between Oni existing as an Electron app vs. not existing at all. - Developers Oni is an open source project, and I open-sourced it because
Read the rest
I wanted help building it (and I've been fortunate to work with some amazing contributors [1]). When you look at the last StackOverflow Developer Survey [2], web tech is overwhelmingly at the top - if I want help, I should pick the tech stack that has the broadest appeal. Every editor is an exercise in trade-offs, and of course Electron brings trade-offs of its own. Oni is an experiment in a different (not necessarily better, because that's subjective and relative to each person's workflow) set of trade-offs than other editors - an attempt to bring together the "modern" functionality of editors like Code/Atom with Vim. It resonates with some people, but it's not going to be for everyone, and that's OK. Even if you don't use Oni or agree with the tech stack, these sorts of experiments are important, because if new ideas or workflows work well... they can find their way into your editor of choice, too. One other note - I focused a lot on Electron, but the project wouldn't be here without neovim, either! They've done excellent work, and there is quite a variety of front-ends - so even if Oni isn't your thing, I'd encourage to check out that project as well as some of the front-ends for it [3]. [1] - https://github.com/onivim/oni/graphs/contributors [2] - https://insights.stackoverflow.com/survey/2018/#technology [3] - https://github.com/neovim/neovim/wiki/Related-projects
In Oni – Modern Modal Editing
badosu·Mar 26, 2018
I did not downvote you but here are some possible reasons: 1. If you're coming from regular vim you should expect having to bundle syntax files for languages that aren't hugely popular. 2. Shortcuts on a vim frontend should be pretty self-evident for a regular vim user. And some reading on the documentation as well until the 1.0 release. 3. This is a good point, but you did not clarify your point well as I assume you meant discoverability and ease-of-use of configuration. Still, I think it's valuable feedback and actually captures some issues that are being worked now: 1. People coming from IDEs expect everything to work out-of-box and perhaps in the future some plugins will be bundled by default (configurable to not be the case for veteran users). 2. Recently a lot of features out of regular vim were added such as markdown preview, brows
Read the rest
er tab, file explorer and sneak mode; which have particular keybindings. For the moment they should be visible when you run the 'Quick Open' menu (`<c-p>`) but seems like there should be another way to discover these. An issue will be opened for this case. 3. Discoverability of options and configuration UI is a current issue indeed and there are plans to improve it (https://github.com/onivim/oni/issues/976). I hope the downvotes do not discourage you from giving further feedback as it's best when given sincerely, issues are very welcome, thanks!
In Oni: Modern Modal Editing – Powered by Neovim
bryphe·Mar 25, 2018
If you're comparing Oni to Atom, the architecture is actually quite different. Oni uses Neovim at the core to manage buffers & buffer manipulation (in other words, a native layer vs JavaScript in Atom) - this is a major benefit when working with large files. In addition, Oni uses a canvas renderer for the editor surface vs the DOM used by Atom. Together, these significantly improve the responsiveness of the tool. Architecturally, Oni is more similiar to the Xray project being investigated by the GitHub team: https://github.com/atom/xray. Most neovim plugins work great with Oni :) Just set the `oni.loadInitVim` configuration value to `true`: https://github.com/onivim/oni/wiki/Configuration#oni
In Oni: Modern Modal Editing – Powered by Neovim

Showing the 15 most recent of 22 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.