OSDev.org

Lately I have been using none. MSVC for source code editing but that's all; building is done using a make system (no scripts). My reasoning stems from that utilizing a make system is the most portable method (if designed well) and imho encourages self hosting.

Kevin wrote:I was talking about visual mode where you select a block that you want to have reindented (it can be started with v or Shift-v). In normal mode you need to specify the range on which = should work, for example G for "until the end of the file". Do this on the first line and the whole file is reindented, so everything combined gives you a gg=G in normal mode.

Ahh, it works. I tried it on one of the more complex examples, and then did a compare with SVN, and it contains no other differences than white-space differences.

Thanks!

Another vim junkie here!

The one tool I couldn't live without is GNU screen. It is so much more efficient than working with multiple terminals, or multiple tabs in a terminal window. It also has the huge advantage of being able to detach and re-attach from sessions.

I have ssh set up to automatically connect to an existing screen session, or create a new one. This makes it very easy to continue working exactly where I left off, but tunnelled in from a different location. It also means that connection dropping is no longer an issue.

Unfortunately it breaks Ctrl-PgUp/Dn in vim for switching tabs, which is really annoying. But when working remotely over ssh, I often use screen anyway.

I don't make use of tabs within vim. I tend to either:

• Use different pages in screen
• Just switch between vim buffers (\be using bufexplorer)

depending on what sort of work is involved.