You don't want to do that... do you? git svn git svn

git rm --cached -n -r `find ./ -type d -name .svn`

Problems with your local perl install?

Try the following uber 1337 commands (based on this):

mv ~/perl5 ~/notperl5
wget -O - http://cpanmin.us | perl - -L ~/perl5 --self-upgrade local::lib


ZOMG!



OK, now add your ~/perl5 dir into git...
cd ~/perl5/ ; git init ; git add . ; git commit -m 'initial import'

This will help you keep things in order over time.


Example:
cpanm Bio::DB::Sam


You can then use git to see exactly what you did, and commit if it worked OK. i.e.
git add . ; git commit -m 'BioPerl and Bio::DB::Sam installed'

(Once you have confirmed that it's working.)


Once your local::lib is in git, you can do lots of stuff like if something is breaking, just edit it in there to insert debugging or whatever and then just reset --hard to get rid of it after you figure out what is going on, etc.



Thanks to rbuels on irc://irc.freenode.net/#bioperl for helping with this!
(All the above is his doing).

Testing MediaWiki (MW) & Semantic MediaWiki (SMW)

Long time coming...


http://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker#Testing



First, set up the MW testing environment:

Grab the latest MW (1.15 branch):

Somewhere in the web-directory:
svn co http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_15/phase3/ MW1_15

Configured using all the default settings.


Next, grab some extensions:
http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_15/extensions/


Write some tests using http://seleniumhq.org/

1) Install the Selenium-IDE (Firefox plugin)

Configure the ssh *client* to stay alive

http://embraceubuntu.com/2006/02/03/keeping-ssh-sessions-alive/

Resurrect screen?

You were just using screen, but now it says

dmb@dallas0 [~]# screen -r
There is no screen to be resumed.

Try this:
ps x | grep -i screen

Note the PID... and:
kill -CHLD screenpid



http://www4.informatik.uni-erlangen.de/~jnweiger/screen-faq.html

"What links here" for symlinks?

Ever been frustrated by knowing that you have created a link to your `pwd` 'somewhere' on the file system, but you are unable to remember where?

Ever wished you could just hit "What links here" to discover the location of the symlink from the target?

Tough.

There is no good solution.


Here are some ugly hacks:

#!/bin/bash
for file in `find / -type l 2> /dev/null`; do
ls $file -l 2> /dev/null | grep "target" 2> /dev/null
done


or

find ./ -type l -exec ls -l '{}' \; | awk '{print $11}' | grep "target"


These 'hacks' will thrash your disk, but what are you going to do? Unless we can make a file system based on a wiki ... (imagine a history page for all your config files?) or a database ... (imagine querying for all the files greater than 1 Gb older than 1 year?) we are stuck with these... Unless you know better?

Perl wrapper for R

This Perl wrapper for R fills in some missing functionality (line number and context on error) and automatically 'dumps' the output of the script.

I can be improved in many ways, but here it is, as is....

   1. #! /usr/bin/perl -w
   2.
   3. unless (@ARGV){
   4.   warn "\n";
   5.   warn "Runs an R script with STDERR dumped to STDOUT\n\n";
   6.   warn "Usage: $0 \n\n";
   7.   exit(1);
   8. }
   9.  
  10. my $rFile = shift @ARGV;
  11.  
  12. die "Stubbornly refusing to run R on a file that doesn't end .R!\n"
  13.   unless $rFile =~ /\.R$/;
  14.  
  15. my $oFile = `basename $rFile .R`; chomp( $oFile );
  16.  
  17. my $args = join(" ", @ARGV);
  18.  
  19. if ($args){
  20.   $args = "--args $args";
  21. }
  22.  
  23. warn "Using: R $args < $rFile > $oFile.dump\n";
  24.  
  25.  
  26.  
  27. open ( OH, ">$oFile.dump" )
  28.   or die "cant : $! \n";
  29.  
  30. my $pid =
  31.   open( PH, "R $rFile -q --vanilla $args < $rFile 2>&1 |" )
  32.     or die "cant : $? : $! \n";
  33.  
  34. my $lineNumber;
  35.  
  36. while(){
  37.   $lineNumber++ if /^(\>|\+)/o;
  38.   print OH;
  39. }
  40.  
  41. close( OH );
  42. close( PH );
  43.  
  44. if ($?) {
  45.   #warn "killed by $?\n";
  46.   warn "FAILED AT LINE $lineNumber\n";
  47.   system("tail -n 5 $oFile.dump");
  48.   exit(1);
  49. }
  50.  
  51. warn "OK (NO ERRORS DETECTED)\n";