-
Notifications
You must be signed in to change notification settings - Fork 107
[WIP] December Newsletter #117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
of plugins/tools that perform arbitrary manipulation in any language that | ||
supports msgpack. | ||
- Binary serialization format allows efficient/safe storage of arbitrary data. | ||
- Multiple Neovim instances will be able to share data in real time: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was never a goal of ShaDa. ShaDa provides only safe and extendable way of joining data from multiple NeoVim instances at their exit (or when explicitly calling :\*shada
functions), so that data will not be lost because one of the instances exited too early and without using :rviminfo
before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I will fix it
that last one is actually |
|
||
## Development News | ||
|
||
### SHADA(SHAred DAta) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I usually refer to this as ShaDa
.
👍 just a small typo 😄 |
I've updated with the suggested fixes. Adding @Shougo @junegunn @benekastah @kassio to review the information about their plugins |
interface. @Shougo is the sith lord of Vim plugins, here's a list containing | ||
some of his previous work: | ||
|
||
- [neocomplcache][neocomplcache] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think neocomplete should be listed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@tarruda LG. Thanks for the shout out! On Saturday, September 26, 2015, Thiago de Arruda notifications@github.com
|
The 0.1 release is basically just a tag that users looking to compile Neovim in | ||
a version that has a minimum level of stability, but future releases may also | ||
contain precompiled binaries and even installers(when Windows is officially | ||
supported) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could add some hints for packagers here.. maybe I'll send a PR once neovim/neovim#3318 is done.
Let me know if you need any assistance, @tarruda 😄 |
- Assumes no state stored between data pieces inside the file, which makes | ||
such tools simpler and allows such manipulations as “to concatenate two | ||
ShaDa files from different NeoVim instances simply use `cat 1.shada | ||
2.shada > joined.shada`, NeoVim will handle this properly when reading”; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now most points have dots. But not this and the previous one.
Updated to reflect latest changes and rebased |
### jemalloc | ||
|
||
[jemalloc][jemalloc], a high performance general purpose memory allocator, is | ||
now used by default. Since Neovim makes heavy use of dynamic queues (see above) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I'm reading neovim/neovim#3515 correctly, then this is no longer true.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason I thought that PR only added an option for turning jemalloc off without touching the default. I will fix it.
[windows-instrutions]: https://github.com/neovim/neovim/wiki/Installing-Neovim#windows | ||
[neovim-qt]: https://github.com/equalsraf/neovim-qt | ||
[homebrew-formula]: https://github.com/neovim/homebrew-neovim | ||
[archlinux-pkgbuild]: https://aur.archlinux.org/packages/neovim |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neovim has been added to the Arch Linux repos, so this link can be changed to https://www.archlinux.org/packages/?q=neovim
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, but isn't it useful to leave a pkgbuild script for compiling from git? Some users like to have the latest commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tarruda The Git pkgbuild is still in AUR for users to compile themselves, but the release is now in an "official" binary repo |
I have created the deoplete slide. http://www.slideshare.net/Shougo/deoplete-the-dark-powered-auto-completion-plugin-for-neovim |
👍 |
This will go out with the 0.1 release
ccing @ZyX-I to review the information about shada