hoschi

Cool. You can "watch" the Github repo with the button in the right upper place beside "star" and "fork".

With the buffer events and especially `nvim_buf_call` of NeoVim it is possible to do everything without hacks.

Naaah ;) Some people missed the installation instructions https://github.com/hoschi/yode-nvim/issues/5

this already works, just use `YodeCreateSeditorReplace`. The command creates a seditor and opens it in the current window. You can then use the created seditor like any other buffer. To open a selected code part in normal splits do:

:YodeCreateSeditorReplace :vsp <Leader>blt

Yode-Nvim can create more regions of the same file as well as a floating "window manager" for regions called "layout". Yode-Nvim syncs changes from regions to files in real time where you need to "write" the changes by hand with NrrwRgn.

fixed it

Splits are not based on content, but are controlled by a layout algorithm. For horizontal splits, for example, the size changes every time you create a new one. Yode-Nvim is based on the size of the seditors and enlarges/reduces them automatically. There are more layouting algorithms planned and they can be different for each tab, the code is already set up for that.

Yode (the POC 4 years before) itself only worked with a (JavaScript) AST to create seditors. Tree-sitter would have helped here to provide an AST for different programming languages uniformly directly in NeoVim. Yode-Nvim is more powerful than the first version because it operates on lines to create seditors. In this respect Tree-sitter doesn't matter for Yode-Nvim. If someone uses Tree-sitter to select code in visual mode, he can easily create seditors for code objects like functions. This is also possible without Tree-sitter, but you have to select the function yourself.

Demo page is just white background :(

there is a lot of that stuff in the readme on Github (icon top right corner). Ask me if something isn't clear :)

Atom doesn't use React any longer for their editor component

React is a great tool for many cases, for our particular needs in this particular case I decided it would be easier to just do things for ourselves.

https://github.com/atom/atom/pull/5624

I tested Sencha, jQuery Mobile and Dojo 1.7 and 1.8 a week ago with my Nexus phone -> Dojo 1.8 wins clearly when it comes to performace of touch events and transitions :)

Yeah, now I can throw away tig for staging files :D

How do you think code checking tools (FindBugs), buildsystems (Maven), version control systems (Git), ... has an impact to your productivity/flow? I think, this tools helps me a lot, because I just must write code, commit, write code, commit, ... and all other stuff runs automagically in background.

In my opinion APIs are also very critical for flow, beside the programming language. If I see easily what I must use/touch to get things to work, I'll be productive. In contrast to big/strange named APIs where I need to read a lot of documentation to get the idea behind.

There is a link error: "flow" should link to http://en.wikipedia.org/wiki/Flow_(psychology). You forgott the trailing ). Beside that, the title of your articles is just "Hi".

I built a Zypr clone for software development -> http://news.ycombinator.com/item?id=3214934

Has someone more cool scripts which raise productivity?

Give us an API which has also the points for a headline included (the RSS feed does not :( ), so I can build a more customizable feed.