|
|
Post by TheFeDuke on Aug 12, 2015 23:53:30 GMT -5
I developed a readability problem in edit since the update that corrected the FM display problem that left the last file acted on in the next page scrolled. Two bytes are displayed at the end of the data of some lines in Edit. I discovered that is was not arbitrary but occurred after scrolling to a relatively short line in the same position on the second page as a longer line in the previous page. [Pg Dn] and [Pg Up] and the two bytes cleared if the next page contains white space in that position or are replaced with two bytes from that position on the third page.
The data is fine, but the display is very confusing. The [End] key positions to the beginning of the garbage, which reacts strangely to deletion and over-typing. I edit mostly .bat files using colorization. Perhaps I am missing some setting that was sensitized in that update.
Your product is wonderful. All of my old tricks work great! Waxing nostalgic, I worked at 243 Consumers' Road when it opened in the 70's.
Regards,
|
|
|
|
Post by George on Aug 13, 2015 11:21:24 GMT -5
thefeduke: Robert's guess sounds good, a colorize problem. Try HILITE AUTO OFF and if that corrects the display, then yes, we'd love to have the edit file and your BAT.AUTO file.
I worked at Consumers Rd. from the mid 90's. I retired in 2002, but my last few years were almost totally work at home. Thank heavens as I live in Burlington and the drive to Consumers was getting awful, even leaving for work before 6:00 AM. Glad to be out of THAT rat-race.
George
|
|
|
|
Post by TheFeDuke on Aug 14, 2015 2:00:29 GMT -5
From SPFLite.ver: 8.2.5179 EXEHILITE AUTO OFF made the displayed text grey and removed the two bytes. Interestingly enough they are also removed by minimizing and restoring the window and by covering it with another window and popping it to the foreground again. I have attached bat.AUTO and a dull sample file called overbyte.bat, if I understood how to use the forum attachment tool. If nothing else, I now have a couple of workarounds. Environment: I started with SPFLite about two years ago on a reclaimed blue screen of death XP system and then used it on a refurbished Windows 7 system and a flash drive which I did not (as I learned later) set up properly until recently, by which time I was on Windows 10. Regards, Attachments:bat.AUTO (2.31 KB)
OverBite.bat (2.05 KB)
|
|
|
|
Post by George on Aug 14, 2015 11:36:24 GMT -5
thefeduke: Super, your sample files demo the problem nicely. Now to go off and stomp on it.
George
|
|
|
|
Post by TheFeDuke on Aug 14, 2015 12:44:23 GMT -5
Thanks, gentlepeople. Just to put it into perspective, very low priority on my part. I am OK with the workarounds for now, so do what you do in due course or in case this is the tip of some iceberg that might affect others.
Social: Burlington to North York. I was always lucky enough to live east of work. no solar glare from Pickering.
|
|
|
|
Post by George on Aug 14, 2015 13:37:41 GMT -5
thefeduke: Found and corrected it. But the trigger to reaching the actual buggy code is caused because those last few lines in your file containing an unclosed quoted string, which exposed the error.
PATH=%'savedPATH%
As to solar glare, I used to come across the Gardiner and up the Parkway, and at a certain time of year coming up and over the Humber bridge put the rising sun as squarely in your eye as possible, there was simply no way to avoid it. Made for a couple hundred yards of driving that were REAL fun.
George
|
|
|
|
Post by TheFeDuke on Aug 15, 2015 1:32:53 GMT -5
Thank you, George.
So it is an interesting coincidence that I once affected to use a ' to begin some of my file and environmental variable names for convenience in collating order and that I could use a "set '" command to check on things. There is no unbalanced quote in either " Set 'var=String " or " Echo.%'var% ", but I can see how that could come up when looking at such code.
Once again, My compliments on your product and responsiveness.
|
|
|
|
Post by George on Aug 15, 2015 10:51:20 GMT -5
thefeduke: Not sure how you can say there's no unbalanced quotes, there's an opening ' mark and no closing one. Or are you assuming 'quotes' only means double quotes " (CHR$(34)). Remember SPFLite color parsing is language 'blind'. It neither knows nor cares whether the text is a BAT file, an ASM file, C, Rexx, Basic. The different AUTO files provide different keywords and coloring settings, but there is never anything happening based on the syntax rules for a particular language.
George
|
|
|
|
Post by TheFeDuke on Aug 15, 2015 17:53:01 GMT -5
Hi Folks.
It's all good. Language blind is good. I was just explaining why it occurred. I'll go back to figuring out how to colorize out the end of some language specific end of comment situations. You probable already have the features that I just need to define.
Please note that I balanced the quotes in the above paragraph. Cheers!
|
|
|
|
Post by George on Aug 16, 2015 11:39:02 GMT -5
thefeduke: Robert: I wasn't trying to excuse the creation of the garbage characters, that's a bug, plain and simple, and I've corrected it.
I was explaining that the bug only showed up because of the unclosed quote. There's logic in there to handle unclosed quotes, but it got muddled by the EOL logic for ESCAPECHR when not followed by a character.
Unclosed quotes treat the whole rest of the line as the quoted string.
George
|
|
