Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Paul E Bennett Newsgroups: comp.lang.forth Subject: Re: Making Forth official Date: Thu, 21 Nov 2013 23:27:39 +0000 Organization: Hidecs Consultancy Lines: 34 Message-ID: References: <528e0962$0$26909$e4fe514c@dreader37.news.xs4all.nl> <2013Nov21.145702@mips.complang.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Trace: individual.net lRrsX/VGECSeB/Kn25fh0AFdO2k54/95Czwu6WXSpH8is8gMXR Cancel-Lock: sha1:nYVV3+BT3z6C6M3JtmIMzoalhaU= User-Agent: KNode/4.10.5 Xref: csiph.com comp.lang.forth:26900 Mark wrote: > "Paul E Bennett" wrote in message > news:bf6oboFld0gU1@mid.individual.net... >> >>As one who uses the .fth extension for Forth Source files and usually the >>Kwrite Editor on a linux System, I would vote for the .fth etension to be >>included. >> >>Kwrite actually manages to do some interesting highlighting with the >>source code without having to be told about it. None of the highlighting >>effects affect the source code delivered to VfXForth. > > I guess that if you have a reasonably new version of Kwrite (post December > 2011) then this might be my syntax highlighter. I asked on CLF for > commonly used file extensions and ended up including .4th, .f, .frt, .fs, > .fth and .seq. > > Regards > > Mark Yes, the one I am using at the moment is a very recent version. Thanks, the highlighting is quite nice. -- ******************************************************************** Paul E. Bennett IEng MIET..... Forth based HIDECS Consultancy............. Mob: +44 (0)7811-639972 Tel: +44 (0)1235-510979 Going Forth Safely ..... EBA. www.electric-boat-association.org.uk.. ********************************************************************