00:00:00 --- log: started forth/20.11.19
01:44:53 --- log: started forth/20.11.19
01:44:53 --- join: clog joined #forth
01:44:53 --- topic: 'Forth Programming | logged by clog at http://bit.ly/91toWN backup at http://forthworks.com/forth/irc-logs/ | If you have two (or more) stacks and speak RPN then you're welcome here! | https://github.com/mark4th'
01:44:53 --- topic: set by proteusguy!~proteusgu@cm-58-10-208-146.revip7.asianet.co.th on [Mon Dec 30 10:43:28 2019]
01:44:53 --- names: list (clog mtsd spoofer X-Scale dys wj Kumool sts-q gravicappa boru Zarutian_HTC1 siraben cheers _whitelogger MrMobius proteusguy Lord_Nightmare rixard wineroots mjl ecraven catern tangentstorm jedb crc +KipIngram koisoke Vedran cp- remexre cantstanya actuallybatman tabemann jimt[m] ovf routeveg klys Chobbes rprimus iyzsong patrickg APic inode pareidolia phadthai rann ggVGc crest_ guan dnm dzho bluekelp FUZxxl irsol lonjil ornxka Keshl WilhelmVonWeiner jn__ a3f tolja)
01:44:53 --- names: list (ptrkriz cmtptr heredoc DKordic rpcope neuro_sys crc- nmz presiden arrdem pointfree dddddd diginet2 fiddlerwoaroof the_cuckoo veltas C-Keen djinni)
03:12:14 --- quit: wj (Quit: Leaving)
03:58:34 --- quit: Zarutian_HTC1 (Remote host closed the connection)
03:59:40 --- join: dave0 joined #forth
04:09:25 --- quit: _whitelogger (Remote host closed the connection)
04:12:23 --- join: _whitelogger joined #forth
06:10:30 --- quit: dave0 (Quit: dave's not here)
06:33:56 --- quit: mtsd (Quit: Leaving)
08:53:24 --- join: X-Scale` joined #forth
08:54:59 --- quit: X-Scale (Ping timeout: 246 seconds)
08:54:59 --- nick: X-Scale` -> X-Scale
09:34:18 --- join: WickedShell joined #forth
10:55:07 <veltas> Are there text editors with good syntax highlighting for Forth? (don't say color forth)
10:55:34 <veltas> Because vim's is not good, it is easier to read with it off
10:56:27 <veltas> I don't know how to do a good job with it, but probably just matching comments would be better than the confused mess I get on vim
10:59:43 <cmtptr> yeah, that was my experience as well.  i ended up writing my own, but i don't think it would be helpful to you because over time it became very specific to my own weird dialect
11:01:38 --- quit: gravicappa (Ping timeout: 240 seconds)
11:02:04 <boru> There are a bunch of syntax schemes for Forth for vim around the web. The default is a bit crap, but a proper colour scheme helps also, imho; I use zenburn/darkburn.
11:02:39 <veltas> I'll try that out, thanks for the suggestion
11:03:05 <boru> Sure thing. I would strongly recommend trying some of the other syntax files, though.
11:03:33 <boru> Or, if you have the time, writing one. It's what I ended up doing for Forth and some other languages, also.
11:03:39 --- join: gravicappa joined #forth
11:04:12 <boru> You could also try grabbing one from the web and modifying it to your liking.
11:04:25 <veltas> At work I have to write a lot of assembly and often the C highlighter does a better job than asm.vim
11:04:55 <boru> Don't get me started; I write a lot of assembly for various ISAs, also. I've written syntax files for a bunch of ISAs at this point.
11:05:00 <veltas> I have written a few syntax highlighters for vim, but for languages that don't usually have the amount of control that forth has over its interpreter
11:05:24 <boru> Then updating C one for C99/11, and I wrote some for Verilog and VHDL, also.
11:05:30 <veltas> Have you got a good one for PPC that can handle C preprocessor directives as well?
11:05:54 <boru> I don't, alas. I haven't done much power stuff, and not for a long time.
11:06:00 <veltas> I'm mostly writing PPC at the moment :(
11:06:15 <boru> It could be worse.
11:06:22 <veltas> Just keep typing rlwinm, it will work eventually etc
11:06:29 * boru chuckles.
11:09:10 <veltas> Ah yes I had to turn the bracket/paren error highlights off in C
11:10:03 <veltas> Using compound literals will scare vim's C highlighter and convince GitHub you are writing C++
11:10:04 <boru> I use YCM and Ale for that; they're not as obnoxious as other plugins.
11:10:25 <boru> But the default also has crap highlighting for C99 and C11.
11:12:21 <veltas> Oh sorry by the way the whole time I have been saying "syntax highlighting" I mean specifically what goes in vim syntax directories, not the color scheme
11:12:32 --- quit: Vedran (Ping timeout: 256 seconds)
11:12:51 --- join: Vedran joined #forth
11:12:51 <boru> Ah, I see.
11:13:05 <boru> I thought we had digressed a bit.
11:13:13 <veltas> I realise now when I looked up zenburn
11:13:28 <boru> But what I said above wrt writing syntax files still holds.
11:13:42 <boru> The only theme-related thing was the comment about zenburn.
11:13:48 <veltas> Yes I think I will have to do that for forth, and keep it very simple as I said
11:14:12 <boru> FWIW, you can load a syntax file for a given dialect quite easily, if you wanted to do so.
11:14:37 <boru> Or just take someone's all-singing-all-dancing syntax file and edit it to fit your prefernce.
11:18:42 <siraben> veltas: I use Emacs and the Forth syntax highlighting is decent
11:18:45 <veltas> I am just editing one I wrote
11:19:05 <veltas> siraben: That's interesting to know, might have a peek to see how they do it
11:39:17 <the_cuckoo> i kinda like the look/color choice of vim's forth, but the handling of dw/cw is awful - i just can't seem to find what needs to change to correct that 
11:40:42 <cmtptr> mine was pretty simple: everything got preprocessor coloring by default, then no coloring when in compilation mode, and then there were some patterns to match naming conventions for parsing words and literals, and then some control flow keywords and comments
11:41:23 <cmtptr> only works if you always name your parsing words to satisfy the convention, though
11:43:42 <veltas> I'm sure there are people that can just switch between vim and emacs and get all the chords right
11:43:51 <veltas> I've already forgotten everything
11:49:17 <the_cuckoo> when you reach the age of 50, forgetting eveything, including what people are talking about, is par for the course
11:52:10 --- quit: Vedran (Read error: Connection reset by peer)
11:52:22 <veltas> Not quite there yet
11:52:23 <cmtptr> that's why my plan is to never reach 50
11:52:28 <veltas> ^
11:52:32 --- join: Vedran joined #forth
12:43:34 <veltas> Highlight double quotes or not, it looks a bit weird either way
12:47:26 <the_cuckoo> cmtptr: life gets more interesting when you reach 50 - mostly cos you can't rememeber what the hell happened before you got there - adds a sense of adventure to everything (like talking to your wife and going "who are you agian?")
12:48:44 <the_cuckoo> all stuff to look forward to
12:55:21 <cmtptr> veltas, do you mean the token itself or the entire string literal?
12:55:25 <cmtptr> if the latter, i say yes
13:02:49 <veltas> By "entire string literal" you mean including the part before the quote?
13:03:05 <veltas> e.g. the whole of ." example"
13:03:49 <cmtptr> yeah
13:04:59 <veltas> If I do that I can't highlight it with a string literal color, it looks wrong. I can use another color though
13:06:42 <cmtptr> vim does the same in c for L"xxx"
13:07:05 <cmtptr> not sure if that's really the same in your mind, but there it is if you care
13:08:38 <veltas> Really a matter of taste, no right answer with forth's syntax
13:08:41 --- join: lispmacs[work] joined #forth
13:08:49 <cmtptr> of course
13:09:09 <cmtptr> but if you have two options and you think they're both wrong, then you have a problem
13:16:42 --- quit: gravicappa (Ping timeout: 256 seconds)
13:23:02 --- join: dave0 joined #forth
13:24:18 --- quit: Vedran (Ping timeout: 240 seconds)
13:24:30 --- join: Vedran joined #forth
13:42:35 <veltas> Oh the string literal color doesn't look bad actually, fucked it up last time
14:30:10 --- join: Zarutian_HTC joined #forth
15:00:37 --- quit: dave0 (Read error: Connection reset by peer)
15:05:53 --- join: dave0 joined #forth
16:02:59 --- quit: Zarutian_HTC (Remote host closed the connection)
16:06:04 --- join: Zarutian_HTC joined #forth
17:05:19 --- join: marksmith joined #forth
18:06:26 --- quit: X-Scale (Ping timeout: 256 seconds)
18:07:21 --- join: X-Scale` joined #forth
18:07:47 --- join: [X-Scale] joined #forth
18:08:42 --- nick: [X-Scale] -> X-Scale
18:19:18 --- quit: marksmith (Ping timeout: 272 seconds)
18:20:55 --- join: Zarutian_HTC1 joined #forth
18:20:55 --- quit: Zarutian_HTC (Read error: Connection reset by peer)
18:23:09 --- quit: WickedShell (Remote host closed the connection)
18:31:42 --- join: boru` joined #forth
18:31:44 --- quit: boru (Disconnected by services)
18:31:47 --- nick: boru` -> boru
18:41:56 --- quit: Zarutian_HTC1 (Remote host closed the connection)
20:11:53 --- join: jsoft joined #forth
20:53:18 --- quit: sts-q (Ping timeout: 240 seconds)
21:00:33 --- join: sts-q joined #forth
21:32:06 --- join: gravicappa joined #forth
22:02:58 --- quit: X-Scale (Ping timeout: 240 seconds)
22:03:30 --- quit: X-Scale` (Ping timeout: 272 seconds)
22:04:51 --- join: [X-Scale] joined #forth
22:04:57 --- join: NorthStar joined #forth
22:05:46 --- nick: [X-Scale] -> X-Scale
22:06:27 --- quit: veltas (Ping timeout: 240 seconds)
22:07:25 --- join: veltas joined #forth
22:12:24 --- quit: _whitelogger (Remote host closed the connection)
22:15:22 --- join: _whitelogger joined #forth
23:42:28 --- join: hosewiejacke joined #forth
23:50:17 --- quit: phadthai (Ping timeout: 265 seconds)
23:50:50 --- join: phadthai joined #forth
23:59:59 --- log: ended forth/20.11.19