Zarutian_HTC1 has quit [Remote host closed the connection]
dave0 has joined #forth
_whitelogger has joined #forth
dave0 has quit [Quit: dave's not here]
mtsd has quit [Quit: Leaving]
X-Scale` has joined #forth
X-Scale has quit [Ping timeout: 246 seconds]
X-Scale` is now known as X-Scale
WickedShell has joined #forth
<veltas>
Are there text editors with good syntax highlighting for Forth? (don't say color forth)
<veltas>
Because vim's is not good, it is easier to read with it off
<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
<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
gravicappa has quit [Ping timeout: 240 seconds]
<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.
<veltas>
I'll try that out, thanks for the suggestion
<boru>
Sure thing. I would strongly recommend trying some of the other syntax files, though.
<boru>
Or, if you have the time, writing one. It's what I ended up doing for Forth and some other languages, also.
gravicappa has joined #forth
<boru>
You could also try grabbing one from the web and modifying it to your liking.
<veltas>
At work I have to write a lot of assembly and often the C highlighter does a better job than asm.vim
<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.
<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
<boru>
Then updating C one for C99/11, and I wrote some for Verilog and VHDL, also.
<veltas>
Have you got a good one for PPC that can handle C preprocessor directives as well?
<boru>
I don't, alas. I haven't done much power stuff, and not for a long time.
<veltas>
I'm mostly writing PPC at the moment :(
<boru>
It could be worse.
<veltas>
Just keep typing rlwinm, it will work eventually etc
* boru
chuckles.
<veltas>
Ah yes I had to turn the bracket/paren error highlights off in C
<veltas>
Using compound literals will scare vim's C highlighter and convince GitHub you are writing C++
<boru>
I use YCM and Ale for that; they're not as obnoxious as other plugins.
<boru>
But the default also has crap highlighting for C99 and C11.
<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
Vedran has quit [Ping timeout: 256 seconds]
Vedran has joined #forth
<boru>
Ah, I see.
<boru>
I thought we had digressed a bit.
<veltas>
I realise now when I looked up zenburn
<boru>
But what I said above wrt writing syntax files still holds.
<boru>
The only theme-related thing was the comment about zenburn.
<veltas>
Yes I think I will have to do that for forth, and keep it very simple as I said
<boru>
FWIW, you can load a syntax file for a given dialect quite easily, if you wanted to do so.
<boru>
Or just take someone's all-singing-all-dancing syntax file and edit it to fit your prefernce.
<siraben>
veltas: I use Emacs and the Forth syntax highlighting is decent
<veltas>
I am just editing one I wrote
<veltas>
siraben: That's interesting to know, might have a peek to see how they do it
<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
<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
<cmtptr>
only works if you always name your parsing words to satisfy the convention, though
<veltas>
I'm sure there are people that can just switch between vim and emacs and get all the chords right
<veltas>
I've already forgotten everything
<the_cuckoo>
when you reach the age of 50, forgetting eveything, including what people are talking about, is par for the course
Vedran has quit [Read error: Connection reset by peer]
<veltas>
Not quite there yet
<cmtptr>
that's why my plan is to never reach 50
<veltas>
^
Vedran has joined #forth
<veltas>
Highlight double quotes or not, it looks a bit weird either way
<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?")
<the_cuckoo>
all stuff to look forward to
<cmtptr>
veltas, do you mean the token itself or the entire string literal?
<cmtptr>
if the latter, i say yes
<veltas>
By "entire string literal" you mean including the part before the quote?
<veltas>
e.g. the whole of ." example"
<cmtptr>
yeah
<veltas>
If I do that I can't highlight it with a string literal color, it looks wrong. I can use another color though
<cmtptr>
vim does the same in c for L"xxx"
<cmtptr>
not sure if that's really the same in your mind, but there it is if you care
<veltas>
Really a matter of taste, no right answer with forth's syntax
lispmacs[work] has joined #forth
<cmtptr>
of course
<cmtptr>
but if you have two options and you think they're both wrong, then you have a problem
gravicappa has quit [Ping timeout: 256 seconds]
dave0 has joined #forth
Vedran has quit [Ping timeout: 240 seconds]
Vedran has joined #forth
<veltas>
Oh the string literal color doesn't look bad actually, fucked it up last time
Zarutian_HTC has joined #forth
dave0 has quit [Read error: Connection reset by peer]