[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Autoexpanding ZIP archives?

From: André Pönitz <andre_at_wasy.de>
Date: 2005-12-08 17:15:24 CET

John Peacock wrote:
> If all of your Open Source activities involve the use of variously
> compressed files, I am not aware of *any* version control system which
> will efficiently store these files, for all of the technical reasons
> that have appeared in this thread.

IIRC there are version control systems out there that do support
client side scripting. I understand that writing useable scripts
there is difficult, though.

> If you, on the other hand, are
> storing *source code* in your repository, Subversion is
> IMNSHO, the best tool out there for *that* purpose.

Believe it or not, I _do_ handle .png icons the same way as source
code i.e. I edit them with the same editor as I use on .c and .h files
(put autocmd BufRead *.png :silent %!/usr/bin/convert - xpm:-
autocmd BufWrite *.png :silent %!/usr/bin/convert - png:-
in your .vimrc to see what I mean)

The situation here for vim is pretty much the same as it would be
for svn:

.png is not a 'native format' of vim (that would be plain text),
but it is convertible to and from text, so this non-native format
'feels' pretty 'native' from a user's point of view.

And this extensibility is what makes vim a much more powerful
editor than e.g. good old vi.

svn is pretty close to vi in this regard: Do the basics, do them
good, do not more.

In my opinoin, an 'svnimproved' would be a much better utility
for most users, even if it gives them even more rope to hang


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 8 17:33:08 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.