Issue 775012: No syntax hilite on new file until saved as *.py (original) (raw)

Issue775012

Created on 2003-07-21 13:35 by cybervegan, last changed 2022-04-10 16:10 by admin. This issue is now closed.

Messages (3)
msg17170 - (view)	Author: Andy Jewell (cybervegan)	Date: 2003-07-21 13:35
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).
msg17171 - (view)	Author: Kurt B. Kaiser (kbk) *	Date: 2003-09-05 22:15
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."
msg17172 - (view)	Author: Kurt B. Kaiser (kbk) *	Date: 2005-06-12 04:37
Logged In: YES user_id=149084 Fixed by Patch 1196895, Jeff Shute.