[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 136164] New: projectname.kdevelop file seems to randomly switch
From:       Ian Mackenzie <ian.e.mackenzie () gmail ! com>
Date:       2006-10-23 4:05:43
Message-ID: 20061023060541.136164.ian.e.mackenzie () gmail ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=136164         
           Summary: projectname.kdevelop file seems to randomly switch
                    between both forms of XML empty elements
           Product: kdevelop
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: ian.e.mackenzie gmail com


Version:           3.3.5 (using KDE 3.5.5, Gentoo)
Compiler:          Target: x86_64-pc-linux-gnu
OS:                Linux (x86_64) release 2.6.18-gentoo

My KDevelop project file (in my case, libcaddis.kdevelop) seems to switch randomly \
between <element></element> and <element/> forms of empty elements.  For instance, \
<prefixGet></prefixGet> sometimes changes to <prefixGet/> and sometimes changes back.

This isn't really a big deal, as it doesn't affect any functionality, but I have the \
libcaddis.kdevelop file under version control, so every time these spurious changes \
are made I have to commit the file again, and make sure to update it on my other \
computer to avoid getting any conflicts.  It would be nice if KDevelop used only one \
form for empty elements, as it would mean I would only have to commit updates to the \
libcaddis.kdevelop file only when actual changes were made.

I haven't noticed a definite pattern as to when the file gets changed, and which \
elements do (usually it's several), but if necessary I could play around and see if I \
can reproduce it reliably.


[prev in list] [next in list] [prev in thread] [next in thread]