User forums > Using Code::Blocks

syntax-highlighting on write-protected sourcefiles fail

<< < (2/4) > >>

sethjackson:

--- Quote from: thomas on May 23, 2006, 01:13:53 pm ---
--- Quote ---when opening a write-protected file in the editor. The highlighting then is completely wrong. If the file is not write-protected, everything is fine.
--- End quote ---
This is no bug, it is intentional behaviour.


--- Quote ---it is sufficient to open the syntax-highlighting dialog and to terminate it with OK. Then this single write-protected file is shown with the correct highlighting until code::blocks is ended.
--- End quote ---
This is a bug.

--- End quote ---

Exactly.

EDIT:

Proposed fix here.

tiwag:
i don't understand the reason, why write protected files should not use the same highlighting scheme as non write protected.
why is this intentional ?


from my point of view it would be much more user-friendly, if write-protected files would use exactly the same highlighting-scheme as not write protected ones.

not everyone is using svn - in many companies version-control is done by other systems, which are using file-protecting until you have checked out a specific file to work with, but normally you have to look in many other files too, which you didn't check out for editing.
i find the current highlighting handling of write-protectde files really annoing. if you can't edit a file, you know already that it's write protected, that's enough.

mandrav:

--- Quote from: tiwag on May 24, 2006, 08:39:52 am ---if you can't edit a file, you know already that it's write protected, that's enough.

--- End quote ---

Well, the first few times this happened to me, I thought my keyboard was broken or a virus had entered my system :P

worster:
In my opinion, you could just place a little meaningful file icon to indicate a file is write-protected,
that's enough, and the syntax highlight should be the same as files which are not protected.

Just my point of view.

mandrav:
Well, I suggest someone should start a poll about this issue. Then we can go with what the community decides...

Navigation

[0] Message Index

[#] Next page

[*] Previous page