Question about editors

[pablogosse]

Hi all. I normally use Homesite as my editor, mainly because it allows me to edit files directly on the server.

However, my sysadmin has recently shut off ftp on the webserver, and is forcing everyone to ftp via ssh.

This has killed my ftp abilities within homesite, so I'm wondering if anyone knows of an editor that allows one to connect to a server via ssh? I know homesite allows one to connect via ssl, but it ain't ssh so I'm sshit (ha ha ha, couldn't resist ;o) outta luck there.

Anyone have any ideas?

Thanks in advance,
Pablo

[Sxooter]

Well, a lot of unix servers will let you run X apps and redirect them out to another box (we do that at work) are you running a flavor of Unix as well as windows?

If not, then see if your unix box has pico on it, it's not near as stinky to use as vi or emacs can be.

[mrmufin]

Originally posted by Sxooter
If not, then see if your unix box has pico on it, it's not near as stinky to use as vi or emacs can be.

IMHO (and remember, folks: O's are like A's, we've all got one) vi is a fine editor. For anybody who's doing lots of internet programming, knowing at least the basics of vi should be *mandatory*. If for no other reason, it's because you can count on it being there on whatever flavor of UNIX you're doing your thang on...

[marianna]

I'd like to put in another vote for vi
actually, I recomend vim because it has a few extra features

putty is a nice free telnet client
it has no special bells or whisles though

[Sxooter]

I know how to drive vi, and I have to say that while it's ubiquitious nature makes it something we should all be at least familiar enough with to use, it's like driving a car with 8 pedals, 3 steering wheels, and 4 shifter knobs for joe beginner.

Vi is a good editor, and my dad's studebaker was a great truck, but nowadays I'm glad I don't have to know how to hold the clutch half way in / out to get it to go into reverse anymore, and I'm glad I don't have to drive vi much anymore. After all, vi was designed to conserve paper and keystrokes on a 110 baud teletype connection, and while those decisions were perfectly logical for the days of solenoid driven displays, things like vim are a welcome relief from the plain old vi one finds on Solaris.
I grew up on Emacs on an Amiga, and have to say it is a much more powerful editor, and if one is going to invest hours learning an editor, it's better spent on emacs than vi, in terms of return on investment.

[largo]

Originally posted by Sxooter
I know how to drive vi, and I have to say that while it's ubiquitious nature makes it something we should all be at least familiar enough with to use, it's like driving a car with 8 pedals, 3 steering wheels, and 4 shifter knobs for joe beginner.

Vi is a good editor, and my dad's studebaker was a great truck, but nowadays I'm glad I don't have to know how to hold the clutch half way in / out to get it to go into reverse anymore, and I'm glad I don't have to drive vi much anymore. After all, vi was designed to conserve paper and keystrokes on a 110 baud teletype connection, and while those decisions were perfectly logical for the days of solenoid driven displays, things like vim are a welcome relief from the plain old vi one finds on Solaris.
I grew up on Emacs on an Amiga, and have to say it is a much more powerful editor, and if one is going to invest hours learning an editor, it's better spent on emacs than vi, in terms of return on investment.

It's hard to argue with an example like that, well written. Of course you're talking about vi, vim get's my vote, and I am sure your approval.

[Frag]

You all are just making things to easy.

Use the commands cat, awk, sed, and grep as your editor

Now your talking about some fun fixing syntax errors

Frag