[Monotone-devel] Issues with mtn commit and the latest net.venge.monotone head

[Tero Koskinen]

Hi,

"mtn commit" seems to be broken in revision
d24b59732a5b3293592457cba013c8f8b716a875.

I found out two problems

Problem 1)

When doing "mtn commit" I get:
$ mtn ci
mtn.real: beginning commit on branch 'fi.iki.tkoskine.ahven'
mtn.real: warning: [string "<std hooks>"]:314: bad argument #1 to 'find' 
(string expected, got nil)
mtn.real: misuse: edit of log message failed
$

Setting EDITOR to "vi" (or something else helps):
$ echo $EDITOR

$ export EDITOR=vi
$ mtn commit                             
mtn.real: beginning commit on branch 'fi.iki.tkoskine.ahven'
mtn.real: committed revision 40a7d624e7f9f798ce2d6edac39b39712ce9fbdd
$

The problem was gone when I updated to revision
04766db8e363880fd1d50692d793661d9f4fdcf4. (A newer revision might also
work, I didn't iterate through every rev.)

Problem 2)

When doing "mtn commit -m 'long message'" I get unknown path errors:
$ mtn commit -m 'Increase version to 1.7'
mtn.real: warning: restriction includes unknown path '1.7'
mtn.real: warning: restriction includes unknown path 'to'
mtn.real: warning: restriction includes unknown path 'version'
mtn.real: misuse: 3 unknown paths
$

In other words, the text after the first word is interpreted as paths.
Update to rev 04766db8e363880fd1d50692d793661d9f4fdcf4 didn't solve
this, but in release 0.42 '-m' option works as expected.

-- 
Tero Koskinen <address@hidden>