If you just want to get a clojure REPL within vim using the excellent VimClojure, just change vim to clojure mode like so
:set ft=clojure
and start the REPL using typing \sr
Make sure, nailgun server is running in the background
Instructions to install VimClojure
Tuesday, April 20, 2010
Sunday, February 28, 2010
Friday, February 19, 2010
macosx tar - annoying ._* files
I noticed that tar generates files starting with ._* when creating an archive
And the corresponding listing in archive
Notice how it adds "._.htaccess"
I found the solution here
Here's the command for convenience
$COPYFILE_DISABLE=true tar cvzf jfa.tgz jfa
COPYFILE_DISABLE=true (for Leopard)
COPY_EXTENDED_ATTRIBUTES_DISABLE=true (for Tiger)
$ tar cvzf jfa.tgz jfa
And the corresponding listing in archive
ashee-mac:shiva amitava$ tar tvf jfa.tgz
drwxr-xr-x amitava/staff 0 2010-02-19 09:18:22 jfa/
-rw-r--r-- amitava/staff 187 2010-02-19 08:40:06 jfa/._.htaccess
-rw-r--r-- amitava/staff 616 2010-02-19 08:40:06 jfa/.htaccess
....
....
Notice how it adds "._.htaccess"
I found the solution here
Here's the command for convenience
$COPYFILE_DISABLE=true tar cvzf jfa.tgz jfa
COPYFILE_DISABLE=true (for Leopard)
COPY_EXTENDED_ATTRIBUTES_DISABLE=true (for Tiger)
Monday, February 15, 2010
Friday, February 5, 2010
F# in macosx
I downloaded FSharp-1.9.7.8 and attempted to run it in MacOSX using mono (2.4.2.3).
This kept exiting the prompt after brief attempts to spawn a GUI. I found the solution here
Invoke fsi.exe without gui and with readline as indicated in the link above
mono $FS_HOME/bin/fsi.exe
This kept exiting the prompt after brief attempts to spawn a GUI. I found the solution here
Invoke fsi.exe without gui and with readline as indicated in the link above
mono fsi.exe --readline+ --gui-
log4j - "appender is not assignable to Appender"
If you are getting "appender is not assignable to Appender" error in an attempt to configure log4j, just pass a system property as below
$) java -Dlog4j.ignoreTCL ...whatever...
See here
$) java -Dlog4j.ignoreTCL ...whatever...
See here
Wednesday, January 20, 2010
Hadoop 0.20.1 - Null pointer exception on startup
I am trying out Hadoop on my Mac0SX (10.5.8). I unzipped the distribution and after cd'ing to ~/hadoop-0.20.1/bin, ran
I get the following exception
Turns out, the default does not come configured with, well "defaults". The fix is easy enough as highlighted in Quick Start (duh)
conf/core-site.xml:
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:9000</value>
</property>
</configuration>
conf/hdfs-site.xml:
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
</configuration>
conf/mapred-site.xml:
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:9001</value>
</property>
</configuration>
ashee-mac:bin amitava$ ./start-all.sh
I get the following exception
2010-01-20 13:14:13,341 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = ashee-mac/10.17.8.21
STARTUP_MSG: args = []
STARTUP_MSG: version = 0.20.1
STARTUP_MSG: build = http://svn.apache.org/repos/asf/hadoop/common/tags/release-0.20.1-rc1 -r 810220; compiled by 'oom' on Tue Sep 1 20:55:56 UTC 2009
************************************************************/
2010-01-20 13:14:13,480 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: java.lang.NullPointerException
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:134)
at org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:156)
at org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:160)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:175)
at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:279)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:956)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:965)
2010-01-20 13:14:13,482 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: SHUTDOWN_MSG:
/************************************************************
Turns out, the default does not come configured with, well "defaults". The fix is easy enough as highlighted in Quick Start (duh)
conf/core-site.xml:
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:9000</value>
</property>
</configuration>
conf/hdfs-site.xml:
<configuration>
<property>
<name>dfs.replication</name>
<value>1</value>
</property>
</configuration>
conf/mapred-site.xml:
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:9001</value>
</property>
</configuration>
Subscribe to:
Posts (Atom)