> Ingo, > > This seems like a reasonable change to Fossil as long as adding it doesn't > break anything we don't understand (I can't believe it would). No, it won't break anything. The only difference is that on the commandline the users answer has to be entered on a new line and not on the same line as the prompt.
> Propose it as a change and get Richard Hipp's feedback. Maybe you should try > to become a Fossil contributor and make the change yourself so there doesn't > have to be a custom Fossil build. I've already added a ticket as a feature request a while ago. I won't conjecture about the reasons not to include this change. After all it is Richard's project. I'll try to always include a modified Windows binary release of the latest official Fossil release version into my project. Anyone who doesn't trust this exe might compile it himself. ;-) As I mentioned, SharpFossil and WinFossil are far away from beeing complete or bug free. And as long as there is one user (me ;-) ) it doesn't make sense to beg Richard again and again to change anything in Fossil to support SharpFossil. The main purpose of my original post to the list was to encourage Windows users of Fossil to try SharpFossil/WinFossil and to get feedback about it and may be to get people involved in further development (for me, it is a spare time project and unfortunately not evolving fast enough) . Ingo
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
