This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Dev 8.2 / 201609040002 Product Version = NetBeans IDE Dev (Build 201609040002) Operating System = Windows 10 version 10.0 running on amd64 Java; VM; Vendor = 1.8.0_60 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.60-b23 - Make a php file "file1.php" - Make a php file "file2.php" - In file2.php, type : ----- <?php include "" ----- - Invoke auto completion between the quotes What occurs : => Nothing is suggested (as files) What's expected : => filename suggestion to "file1.php"
Created attachment 162879 [details] screenshot I can't reproduce it in NetBeans 8.2. Product Version: NetBeans IDE 8.2 (Build 201609300101) Java: 1.8.0_111; Java HotSpot(TM) 64-Bit Server VM 25.111-b14 Runtime: Java(TM) SE Runtime Environment 1.8.0_111-b14 System: Linux version 4.4.0-47-generic running on amd64; UTF-8; ja_JP (nb) Thanks.
(In reply to junichi11 from comment #1) > Created attachment 162879 [details] > screenshot > > I can't reproduce it in NetBeans 8.2. > > Product Version: NetBeans IDE 8.2 (Build 201609300101) > Java: 1.8.0_111; Java HotSpot(TM) 64-Bit Server VM 25.111-b14 > Runtime: Java(TM) SE Runtime Environment 1.8.0_111-b14 > System: Linux version 4.4.0-47-generic running on amd64; UTF-8; ja_JP (nb) > > Thanks. Hi, Please note that the test case doesn't take the semi-column on the end of the line (as in your test). If the semi-column isn't present, the auto-completion doesn't suggest files. I reopen this issue.
(In reply to amobilia from comment #2) > Please note that the test case doesn't take the semi-column on the end of > the line (as in your test). > > If the semi-column isn't present, the auto-completion doesn't suggest files. > > I reopen this issue. I see now. Unfortunately, we cannot fix it in the current implementation (the parser is used). Because there is a syntax error. I think that users can add a semicolon easily [Ctrl + ;]. Thanks.
(In reply to junichi11 from comment #3) > we cannot fix it in the current implementation Sorry, I'm wrong. Probably, it can be fixed. Thanks.