Am 10.05.2011 02:24, schrieb Jeff Slutter:
> On 5/9/2011 8:15 PM, Matt Welland wrote:
>> Rather than changing the terminal user interface (it will be slightly
>> less nice IMHO due to the extra newline on a prompt) I suggest
>> considering the approach used on the monotone project. A separate
>> interface for automation. Make the human friendly interface friendly
>> to humans and make the automation interface friendly to automation.
> I agree, you don't want to mess up the text for the normal command line
> user. I suggest doing something similar to Perforce with it's tagged
> text output ("-z tag") ripe for parsing, or, just testing to see if
> adding fflush(stdout); fflush(stderr); instead of adding tacking on a
> newline. This will hopefully cause the parent process to receive the
> child output.
Unfortunately fflush(stdout) doesn't help. It is part of the prompt_user
function since day one.
For now, I think I'll do it with my small change. It works and has near to no
impact on the fossil code base. The prompt_user function doesn't look like it
will be changed in the future. An additional flag for parsing friendly output
would require changes in a number of commands and IMHO is not an option until
there are more projects which require this.Ingo _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
