Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.forth    |    Forth programmers eat a lot of Bratwurst    |    117,927 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 116,544 of 117,927    |
|    sjack to albert@spenarnc.xs4all.nl    |
|    Re: Extensions for Forth files.    |
|    07 Jun 24 00:08:25    |
      From: sjack@dontemail.me              albert@spenarnc.xs4all.nl wrote:       > The official extension known to a linux system (make) are:              I use make to assemble my assembly level portion of Forth which       files have the known .s file-type. I also use make to build       extended Forths with file-types .f .fb etc. that it doesn't need       to know as the file parts and paths are provided in variables that       it happily processes.              My extensions:       s assembly source (Linux convention)       sh shell program (Linux convention)       fs Forth system source        The few extensions to the assembled code to give the        Forth its character (e.g turns FIG into a TOAD)       f General Forth extensions (of the character type).       fb Block file source        Main block file library       scr block file        Legacy block files       pac pack files (sequence file conversion of a block file)       d document (mime type: text/x-rsml)       rcd record file (mime type: text/x-rsml, Record simple markup)                     Note:       Linux provides various dot files for user to use his own       file-type mappings that overrides (registered) defaults.              In .vim for color syntax I have the following set       for Forth: .f .fs .fb .seq .4th .fth       I don't use FORTRAN so no conflict but wouldn't have one if I did.       Magic and mime can be used in manner to bypass file extension.              In .mimi.types I only needed settings for: .fb .scr              In lessfilter only: .fb .scr       (This is nice, any block file of .fb or .scr is auto-converted, using       dd, for display as a sequence file.)              I still use the .sh for shell scripts even though it doesn't       distinguish between Dash and Bash (which one is being used sometimes       makes a difference, but I somehow get around it.)              My Forths are in constant flux (shifting sands). I haven't updated       color syntax in a decade. What's there or not doesn't bother me.              A thought: If a standard set of extensions become a reality,       just soft link all the legacy files.              --       me              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca