Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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).
  • 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)
  • 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.
  • # (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
       
  • "but that's what source control is for" :-)

    Go on. Now you've done it again go check all those files in now!