ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Either my telnet of my vi editor is screwed up... When i go into vi editing vi has a tendency to screw up. It will do wierd things like print lines on top of other lines when i scroll across a line, it doesnt actualy make this change, it just looks like it is writing over the line, and its difficult to write code when you dotn know what line you are actualy writing to. Is there anyway to fix this, or a vi alternative I could use. I would love to dump vi if there is somthing better.
What you telnet'ing from?? Windows? In which case it ain't vi - its telnet problem. The windows telnet is really shite, you'll find problems with mose full screen apps (like editors). If you have pine installed then you can use Pico, the key mapping it uses seems to be alright. Vi seems to work here with the default telnet so long as I don't need to use the arrow keys! (not a problem as you can use h, j, k, and l movement when you're not in edit mode).
I use the telnet client that comes with Exceed and everything is fine. I'd suggest you change your telnet client.
Originally posted by Daniel I just cant help but show off my new sig.
looks as if you spend more time on your sig file than your posts!!!! just kidding, it is good but a bit long.
you know, they say shorter speeches make a bigger impact on the audience than long one's. take example lincoln, gettysburg address, about 5 minutes long. the guy before him. about 3 hours. which one do they remember in history.....
okay, its late and i need to leave work, i been here for 18 hours straight now.
I would guess that it is not a telnet problem nor a vi problem. It is a terminal emulation problem. Most likely your host does not know what type of terminal emulation that you are using or it does not know the correct size of your termal. What type of client are you using on the client side? Windows telnet, linux telnet, console? If you are coming from windoze with that sad telnet that was shipped with NT4 and 98 then try setting:
TERM=vt100
stty rows 24 cols 80
You need to count the number of lines you see in your window, rows and columns and stick the correct values in the stty command. With this properly setup vi should work correctly.
If you do not know what type of terminal emulation you are using you can either try vt100, ansi or linux. They are the most popular.
Most telent clients will tell you what term type they are emulating.
If all else fails you can always use the ex line editor, what fun.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.