On 9/23/06, Dukhat <email@example.com> wrote:
> Kenneth Porter wrote:
> > On Friday, September 22, 2006 9:14 AM +0200 Dukhat
> <firstname.lastname@example.org> wrote:
> >> My suggestion is: Invent a few official subversion properties to control
> >> the settings. Like svn:tab=8 svn:indent=4 svn:tabfill=space or
> >> svn:tab=8,4,S .
> > I question putting them in the "svn:" namespace, since Subversion
> isn't directly involved in the editing of text files.
> No, agreed, Subversion doesn't do that. However at least the tab-size is
> a part of the file's rendering, i.e. a part of the file's properties
> which should be stored and versioned.
> > Some editors recognize this kind of control in the form of special
> source code comments. Moving this information to Subversion properties
> would mean that editors would need to link the Subversion libraries to
> access them.
> No, they would use the plug-ins: Ankh for VS, something for emacs etc.
> Those two would cover a large part of the users.
emacs and vi already have support to detect in-file tab size comments.
That's exactly what Kenneth was referring to. Why can't Ankh extract
exactly this information from the file content?
> > Instead, I would suggest putting source style information in a
> separate file so that users of any version control system could access it.
> Very nice... in theory. However, in real life that would imply yet
> another hopelessly ignored library.
Then why does this work great for both vi and emacs?!
> In real life, "cat" on linux and "type" on windows will never use any
> solution to detect tab-size, whether it be a separate file or version
> control system.
Right. Neither will 'svn cat' or 'svn diff'... They will just print
the tab character to the console.
> No, this property is for coders using the Subversion flavoured tools.
> There is a real chance that if Subversion describes this property, the
> tools and utilities can pick it up quite fast. For example, svn diff
> could lead the way. If TortoiseSVN and Ankh adopt, the Windows world is
> largely covered.
'svn diff' doesn't interpret the file content. I agree that if Ankh
and TSVN adopt that the windows world would be largely covered, but
how would we make Subversion on linux behave like Subversion on
No, the Subversion team made an explicit choice not to interpret file
content, because it leads to more problems than solutions... I think
it's a good idea to keep it that way. BTW: why couldn't Ankh and TSVN
agree on a 'separate file' solution? Or why can't they agree on the
> But, the separate file solution could gain ground IFF the Subversion
> team would implement such a stand-alone library for all platforms. And
> use it themselves, of course. Adopting a third party solution might also
> work, if done officially by the Subversion team.
Although I do see the benefit, I see hardly any relation to version control...
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Sep 23 21:09:33 2006