From ff53a1b289fd99f9d6b29e420ec212666b5c3adc Mon Sep 17 00:00:00 2001 From: Andrew Gvozdev Date: Sun, 30 May 2010 03:29:09 +0000 Subject: [PATCH] bug 289168: [RegexErrorParser] Update Help --- .../tasks/cdt_o_tasksview.htm | 20 ++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_o_tasksview.htm b/doc/org.eclipse.cdt.doc.user/tasks/cdt_o_tasksview.htm index 7b56dded9e3..fc5b24f14c9 100644 --- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_o_tasksview.htm +++ b/doc/org.eclipse.cdt.doc.user/tasks/cdt_o_tasksview.htm @@ -4,15 +4,29 @@ -Viewing and managing compile errors +Dealing with compilation and other build errors -

Viewing and managing compile errors

+

Dealing with compilation and other build errors

-

The following topics describe how to view and manage compile errors. The CDT displays compile errors in the Console view.

+

After a build finishes, CDT displays the build output in the Console View. The build output shows +the result of build and a user can inspect it to find out if it was successful or not. To assist with that +CDT Error Parsers scan build output and create Problem Markers which are presented in a variety of ways: +

+There are 3 types of Problem Markers: Errors, Warnings and Info. A user can control how the markers are +generated on "Error Parsers" Preference page. +

+ +

The following topics describe how to view and manage compile errors.

Jumping to errors
Filtering the Problems view
Setting reminders