Originally Posted by gerbear1
Thanks for the replies everybody. I didn't explain myself very well, I wrote the post kinda in a rush. This is close to what I'm looking for.
I connect to the linux servers from Windows using putty. I can use vi to edit whatever files I want, but I'm not a fan of using it, I much prefer to use winscp and then edit the files in EditPlus. That's what I currently do for files that my username owns. The problem is that some of the files can only be edited by a superuser. I have sudo rights to get to that superuser. So I log into the linux box with putty sudo over to the user with my privileges (sudo su - superusr) and then I can edit whatever I want using vi. I can't do this with WinSCP. I can connect to the box with WinSCP as my username, but I can't run any sudo commands or anything to get to the files owned by superusr.
Does this make sense what I'm saying? I'd like to be able to edit files using EditPlus, as I currently do for some that I own on the server, but I can't do it for the ones owned by a super user, even though my login does allow me to sudo over to that superuser. Changing permissions or how this is setup is not an option, this is how the company have configured their security. I don't think there's any way I can do what I want to do, but I hope I'm wrong.
If you ssh in via putty, you are giving yourself an awful lot of work downloading the file to windows, and then editing it, and then pushing it back to the server. Vi/Vim is hard at first, but there are tutorials that will give you the basics. I'm using Vi for over 10 years and I really only use the basics, (insert, replace, find, top of page, end of page, newline, and a little reg ex). Learn those and you should have enough to work. Alternatively try nano, its a very straight forward editor.
I know this isnt the advice you want, but Linux isnt going away, and twenty minutes familiarising your self with either Vi/vim or Nano, will save you hours in the long run.
Plus, copying files from a server to a windows client and then putting them back may violate privacy/security policies in future contracts, if it does not already. Just something to be wary of.