Bug 420527 - more features for files which are not in buildpath and with the wrong filename
Summary: more features for files which are not in buildpath and with the wrong filename
Status: NEW
Alias: None
Product: DLTK
Classification: Technology
Component: Common (show other bugs)
Version: 5.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: dltk.common-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 420361
  Show dependency tree
 
Reported: 2013-10-28 13:26 EDT by Simon Bernard CLA
Modified: 2018-02-08 10:01 EST (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 Simon Bernard CLA 2013-10-28 13:26:26 EDT 
(ok bug title really sucks, but I can find a better one :p)

Some editor features (like autocompletion,task,validation, outline ...) are not available if the file is not in the source path and if does not match the file extension.

It could be cool, if this feature are available when user decides to open this kind of file with a DLTK editor even if it does not respect the 2 previous rules.
Comment 1 Eclipse Genie CLA 2018-02-07 09:11:59 EST 
New Gerrit change created: https://git.eclipse.org/r/116856
Comment 2 Dawid Pakula CLA 2018-02-07 16:10:09 EST 
Patch solves problem with file outside build path but inside folder, files inside projected root worked fine.

Problem with content-type based on file content (rather than extension only) probably should be moved to different bug.