> $ mtn di > mtn: misuse: 'di' is ambiguous; possible completions are: > mtn: misuse: informative diff > mtn: misuse: review disapprove > $ I like this behaviour. This seems natural to me, since it's impression is like emacs or shell tabcompletions. I also like git's aproach providing commands like git-diff making tab complitition work. One could implement those easily as shell aliases too. So why hardcode 'mtn di'?
Don't know the code of monotone, but it seems like the current solution
makes sense from a programmers point of view. For me as a simple user it
would unsettle me having some shortcuts hardcoded, some not. The current
solution is simple. Not much to learn about that.
One more difference: the current behaviour triggers an error when using
'mtn di'. And (i.e. in shell-scripts) it could be destructive (or, in
this case, annoying) to execute 'mtn diff' and proceed, where 'mtn
disapprove' was meant (ok, who uses shortcuts in scripts?).
Regards
Sebastian
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
