[Python-bugs-list] [ python-Bugs-775012 ] No syntax hilite on new file until saved as *.py

[SourceForge.net]

Bugs item #775012, was opened at 2003-07-21 08:35
Message generated for change (Comment added) made by kbk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=775012&group_id=5470

Category: IDLE
Group: Python 2.3
Status: Open
>Resolution: Accepted
>Priority: 4
Submitted By: Andy Jewell (cybervegan)
Assigned to: Kurt B. Kaiser (kbk)
Summary: No syntax hilite on new file until saved as *.py

Initial Comment:
python 2.3c1, on windows xp, uk english.



When typing or pasting into a new text window, no 

syntax highlighting appears until the file is saved with 

a .py name.



I know it doesn't make sense to python-syntax highlight 

a non-python file, but shouldn't it default to 

highlighting?  



IDLE never used to do this - I assume it's a quirk of 

IDLEfork (maybe intentional behaviour i suppose).

----------------------------------------------------------------------

>Comment By: Kurt B. Kaiser (kbk)
Date: 2003-09-05 17:15

Message:
Logged In: YES 
user_id=149084

The following from GvR on IDLEfork Bug 763524 30Jun03:



"I've been using the latest version from Python CVS on

Win9: quite intensively over the last week. Some

observations:



- When reusing a blank untitled window to edit a Text

file, it keeps using Python coloring.



- When saving a Python with a non-Python extension

(e.g. .txt), it keeps the coloring.



- When switching off coloring by saving an untitle

buffer as a non-Python extension (e.g. .txt), it keeps

existing coloring.



- When opening a file reuses a blank untitled window,

it doesn't set the focus on the window."

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=775012&group_id=5470