Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 543569 - Content assistant is not working in "Debug Shell"
Summary: Content assistant is not working in "Debug Shell"
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 543566 543568 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-01-18 05:58 EST by Serhiy CLA
Modified: 2021-01-12 07:34 EST (History)
2 users (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 Serhiy CLA 2019-01-18 05:58:45 EST 
I am edebuging Junit test (Debug As->Junit Test) and content assiastant is ot working at all. Ctrl+Space does not trigger neither vaiable name completion nor method name completion.
Comment 1 Serhiy CLA 2019-01-18 08:59:17 EST 
It appers that is simple project it is working for me. I will post a sample to reproduce this problem
Comment 2 Andrey Loskutov CLA 2019-01-18 09:24:10 EST 
*** Bug 543568 has been marked as a duplicate of this bug. ***
Comment 3 Andrey Loskutov CLA 2019-01-18 09:24:28 EST 
*** Bug 543566 has been marked as a duplicate of this bug. ***
Comment 4 Sarika Sinha CLA 2019-01-20 22:41:00 EST 
I am not bale to reproduce it on Windows 7.
@Kalyan,
Can you please try it on Windows 10 ?
Comment 5 Kalyan Prasad Tatavarthi CLA 2019-01-21 00:00:34 EST 
(In reply to Sarika Sinha from comment #4)
> I am not bale to reproduce it on Windows 7.
> @Kalyan,
> Can you please try it on Windows 10 ?

I have not been able to reproduce this issue on Windows 10
Comment 6 Eclipse Genie CLA 2021-01-11 14:06:50 EST 
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.