What a crummy email interface GitHub has!!!!!!
I couldn't understand your questions but this (&)(&)(*& strips out images from email. I use images so we don't end up going down a terminology rabbit hole. Kind of like you asking for a "Geany filetype" without explaining what you mean. 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. Now I realize you never saw the pictures. GitHub really is barbaric.

I'm dealing with relative in hospital. Can check email, but cannot always get to GitHub and even if I could would need screen shots from this machine in office.

So, from the beginning: System

Configured file types

That was only uncommented with .F77 added after Geany failed to recognize .F77 as a Fortran 77 file extension.

.F90 file extension worked out of the box

.F77 file extension does not, even with the addition in ~/.config/geany/filetype_extensions.conf and a restart of Geany

If I save that exact file with a .f77 file extension Geany likes it.

Even if I change the system level file and restart Geany, it does not like files with .F77 extension.

When I went back in for grins and giggles to my local .conf and added *.F78; after the *.F77; then saved, Geany now started liking .F77 files. Didn't have to exit at all.

Here is a short .F77 file if you wish to test.

FTN_FILL_IN_LOGICALS.F77

        SUBROUTINE FTN_FILL_IN_LOGICALS
        IMPLICIT NONE
C
C       Subroutine to fill in all of the logicals needed by the 
C       Mega_Zillionare application when written in fortran
C

        INCLUDE 'SYS$LIBRARY:FORSYSDEF(LIB$ROUTINES)'

C;;;;;
C       Fill in default file names
C;;;;;
        CHARACTER*12    DRAWING_DATA
        DATA DRAWING_DATA/'MY_MEGA_FILE'/

        CHARACTER*13    DRAWING_STATS
        DATA DRAWING_STATS/'DRAWING_STATS'/

        CHARACTER*10    MEGA_STATS
        DATA MEGA_STATS/'MEGA_STATS'/ 



        CHARACTER*255   TRANSLATED_NAME_STR, WORK_STR
        CHARACTER*1     FIRST_CHAR
        INTEGER*4       L_X
        INTEGER*2       W_X
        LOGICAL         IS_BLANK_LG


C;;;;;
C       Make certain the drawing_data logical exists
C       if not, give it a value in the local directory
C;;;;;
        TRANSLATED_NAME_STR = ' '
        L_X = LIB$GET_LOGICAL( DRAWING_DATA, TRANSLATED_NAME_STR, 
     1          W_X,,,,)


        FIRST_CHAR = TRANSLATED_NAME_STR
        IS_BLANK_LG = FIRST_CHAR .EQ. ' '

        IF (IS_BLANK_LG) THEN
            TRANSLATED_NAME_STR = DRAWING_DATA // '.IDX'
            L_X = LIB$SET_LOGICAL( DRAWING_DATA, 
     1              TRANSLATED_NAME_STR,,,)
        END IF


        TRANSLATED_NAME_STR = ' '
        L_X = LIB$GET_LOGICAL( DRAWING_STATS, TRANSLATED_NAME_STR, 
     1          W_X,,,,)


        IF (TRANSLATED_NAME_STR(1:1) .EQ. ' ') THEN
            TRANSLATED_NAME_STR = DRAWING_STATS // '.IDX'
            L_X = LIB$SET_LOGICAL( DRAWING_STATS, 
     1              TRANSLATED_NAME_STR,,,)
        END IF



        TRANSLATED_NAME_STR = ' '
        L_X = LIB$GET_LOGICAL( MEGA_STATS, TRANSLATED_NAME_STR, 
     1          W_X,,,,)


        FIRST_CHAR = TRANSLATED_NAME_STR

        IF (FIRST_CHAR .EQ. ' ') THEN
            TRANSLATED_NAME_STR = MEGA_STATS // '.IDX'
            L_X = LIB$SET_LOGICAL( MEGA_STATS, 
     1              TRANSLATED_NAME_STR,,,)
        END IF


        RETURN
        END

This acts like multiple things are going on.

1. 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.
2. 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. I mean I tried opening many different files after changing both local .conf and system without Geany recognizing .F77 as an F77 file.
3. Something else I haven't tracked down.

On the big systems
*.F is common for Fortran IV or earlier (Yes, lots of that still in production.)
*.FIV for shops that were straddling the change between Fortran IV and Fortran 77
*.F77 for Fortran 77.
We always used upper case because that is all the early terminals had.

I hope this answers all of the questions.

As a workaround, if these file extensions could just be "functional" in the base package the other issues wouldn't surface.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <geany/geany/issues/3425/1460298214@github.com>