26 Jun
2018
26 Jun
'18
1:47 p.m.
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
On Tuesday 26 June 2018 08:51:15 Dr. Nikolaus Klepp
wrote:
It's for "kate" and "kwrite" :-)
When we are at LinuxCNC, could you try out the
new syntax highlighting
for gcode? It's included in the latest psb builds.
Nik
For what editor? Where should I see it IOW. Certainly not gedit as it has
an incurable tendency to move arbitrary blocks of code around in the
file so its been nuked from all of my systems. gedit is a very capable
editor, capable of wrecking 2 years work. I've sorted that pan of
scrambled eggs, 1000 LOC, several times too many, even resorting to
getting last nights backup out to recover. I now use nano or geany if a gui is available, which
so far has Just
Worked(TM). It does do some C style code checking, matching brackets etc
type stuff, but I've found highlighting words only usefull by the spell
checkers.
geany was what I used ill I found FernVs gcode.xml for kate. I think the highlighting for
kate works way better than in geany. The only bug I found is indirect o-calls are marked
as syntax error (e.g.: o[#1] is displayed red underlined).
As for LCNC, I wish the highliteing of the line being
processed in it
lower code display wasn't greyed out as it is now, but displayed in bold
text. Trying to read the greyed out text is getting difficult with my
cataracts thrown in.
perhaps you could do something about that?
I think that would be possible, but axis is written python and my python knowledge is
still in a book on the shelf ..
And we are off-topic, again.
:-)