[WIP] July Newsletter #52
Conversation
|
Thanks for tagging, will hopefully get some time this week or in the weekend to read the updates! |
|
Something that might help: you can clone the wiki repo https://github.com/neovim/neovim.wiki.git and then use the logs/diffs to see what changed since last newsletter. I've been more careful about writing useful commit messages in the wiki since I noticed it was an actual repo. (I wish we could download the issues as a repo...) |
|
That's a great idea. I knew it was a Git repo, but I didn't think to use it like that. Yeah, if Issues were a repo as well, that'd be awesome. |
|
One of the things that I'm contemplating doing in this issue is actually tagging the developers that are working on things. While it makes it look a bit informal, I think it gives credit where credit is due and provides a "human touch" to it. If anyone opposes, we can do away with it. @equalsraf I've just added a section on your Windows compiling. If you could give it a read and let me know (link to the latest in the top comment) what you think. I can always add/remove things as you see fit. @aktau I've added a section on your string handling Wiki issue. Let me know how it looks. @justinmk I've added a section on the License; I tried to be as clear as possible. Feedback would be great. Everything is still coming along and in draft mode. Suggestions on things that I've missed are welcome; I'm still crawling through the Issues/Pull Requests and commit history since June 6th. Thanks everyone! |
|
Oh, and @philix, I think I've got everything from your Evernote that you sent me. Once again, it's invaluable. Nice work with it; let me know if I missed anything. |
|
@jdavis LGTM |
|
@jdavis great stuff. If you find enough content to pad out the article you can leave out the string handling though. It's not a feature, it's more plumbing work that'll probably not be interesting for the vast majority of the users. Something that might be a bit more user visible is the merging of libcall (based on libuv) which enables some more plugins. Relevant issues/PR:
It's always enabled (not behind a configure switch), so that's a tiny mental box users don't have to think about anymore. As for plugin-enablement, @tarruda's work is by far the most interesting, many cool plugins are based on python and I've seen quite some people claiming to be able to run their vim config unaltered not. Which is awesome. |
|
@aktau Cool, I planned on adding a libcall section here: https://github.com/jdavis/neovim.github.io/blob/july-newsletter/_posts/2014-07-04-july-newsletter.md#implement-viml-libcall-section-here I missed neovim/neovim#795 though so thanks for pointing that out. And I'll put Thiago's stuff at the top then once I finish writing it up. Thanks for the info, Nicolas! |
|
@jdavis I just added an entry about pt_br and German translations to my __ |
|
Thanks, @philix, updated. |
|
I've added the translation section as you pointed out, @philix. Also @stefan991, I added a section for the documentation. Give it a look and let me know what you think =] I have a handful of sections more to do but I should/hope to have it done later today. |
|
Is it too early to announce the colorscheme contest? |
|
Nope, I could totally add a section on for it in the General News. I think that'd be great! Edit: Instead of starting the submission process, we can just announce it, like you said. That way people will at least know it is coming. That'll give us some more time to prepare the submission process, create the bounties (if that's how we decide to do it), and iron things out. |
| In last month's issue, we talked about the [changes to `mch_stat` | ||
| calls][file-previous]. This refactoring was [continued][file-continued] by | ||
| @stefan991 to add a new structure that encapsulates `st_dev` and `st_ino` of | ||
| libc's [stat.h][file-stat-h] attributes of the `struct stat`. |
There was a problem hiding this comment.
It's not libc's struct stat but libuv's uv_stat_t (https://github.com/joyent/libuv/blob/b9b386ac5a8bf772af95e7238c3f0b6673626923/include/uv.h#L441). Not sure if this detail is relevant for the readers of the newsletter.
LGTM 👍 |
As pointed out by @stefan991, thanks for that!
|
Cool, just fixed that, @stefan991. Thanks man. |
Also sections and add some links. in the newsletter Also sections and add some links.
|
Phew, okay, I finally should be done. I finished up @tarruda's section and then moved things around a bit. Let me know if anyone sees any issues! |
|
I'm merging this for now, let me know if you see any issues with it and I'll update them as soon as possible. I'm doing some family things for the 4th so I'll have limited access. |
I'm going to be writing up the next newsletter this week and the next. Feel free to let me know if there's anything in particular that you want added/addressed. I'll be catching up on Issues as well as using @philix's Evernote as the basis for what gets added.
Tagging some of the core developers that aren't watching the main repo, sorry to be obnoxious: @aktau @jszakmeister @oni-link @schmee @Hinidu @elmart
Progress So Far
View the complete newsletter here.
Sources for info: