Bug 334634 - Makefile editor fails to colorize when file is not named Makefile or *.mk
Summary: Makefile editor fails to colorize when file is not named Makefile or *.mk
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-editor (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
: 371317 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-18 08:21 EST by Jate Sujjavanich CLA
Modified: 2020-09-04 15:19 EDT (History)
4 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 Jate Sujjavanich CLA 2011-01-18 08:21:52 EST 
Build Identifier: 20100917-0705

The Makefile editor will open certain files but not syntax colorize. I tested by copying a known good Makefile to various names. I then right-clicked, chose "Open With", "Other...", "Makefile Editor".

linux_Makefile, Makefile.test are not colorized
*.mk is colorized

If the file is recognized as a Makefile, the selection for Other...\Makefile Editor does not have to be made because it's already selected by default.


Reproducible: Always

Steps to Reproduce:
1. Rename a Makefile which takes syntax coloring to a name which does not match the pattern *.mk or Makefile.
2. Open the file using the Makefile editor.
Comment 1 Andrew Gvozdev CLA 2012-02-12 13:32:39 EST 
*** Bug 371317 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Gvozdev CLA 2012-02-12 13:36:39 EST 
I think this request is probably valid but as a workaround try to specify content type of your file in Preferences->General->Content Types then select content type as Text->Makefile.
Comment 3 Josh Davidson CLA 2012-02-13 23:32:52 EST 
Adding via General->Content types does work, but oddly adding via General->Editors->File Associations does not.