Paul L Lussier <firstname.lastname@example.org> writes:
> (removed redundant Cc's since we're all on this list :)
> In a message dated: 02 May 2003 08:38:44 CDT
> email@example.com said:
> >The former. The addition of the -R would cause only two changes to
> >the way that propedit works today:
> > 1) the editor would always be loaded with an empty file (instead of
> > any current property value(s), if such exist).
> Why not load with any existing values? If the person invokes
> propedit, and wants to apply it recursively, they probably want the
> existing ones. And if they don't, they're in an editor, they can
> easily delete them.
You have two choices of interface here, then:
- Load *all* the collective values of that property in all the
recursive targets into the one editor buffer. Well, this is
silly (I trust you agree).
- Open and close the editor for each and every recursive target.
Hey, that's fine with me if you want to deal with that sucker
popping up in your face a hundred times.
> You are dead on in that I am not completely awake, nor
> sufficiently caffienated (sp?). However, I think this lack of
> stimulants in my brain is also preventing me from understanding why
> using a redirected I/O would be problematic?
> All I suggested was allow propedit to read from STDIN. How the shell
> deals with STDIN shouldn't matter to propedit, should it? It's just
> STDIN, right? (remember, I'm not a programmer, well, unless perl
> counts, so if I'm missing something incredibly basic, please learn me
> something new :)
I think you're missing something here. Remember, we have both 'svn
propedit' (which allows a person to edit properties in an editor
program) and 'svn propset' (which allows a person to set new property
values taken from the command-line or from a file).
Let's look at your examples:
> svn propedit -R PROPNAME . # take property info from STDIN
> # (i.e. the keyboard)
For this, do 'svn propset -R PROPNAME PROPVALUE'.
> svn propedit -R PROPNAME . < props.txt # take property info from
> # STDIN, which is redirected
> # from the file props.txt
For this, do 'svn propset -R PROPNAME -F props.txt'.
> svn propedit -R PROPNAME -e EDITOR . # invoke the editor, get the
> # prop info, and apply it when
> # finished
And this is the where we don't currently have a matching
functionality. svn propedit already uses an editor (you don't have to
tell it to -- that's why it's called propEDIT). But as part of its
operation, it opens the editor on a tmpfile that contains the current
value of the property you are setting (if a current value exists).
You edit that current value in the editor, save the tmpfile, and close
the editor. Then propedit applies your edited property to the target,
overwriting the previous property value.
The problem is what to do with -R on a propedit, as you can see from
other messages on this list today.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri May 2 16:37:47 2003