Text string bug

If you find an issue in LiveCode but are having difficulty pinning down a reliable recipe or want to sanity-check your findings with others, this is the place.

Please have one thread per issue, and try to summarize the issue concisely in the thread title so others can find related issues here.

Moderator: Klaus

dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10305
Joined: Wed May 06, 2009 2:28 pm

Re: Text string bug

Post by dunbarx » Wed Jan 12, 2022 3:03 pm

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

SparkOut
Posts: 2943
Joined: Sun Sep 23, 2007 4:58 pm

Re: Text string bug

Post by SparkOut » Wed Jan 12, 2022 3:05 pm

But it is. Or a placeholder for a spamlink.

Klaus
Posts: 14177
Joined: Sat Apr 08, 2006 8:41 am
Contact:

Re: Text string bug

Post by Klaus » Wed Jan 12, 2022 3:15 pm

WAS a placeholder for spam links! :D

dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10305
Joined: Wed May 06, 2009 2:28 pm

Re: Text string bug

Post by dunbarx » Wed Jan 12, 2022 3:16 pm

Klaus is on the case.

Craig

Klaus
Posts: 14177
Joined: Sat Apr 08, 2006 8:41 am
Contact:

Re: Text string bug

Post by Klaus » Wed Jan 12, 2022 3:24 pm

You BET! :D

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10043
Joined: Sat Apr 08, 2006 7:05 am
Contact:

Re: Text string bug

Post by FourthWorld » Tue Feb 01, 2022 9:53 pm

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.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn

dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10305
Joined: Wed May 06, 2009 2:28 pm

Re: Text string bug

Post by dunbarx » Tue Feb 01, 2022 10:49 pm

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

SparkOut
Posts: 2943
Joined: Sun Sep 23, 2007 4:58 pm

Re: Text string bug

Post by SparkOut » Wed Feb 02, 2022 8:20 am

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.

Post Reply