I apologize: The first sentence of my last comment is inaccurate. I was able to reproduce the error with very few characters and as little as one line. Also, I did another test: I typed a shell script comment line in the first line of code, ran the external command, and checked the results. To my surprise, the highlight mode was switched appropriately--to Scripts-->sh. This indicates that after running certain external commands that modify the original file, gedit automatically re-detects the syntax based on the first two lines of a document. Thus, it makes sense that it kept switching to "C" highlighting mode, since Java and C have the same basic syntax. This isn't exactly a bug--just a missing feature: gedit could be a little bit smarter about how it re-detects the syntax after running such commands on the document--all it needs to do is check to see if the current highlighting mode is appropriate _before_ it tries to change it to the best choice--since the user may well have already selected the correct highlighting mode, either explicitly (by manually changing the setting) or implicitly (by choosing a certain file extension).
-- "Highlight Mode" reset after using "External Tools" plugin https://bugs.launchpad.net/bugs/346592 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
