I'm using neovim all the time, but I don't find this "zipping through the code" to be very critical. Most of the time is spent on thinking and analyzing it, not on fast typing or jumping through it.
Maybe but I often find the bottle neck between thoughts in my head is often the speed of which I can put them in motion, with that in mind vim motions are an absolutely amazing way to interact with a keyboard efficiently.
When using any new software my first thought is often how can I map these actions to vim motions and enable a full keyboard experience.
Depends on what you are doing. When it’s a large codebase, trying to debug or understand a implementation, hitting * to cycle through the occurrences in a file, “gd” to jump to the function definition, Ctrl+o to go to previous position are crucial.
Congrats on ntsync and new wow64 support! Those are two huge features released last year.
ntsync allows efficient and correct synchronization usage that matches logic of Windows and new wow64 allows running 32-bit Windows programs without 32-bit Linux dependencies.
This would be fantastic. I'm trying to write an audio driver for my HT|Omega eClaro PCIe soundcard for Linux by leveraging kernel modules for cards with a similar BOM. It is mostly working, but the main hurdle is the inability to increase the volume to >= 50% of the volume in Windows. I'm setting attenuation correctly to the correct DAC registers and I can hear the opamp relay click on, but can't adjust the final gain. It sure would be great to have the Windows driver source. Worse yet, the company is unresponsive to my requests for any info (schematics, gain setting sequence, anything).
> It's projection. Their evangelism is born of insecurity.
It's fear, but of different kind. Those who are most aggressive and pushy about it are those who invested too much [someone else's] money in it and are scared angry investors will come for their hides when reality won't match their expectations.
reply