Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
What a crummy email interface GitHub has!!!!!!
No argument, it should remove it and just be a website with email notifications.
Kind of like you asking for a "Geany filetype" without explaining what you mean.
"Filetype" is basic terminology used throughout the Geany manual and UI (Document->Set Filetype-> ... etc ) and is displayed in the status bar as filetype: F77 as your new image shows and thats explicitly what I asked for: "What filetype shows in the status bar for one of those files?". Sadly your original images did not show the status bar but your new one does and it correctly shows F77.
Images have their uses, but should be used sparingly, you are spamming everybody watching the repo with them and as above they often omit the important part.
Thank you for the example, for the same reason as above, next time please put it in a Gist and just paste the link here.
The example highlights here when opened after I add *.F77; to the filetype.extensions file.
Geany stores whatever syntax it was using and never checks again until a "new" .conf requires a reload. Stopping and starting Geany will not "fix" an existing opened file.
What I think you call the "syntax" is the "filetype" we are talking about, and yes Geany will not change the filetype of an opened file, because a user can set the filetype and it should not therefore be changed. That is preserved in the Geany session and therefore over restart. You can either set it yourself, or close and re-open the file.
... changing both local .conf and system ...
If you mean you edited the files directly instead of the suggested method here? If so you need to reload configuration, or restart Geany to load the edited config file, whereas using the menu does it automatically on save. Then you also need to re-open the file to have its filetype autodetected again.
There is some kind of parsing error for the F77 geany type that doesn't like *.F77; if it is the last thing in the line.
Works here, the F77 line in my filetype.extensions is exactly the same as that shown in your image and your example (saved as /tmp/untitled.F77) works. I am not sure where the problem is, I can't see your setup, but the parsing of conf files is performed by the Glib library that is in use everywhere GTK is, not Geany code, so its unlikely it has such an obvious bug as missing the end of the list. I suspect a procedure issue as explained above which was cured when you made an additional change.
As a workaround, if these file extensions could just be "functional" in the base package the other issues wouldn't surface.
Not sure what you mean, is that "functional" as in functional languages like Haskell or what?
The filetype extensions are specified in a configuration file exactly to cater for examples like this, where a specific use-case needs additional extensions, and to allow users to tailor the annoying case of two applications using the same extension (Matlab and Objective C .m for example).
I've been in IT over 30 years writing software on many platforms and given the pictures I provided I had no clue what you were asking.
Well as I have 15+ more years experience than you I guess I can call you a newby
But its very likely that whoever contributed the fortran filetype and extensions list was even younger and had never heard of VMS, or a Teletype, (ASR33 anybody?) so since .F77 isn't listed as an extension for GNU gfortran (but .f77 is) it wasn't added to the list. Geany is a volunteer project and people contribute what they know about.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.