Bug 546569 - Message for missing semicolon does not show in status bar when caret is after error squiggle
Summary: Message for missing semicolon does not show in status bar when caret is after...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.12   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-18 12:26 EDT by Eric Milles CLA
Modified: 2023-05-14 12:30 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Milles CLA 2019-04-18 12:26:21 EDT 
Consider the following:

    class Main {
      void meth() {
        System.err.println("Hello")
      }
    }

This code has an error squiggle displayed in the Java editor for missing semicolon on the closing paren.  If the caret is placed before the closing paren, the message "Syntax error, insert ";" to complete BlockStatements" is displayed in the gutter (display bar at bottom of window).  If the caret is placed after the closing paren, the message is not displayed.

Having the caret after the closing paren would seem to be the natural place for this message to be displayed.  When typing, the user is not going to back the caret up to before the error squiggle to see what is amiss.
Comment 1 Dani Megert CLA 2019-04-19 06:01:29 EDT 
Actually, in general we do not show the message in the status bar when the caret is before or after the squiggle, but only if it is inside.
Comment 2 Eclipse Genie CLA 2021-04-09 09:59:58 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-05-14 12:30:58 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.