The unified diff between revisions [0fba98c8..] and [88b6620e..] is displayed below. It can also be downloaded as a raw diff.

#
#
# patch "distrib/known-problems"
#  from [d01eb2de5657a9ed2effe84a19c04e3b5b439faa]
#    to [cace4fa3452d24e188b8f94a8cdf09c11a1a198c]
#
============================================================
--- distrib/known-problems	d01eb2de5657a9ed2effe84a19c04e3b5b439faa
+++ distrib/known-problems	cace4fa3452d24e188b8f94a8cdf09c11a1a198c
@@ -1,11 +1,5 @@ Known Problems fixed in GPS 4.3.0
 Known Problems fixed in GPS 4.3.0

-- H904-015: Files status disappearing from VCS Explorer
-  Problem:    When committing a file or editing a revision log file
-              statuses (Needs update and Needs merge) are disappearing
-              from the VCS Explorer.
-  Workaround: Launch a Query Status action to get back the statuses.
-
 - HB17-006: Wrong coverage highlighting
   Problem:    GPS doesn't update the list of uncovered lines in the locations
 	      window after reloading coverage information for a single file.
@@ -20,23 +14,12 @@ Known Problems fixed in GPS 4.3.0
               and take into account the reamining file contents.
   Workaround:  Remove the NUL characters before loading the file in GPS.

-- HA05-007: Cannot create .gps directory for path with non ASCII characters
-  Problem:    If the HOME (or GPS_HOME) environment variable contains
-              non ASCII characters, GPS fails to create the .gps
-              directory.
-  Workaround: Use a GPS_HOME which contains only plain ASCII characters
-
 - HB04-009: Debugger console has no keyboard focus on title click
   Problem:    If you click in the title bar or the tab of the debugger
               console, the cursor is not activated in the console, and
               you need to click inside it before typing
   Workaround: Click in the middle of the console to give it focus

-- D502-003: Procedure name too long and overlap with VCS status
-  Problem:    On the editor's status bar if a procedure name is
-              too long it will overlap with the VCS status.
-  Workaround: Use the VCS Explorer which displays the proper status
-
 - HA14-009: Wrong dialog settings in project properties
   Problem:    On Vista the dialog checks for proper file permissions. As the
               dialog on the project properties (to select a global pragma
@@ -44,6 +27,12 @@ Known Problems fixed in GPS 4.3.0
               to select a file which was read-only.
   Workaround: Change file permissions to read-write.

+- HA05-007: Cannot create .gps directory for path with non ASCII characters
+  Problem:    If the HOME (or GPS_HOME) environment variable contains
+              non ASCII characters, GPS fails to create the .gps
+              directory.
+  Workaround: Use a GPS_HOME which contains only plain ASCII characters
+
 - H915-002: File view from project filter no working
   Problem:    On the file view when activating the
               "Show files from project only" filter there is nothing
@@ -57,6 +46,12 @@ Known Problems fixed in GPS 4.3.0
   Workaround: Launch gprbuild using the Build->Make->Custom... menu, or use
               gprmake.

+- H904-015: Files status disappearing from VCS Explorer
+  Problem:    When committing a file or editing a revision log file
+              statuses (Needs update and Needs merge) are disappearing
+              from the VCS Explorer.
+  Workaround: Launch a Query Status action to get back the statuses.
+
 - H903-019: Generated documentation is displayed incorrectly with IE6
   Problem:    The documentation generator engine of GPS generates html code
               that uses the CSS style "white-space: pre;" which is not handled
@@ -133,6 +128,14 @@ Known Problems fixed in GPS 4.3.0
               A similar behavior can be observed when renaming a file.
   Workaround: Create new files or rename files outside GPS before loading them.

+- H704-007: Closing nodes in call graph still shows locations
+  Problem:    If you select the contextual menu "... calls", you get a
+              call tree, which shows location on its right-hand part. If
+              you fold the toplevel node, the locations are still visible,
+              although clicking on them has no effect
+  Workaround: Expand the node again, and select the entity for which you
+              want to see the locations.
+
 - H630-002: Incorrect file in xref after changing scenario
   Problem:    GPS incorrectly resets its internal xref cache when the scenario
               variables are changed. Do a query from file A, which ends into
@@ -165,14 +168,6 @@ Known Problems fixed in GPS 4.3.0
               is still possible to use an older version of GDB (coming from a
               previous release of GNAT Pro).

-- H704-007: Closing nodes in call graph still shows locations
-  Problem:    If you select the contextual menu "... calls", you get a
-              call tree, which shows location on its right-hand part. If
-              you fold the toplevel node, the locations are still visible,
-              although clicking on them has no effect
-  Workaround: Expand the node again, and select the entity for which you
-              want to see the locations.
-
 - H611-032: File Dependencies plug-in fails
   Problem:    If you active the filedeps.py plugin, you see a new menu
               /Navigate/Show File Dependency Path. However, this menu will
@@ -494,3 +489,8 @@ Known Problems fixed in GPS 4.3.0
   Problem:    It is possible to have an empty revision log when
               committing multiple files selected on the VCS Explorer.
   Workaround: Commit one file at a time or use an activity
+
+- D502-003: Procedure name too long and overlap with VCS status
+  Problem:    On the editor's status bar if a procedure name is
+              too long it will overlap with the VCS status.
+  Workaround: Use the VCS Explorer which displays the proper status