agreed. since i don't trust the network i'm on though, i prefer to use TRAMP instead of ange-ftp. you can run ange-ftp over ssh but i find that more complicated and error prone than TRAMP.
so my setup is: code lives on a dev box (linux + apache), emacs/TRAMP to edit, usually an ssh session to the dev box too. everything's managed with cvs. i keep a dev and staging directory on the dev box. once i'm happy with the code in dev, i cvs commit, then update in the staging dir and make sure it still works there. if that's all good, i do a cvs update on the production box (solaris + apache). Makefiles are useful for handling any differences between configuration on dev vs production.
anders pearson
| [reply] |
vi sucks.
That's why I use vim.
:-)
____________
Makeshifts last the longest. | [reply] |
Remember you can't spell evil without vi.
I've always wanted to write an editor called
evil; I've even backronymed it to "Editor,
VI-Like". My plan is to make it super-easy
to run the text through on-the-fly Perl code... of course,
vim already does that. At
any rate, I've never quite had the free time for it,
especially since vim has most, if not all, of the features
I want.
vim also does remote editing, of course. Still doesn't
have a sexy BastardizedLISP interpreter, though... I'll
have to concede that one to you
Emacs guys,
I guess.
--
The hell with paco, vote for Erudil!
:wq
| [reply] |
