Page 3 of 3
Re: Text string bug
Posted: Wed Jan 12, 2022 3:03 pm
by dunbarx
When I issue a command which results in multi-line output perhaps better described as multi-screen output, any output after the --More-- prompt is highlighted.
The only method I can find to get it back to normal white text on black background is to use the ? character the device syntax is similar to a cisco syntax.
Is this another topic?
It does not read like spam.
Craig
Re: Text string bug
Posted: Wed Jan 12, 2022 3:05 pm
by SparkOut
But it is. Or a placeholder for a spamlink.
Re: Text string bug
Posted: Wed Jan 12, 2022 3:15 pm
by Klaus
WAS a placeholder for spam links!
Re: Text string bug
Posted: Wed Jan 12, 2022 3:16 pm
by dunbarx
Klaus is on the case.
Craig
Re: Text string bug
Posted: Wed Jan 12, 2022 3:24 pm
by Klaus
You BET!
Re: Text string bug
Posted: Tue Feb 01, 2022 9:53 pm
by FourthWorld
LCMark wrote: Thu Dec 23, 2021 8:16 pm
The problem comes with finding similarly simple syntax for relational operators - <, >, <=, >= - although I guess the following aren't too unpleasant:
Code: Select all
put "20" < string "3" -- true
put "20" < number 3 -- false
Optional inline type declarations like that would seem a great solution.
I much prefer it over a system property option like "the compareNumeric", which would be more cumbersome in many ways.
Re: Text string bug
Posted: Tue Feb 01, 2022 10:49 pm
by dunbarx
Richard.
I think this is a good enhancement. The LC parser does a very good job at not needing this, but of course not absolutely everywhere. "String" is already a reserved keyword, though. "Number" is still open...
Craig
Re: Text string bug
Posted: Wed Feb 02, 2022 8:20 am
by SparkOut
I'm not a huge fan of other languages tendency to duplicate operators for different purposes, but perhaps a "<" means compare as is now the case and "<<" means compare "strictly".
Meh, I am not a fan already.