|
From: SourceForge.net <no...@so...> - 2009-01-19 09:41:54
|
Feature Requests item #2519278, was opened at 2009-01-19 09:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=438938&aid=2519278&group_id=44253 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Definitions (source editor) Group: Small (< 1 pair-week) Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Disable non-Java settings when editing non-Java files Initial Comment: I'm editing a plain text file in DrJava (that's one non-Java file included in my DrJava project). I'm quite annoyed by the senseless coloration of words in DrJava's editor. Even more annoying is the Java-based tab key behavior. Whenever I press tab key the currently edited line goes where I don't want it or expect it to be (because the file after all is a plain text file that conforms not to Java's syntax rules, which is the basis for DrJava's tab behavior I believe). So, please disable Java-editing-features in DrJava's editor when it is used to edit non-Java files (could be easily recognized by file extension). Making the DrJava editor act like a plain text editor (no fancy stuff) would be better in this case (and for new non-saved text "buffers", it would be OK to have Java-editing-features initially enabled, until that buffer is saved to a file when then a decision - as to whether continue having the Java-editing-features enabled - is made based on the filename's extension). Thanks, -Moez (mo...@cs...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=438938&aid=2519278&group_id=44253 |