> > Geany stores whatever syntax it was using and never checks again […]. 
> > Stopping and starting Geany will not "fix" an existing opened file.

> Isn't that the only real issue here? 

No. I had many files to choose from. I closed all that were open. I bounced 
Geany and chose different .F77 files. I just replicated the entire problem on 
this system as well.
![f77-bug-100](https://user-images.githubusercontent.com/1883220/224029659-56c4d8e5-a179-44b6-ae0e-a8843a4ef304.png)

I made the change to extensions, saved the file, bounced Geany, loaded a 
completely different .F77 file and had it not highlight. When *.F77; isn't dead 
last in the list, it works. When it is dead last highlighting does not work.

At this point I'm done. I've reported the bug, reproduced the bug on an 
entirely different system, and answered questions. I use pictures so I don't 
get pulled into a terminology war and now I'm being pulled into a terminology 
war. I always paste everything in the report because using something like Gist 
is _exactly_ how critical information gets lost. Internet rot strikes without 
warning.

Thank you for your time. 

I now have to go un-install Geany from the 6-8 machines that will be used for 
this project. They will either have to use Emacs to have a combined editor and 
GDB front end or split editor and GDB front end.

Fix it, don't fix it, I've reported it and replicated it on different OS.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3425#issuecomment-1462032042
You are receiving this because you are subscribed to this thread.

Message ID: <geany/geany/issues/3425/[email protected]>

Reply via email to