I actually need especially "cvs add -ko".
# I use it sometimes when I'm going to manage
# third party files with CVS.
Oliver Giesen said on cvsgui-dev list:
> What we really need is a full-fledged Add
> dialog which exposes the full functionality of the
> commandline client.
> There's many more options supported by recent
> CVSNT versions, among others the improved
> successor to the infamous "Check-out with Unix
> LF" (-kL) and an option to enable binary deltas
> in the repository (-kB). Furthermore all
> these options could be combined freely
> (e.g. -kLo or -kuzv, etc.). Just take
> a look at the output of cvs -H admin for the
> availabe -k options.
> I think this one should be implemented in the core
> to replace the current Add functionality.
I agreed it.
Logged In: YES
user_id=687086
Absolutly
Logged In: YES
user_id=158827
I'd like to extend this request to all commands that accept
the -k option. Add just happens to be one for which so far
no dialog exists at all.
I imagine this very similar to the current CVSROOT wizard:
There could be a simple text edit (with history dropdown of
course) with an elipsis button next to it which would invoke
another dialog that allows to set the individual keyword
options. There would be a radio group for t/b/B/u or
unspecified and checkboxes for k/v/l/o/L/z/c (of course not
using the letters but their corresponding descriptions
instead). Upon exiting the dialog, these would be translated
to the correpsonding k-option string (likewise the dialog
should be initialized from an existing string).
Logged In: YES
user_id=158827
"There would be a radio group for t/b/B/u or
unspecified..."
...as well as the recently added {encoding} (I guess this
would be another text edit).
"...and checkboxes for k/v/l/o/L/z/c"
...where o is mutually exclusive with any of the others.
Also, I think binary modes (b and B) would also be mutually
exclusive with at least k, v, l and L (o should be implicit
with binary so could be disabled as well), not sure about z
though.