use Perl

• cream (Score:2)

  by gizmo_mathboy (782)

  The cream project [sourceforge.net] looks interesting. Not perfect but does make it kind of easy to use vim (well, I do move it out of newbie mode into expert).
• Version control! (Score:1)

  by dlc (50)

  I've been keeping my entire home directory under version control for a few years now, and it works great. When I connect to a new machine for the first time, I simply do:

  cvs -d:blah:blah:blah co HOME

  And I get my full home directory, with all of my configs and so on, right away. There's a small quirk though, in that this checks HOME out into a directory called HOME, but I follow it up with:

  (cd ./HOME; tar cf - .) | tar xf - ; rm -fr ./HOME

  This copies the CVS directories too, so update and commi

  --
  (darren)
  • Re:Version control! (Score:2)

    by petdance (2468)

    I use Subversion. It has no problems being in the home directory. svn co svn+ssh://andy@svn.petdance.com/svn/home .

    --
    

    --
    xoa
• Rsync (Score:1)

  by iburrell (4155)

  I just rsync the important dot files and scripts from my main desktop to the others. This works the best when everything is running Linux with similar versions.
• use subversion! (Score:1)

  by dagolden (6584)

  # (grr, code HTML not formatting -- so I'll cheat)
  
  # I'm with Andy on this.  I use subversion to sync my vimrc between machines.
  
  # Moreover, I've customized my .vimrc for both Win32 and otherwise
  # so I can even sync between my Win32 laptop and my linux boxen
  
  # E.g.
  
  if has("win32")
      let $VIMRC=expand("$VIM\\vimfiles\\vimrc")
      let $DESK=expand("$HOME/../Desktop")
      set backupdir=c:\\temp\\\\
      set directory=c:\\temp\\\\
      if argc() == 0
     
• Yet another on saying... (Score:1)

  by Adrian (66)

  "but that's what source control is for" :-)
  
  Go on. Now you've done it again go check all those files in now!