Seeing more with VIM

[Yarin]

I've never had to press left first, maybe that's a ksh thing.

Haha, no it's not. I just checked and your right, it isn't necessary. I have no idea why I thought you had to do that. Maybe it has something to with the fact that I discovered it accidentally, and that the line has to be empty.

[nkbxwb]

I have ubuntu and I use that sometimes, but the vim I use is through my university. We operate on windows 7, and use PuTTY to log on, and then use vim from there.

[MK27]

I have ubuntu and I use that sometimes, but the vim I use is through my university. We operate on windows 7, and use PuTTY to log on, and then use vim from there.

That's a nice thing about vim -- the GUI and terminal version are almost identical, so when you have to work in a terminal environment, it's painless. Except for little issues such as this, because the terminal version must operate inside a terminal, and that is what is limiting your output lines -- either the local putty (not likely) or the local windows console, or the remote server.

You could go to your school's computer services desk (usually located somewhere deep underground in a maze of tunnels with lots of steel doors, lol, behind the boilers and near the glassed in banks of server racks) and ask someone about this. Someone may have thought about and experimented with scrollback limitations on the network, but OTOH, it may just be a default setting somewhere. So if you point out that it is irritating to the right person, they may even change it. Particularly if you bring it up in class and your prof sympathizes and s/he asks computer services instead.

What I mean by this is: Is there any program that is an IDE that can help me step into and debug my program. I know you can do it in visual studio, but it is a pain in the ass.

You don't have to use an IDE to debug. I find them horrifying. Your school's network probably also runs gdb, just try "gdb" from the shell command line (or <esc> :!gdb inside vim*). There are a couple of gdb tutorials linked in my signature below. It is not that hard to use.

* personally, I'd rather log in twice via putty, using two separate terminals, so I can run vim and write code in one, then just use the shell and compile/test/debug in the other from the same directory.

[rags_to_riches]

Perhaps you need to change PuTTY's scrollback setting?

[Yarin]

I would like to mention, that I don't think the scroll back settings of a consol/SSH session/PuTTY, whatever, is (or at least, should be) the problem. In VIM, I use PageUp, PageDown, Up, & Down, to navigate the lines. When doing this through SSH or locally, I've noticed that in-VIM scrolling is independent of the scroll-back. To be more clear: When you "scroll" up in VIM, the remote server will re-send the data back straight from VIM, and will _not_ scroll back in the consol on the remote _or_ local side. If your using a GUI terminal, you can see it for your self, by scrolling up in it, and you'll see the history of what you've been doing in VIM, esp. if you go up and down and back again, it'll be a mess of stuff. I know there are different consol "modes", that effect this, so YMMV.