

Re: status output and long fields

From: Tim Moloney <moloney_at_mrsl.com>
Date: 2003-02-19 20:42:09 CET

Perhaps the suggestion that I made a while ago is pertinent.

Let there be a default format for the output but allow it to be overridden
by using a format option. For example,

--format="%5{status} %4{work-rev} %4{last-chg} %8{author} %{file}\n"

would display 5 columns for status, a space, 4 columns for the working
revision, a space, 4 columns for the last changed revision, a space, 8
columns for the author, a space, the entire file name.

This is perfect for scripts because you can specify:
- what information you want to get
- the order in which the information is returned
- the number of columns assigned to each piece of information
In other words, a script gets exactly what it wants and knows exactly
what it's going to look like.

You have to have a reasonable default for interactive use and I agree
with CMike that autosizing columns with minimum widths and a header is
the way to go. However, it seems to me that if you are going to do
autosizing columns, you need to provide a format option for scripts
otherwise it becomes too awkard to retrieve the data.

Tim Moloney
ManTech Real-time Systems Laboratory
2015 Cattlemen Road                             \     /
Sarasota, FL  34232                     .________\(O)/________.
(941) 377-6775 x208                        '  '  O(.)O  '  '
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
Received on Wed Feb 19 20:42:57 2003
