User forums > Using Code::Blocks
syntax-highlighting on write-protected sourcefiles fail
stuffbit:
I trapped into the problem with syntax-highlighting because we are using MKS Source Integrity as a version control system for some of our projects. File-locking is realized with the write-protection-bit. It´s unusual to check-out files from the project-archive for only viewing them in an editor. SVN has a similar function (property svn:needs-lock) if you don´t want to merge files when they are committed to the repository.
I used CodeWright for many years as my preferred source-editor before I started to work with code::blocks.
- DZi
thomas:
--- Quote from: stuffbit on May 24, 2006, 10:47:55 am ---SVN has a similar function (property svn:needs-lock) if you don´t want to merge files when they are committed to the repository.
--- End quote ---
While the arguments about some other revision control systems are certainly correct, locking in SVN is only to be used for files that do not work well for merging, such as binary images. You can of course do differently, but that is wrong.
In the Subversion philosophy, locking is "considered generally harmful to collaboration".
Every file that can be edited in Code::Blocks can be merged without problems. Therefore, in the normal case, no such file should be locked. There may be exceptions to this rule, but there are few.
sethjackson:
I think the way C::B handles the syntax highlighting of write protected files is ok, but this is my opinion.....
ProutDeMammouth:
--- Quote from: mandrav on May 24, 2006, 10:02:11 am ---Well, I suggest someone should start a poll about this issue. Then we can go with what the community decides...
--- End quote ---
or just add an option somewhere.
sethjackson:
--- Quote from: ProutDeMammouth on May 24, 2006, 01:53:57 pm ---
--- Quote from: mandrav on May 24, 2006, 10:02:11 am ---Well, I suggest someone should start a poll about this issue. Then we can go with what the community decides...
--- End quote ---
or just add an option somewhere.
--- End quote ---
That is an even better idea. :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version