Jason Valencia <[email protected]> writes: > Timo Myyrä wrote: >> Seems the changing the chicken binary is pretty trivial so let's go >> with it. New binary names also line up nicely with other binaries. > > Since csi has been a CHICKEN command since 2000, and a command with the > same name was (as far as I can tell) only added to Mono this year, > wouldn't it make more sense to rename the binary in Mono, which > introduced the conflict? I'd rather break under a year of backwards > compatibility than 18 years.
Probably, but I guess the changing the binary name in chicken was easier task. And updating the chicken workflow to use new binary name, for me at least, is just chaning my emacs configs to use the new name and things work as usual. Though I think the binary name change should be mentioned in the 'following current' page. Timo
