|
| 1 | +--- |
| 2 | +title: August 2021: 0.5.7 Release |
| 3 | +author: Bryan Phelps |
| 4 | +authorURL: http://twitter.com/bryphe |
| 5 | +--- |
| 6 | + |
| 7 | +## What's New |
| 8 | + |
| 9 | +It's been kind of a hectic couple of months for me personally, but there's been a lot of exciting things happening in the project. |
| 10 | + |
| 11 | +### Emoji & Symbols Panel on macOS |
| 12 | + |
| 13 | +TODO: Image / gif |
| 14 | + |
| 15 | +Emojis are easier than ever to type in Onivim 2 on macOS! Zach added an integration to the macOS native emoji panel [#3613](https://github.com/onivim/oni2/pull/3613). |
| 16 | + |
| 17 | +No longer will you have to leave your editor to find that perfect emoji :nerd: |
| 18 | + |
| 19 | +### Search Improvements |
| 20 | + |
| 21 | +TODO: Image / gif |
| 22 | + |
| 23 | +Zach has also made several improvements to the search pane. Toggleable regex-based search, ability to include or exclude files to search, as well as a case-sensitivity togglehave all been added to the search pane. We hope that these changes make finding text in your project easier! |
| 24 | + |
| 25 | +### Right-click Menus |
| 26 | + |
| 27 | +TODO: Image |
| 28 | + |
| 29 | +Rounding out the changes made by Zach, right-click menus are now supported in Onivim 2! |
| 30 | + |
| 31 | +For now, it's mostly just the setup work, such that we can start incorporating this into new features - but the fact the feature has landed means we can start to integrate more. |
| 32 | + |
| 33 | +Fear not though, Onivim 2 is first and foremost keyboard driven, so there will always be a way to achieve actions via the keyboard. |
| 34 | + |
| 35 | +### Quick-open Binds |
| 36 | + |
| 37 | +Finally, Ryan has added some basic bindings to the quick-open menu (that is the <kbd>Control</kbd>+<kbd>p</kbd> menu on Windows/Linux, <kbd>Command</kbd>+<kbd>P</kbd> menu on macOS). These bindings let you open a file in various ways, instead of just replacing the current buffer (which is the current <kbd>Enter</kbd> behavior). |
| 38 | + |
| 39 | +You can now open in a new horizontal or vertical split, or into a new tab (though that makes more sense with [Vim style tabs](https://onivim.github.io/docs/getting-started/vim-tips#how-do-i-get-the-tabs-to-behave-as-they-do-in-vim)). |
| 40 | + |
| 41 | +The default bindings are: |
| 42 | +- <kbd>Shift</kbd>+<kbd>Enter</kbd>: Open in a new _vertical_ split |
| 43 | +- <kbd>Control</kbd>+<kbd>x</kbd>: Open in a new _horizontal_ split |
| 44 | +- <kbd>Control</kbd>+<kbd>t</kbd>: Open in new tab |
| 45 | + |
| 46 | +These default bindings can be changed, with the commands used listed [here](https://onivim.github.io/docs/configuration/key-bindings#list--menu-commands). |
| 47 | + |
| 48 | +### Titlebar Changes |
| 49 | + |
| 50 | +The titlebar now has the option to pick between our custom Onivim 2 themed title bar, and a default OS themed one. Our custom title bar looks nice, since it can leverage theme colors. However, on some platforms - particularly Windows - the native title bar behaves better. There were some annoying usability bugs with our custom titlebar (windows shortcut keys not working, window overflowing to other screens, etc) - for this reason, the native titlebar is now the default on Windows. |
| 51 | + |
| 52 | +The titlebar style can be adjusted with this configuration option: |
| 53 | + |
| 54 | +``` |
| 55 | +"window.titleBarStyle": "custom" |
| 56 | +``` |
| 57 | + |
| 58 | +## Bug Fixes |
| 59 | + |
| 60 | +### Vim compatibility changes |
| 61 | + |
| 62 | +Lots of changes went into to solidify and smooth over the connection to `libvim`, the |
| 63 | +Vim heart of Oni2, to help make certain behaviours in Oni2 act more like they do in |
| 64 | +terminal Vim: |
| 65 | + |
| 66 | + - #3606 - Vim: Fix hang when using `function` in `experimental.viml` |
| 67 | + - #3607 - Vim: Fix crash when specifying empty guifont (fixes #3605) |
| 68 | + - #3699 - Vim: Respect silent flag for output-producing commands (fixes #3680) |
| 69 | + - #3755 - Vim: Fix extra 'editor tab' with `:tabnew`/`:tabedit` (fixes #3150) |
| 70 | + |
| 71 | +### VSCode Extension host changes |
| 72 | + |
| 73 | +Similarly, lots of changes have landed that improve and extend our VSCode extension host |
| 74 | +compatibility. Of note is that whilst some of these issues are "extension specific", we |
| 75 | +aren't special casing any extensions. If we fix a bug with one extension, its very |
| 76 | +likely to help unblock many others as well! |
| 77 | + |
| 78 | + - #3431 - Extensions: Serialize file system errors correctly to extensions (fixes #3418) |
| 79 | + - #3637 - Extensions: Unable to enter API key for WakaTime (fixes #3619) |
| 80 | + - #3571 - Extension: Implement `$tryApplyEdits` (fixes #3545) |
| 81 | + - #3335 - Extension: Fix selection bounds (fixes #3335) |
| 82 | + - #3709 - Extension: Fix activation error with nim extension (fixes #3685) |
| 83 | + - #3746 - Extension: Fix edit application in trailing spaces plugin |
| 84 | + - #3753 - Extension: Don't bubble up extension runtime errors to notifications |
| 85 | + - #3745 - Dependency: vscode-exthost -> 1.57.1 |
| 86 | + |
| 87 | +The full set of changes is available in the [changelog](https://github.com/onivim/oni2/blob/0cd8c424d5fb0bcdf209070ec3ab6296a3654eba/CHANGES_CURRENT.md). We hope that these help make Onivim 2 even better for you. |
| 88 | + |
| 89 | +## Special Thanks |
| 90 | + |
| 91 | +We had @sijad submit a nice fix for a stuck menu state, fixing an annoying UX issue and |
| 92 | +getting a license key! (#3668). |
| 93 | + |
| 94 | +@eEQK sorted a build issue where Oni2 wasn't building correctly when kicked off a |
| 95 | +certain way. |
| 96 | + |
| 97 | +We also received a few documentation updates this release, which is always very appreciated! |
| 98 | +Updating documentation is something that most people can do and it really helps us out, |
| 99 | +as well as helping out your fellow users! |
| 100 | + |
| 101 | + - @rogererens - Updating the Visual Mode documentation. (#3601) |
| 102 | + - @paul-louyot - Filling in some missing parts for the keybinding documentation. (#3626) |
| 103 | + - @Doerge - Tidying up some dead links in our getting started documentation. (#3740) |
| 104 | + |
| 105 | +## What's Next |
| 106 | + |
| 107 | +As mentioned in the beginning, it's been a challenging couple of months for the project. I'll elaborate a bit more in the next set of release notes. |
| 108 | + |
| 109 | +There are several items that are top of mind for me next, including: |
| 110 | +- Syntax highlighting improvements |
| 111 | +- Code actions / refactoring |
| 112 | + |
| 113 | +Thank you for reading and following the project - huge thanks to everyone who has helped us get here. |
| 114 | + |
| 115 | +Cheers, |
| 116 | + |
| 117 | +Bryan, Ryan, and Zach |
0 commit comments