RE: text-base penalty: A proposed solution

Yes, it is very similar to your svn_edit.

However, with some squeezing, it is possible to eliminate the svn_edit
command and also the ascii flat file:

Making the initial load of the workspace files read-only, provides a flag
that a particular file has not been edited (and has no text-base copy). I
think this replaces your flat file function.

If you are using Vim (or Emacs) for editing, a script (in .vimrc) could
automatically activate (autowritepre), sense the read-only, check that a
.svn directory exists with no corresponding text-base file, copy the
read-only file to the .svn/text-base, set the read-only file to read-write,
and then write out the changed file. (I have been reading the Vim manual -
might have a script written soon).

The Vim script essentially does the same thing as your svn_edit program,
but automagically without any extra user keystrokes.

Hey, I'm just trying to push your concept.

BobG

>> You execute a shell command then - an svn_init command (to be written)
>How does that scheme differ from my original proposal where you
>type svn edit before you start editing, or even after when you
>can't write the read-only file? Don't forget the notion of svn
>edit has other signifcant benefits too. Please refer to my original
>proposal (the start of this thread) for details.
>
>Kean

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 20 00:01:24 2002