Overview
Artifact ID: | 2db3dbef6b5f86f8275f7a144b6eb2f2d86662a7 |
---|---|
Ticket: | 2857ab0995828207effd6ebc4526ca88a53755f7
Introduce commandline switches to avoid user input |
User & Date: | anonymous 2010-12-31 00:39:13 |
Changes
- comment changed to:
I'm trying to build a C# wrapper around fossil to provide a .NET dll to be used in Windows source control applications like the source control interface of Visual Studio. While implementing the commands which are available on the fossil command line I've encountered some commands which might require user input. For example fossil open requires an a, y or n if files of the checkout are already present. Handling those commands from my code is kind of cumbersome because I have to run the commands asynchronously, parse their output and inject the correct answers at the right places with event handlers for all the commands which need user interaction. It would be much easier if I could define anything on the commandline. Although it is obviously not possible to have commandline switches for the y or n on individual files, it should be possible to give the a(ll) answer by something like --force on the commandline. It is already done for a number of commands. Generally spoken, it should be possible to set a default answer for all files involved on the commandline whenever user interaction is required. If this feature request is a candidate for future implementation, I'd compile a list of commands which require user interaction and provide suggestions for a commandline switch. Btw.: Did you ever think about making fossil available as a library like you did with SQLite?
- foundin changed to: "all"
- private_contact changed to: "e16bca9376b716bf489a593de88e7b2760905520"
- severity changed to: "Important"
- status changed to: "Open"
- title changed to: "Introduce commandline switches to avoid user input"
- type changed to: "Feature_Request"