Post by Martin Paris on Oct 6, 2013 1:51:21 GMT -5
George,
I was working on a large text file. The file is 170MB.
The file has about 2.6 million records, variable length, longest is 162 characters. Most of them are shorter.
I had excluded about 550.000 lines with the eXclude command.
Then I made a new line with I and entered a character in column 131.
Then I moved that line in overlay mode on the excluded lines.
It seems it did all the overlays, but with the error.
Later in the same file, same session, I excluded another 390718 lines and created a new line etc.
The see if things would change I used a C line command with overlay on the excluded lines.
No error. I then had to delete the C line, that's why I prefer to use Move Overlay.
I had to also do this with another set of lines, now the remainder which was 1.701.550 lines.
I saved the file after eXcludig, but before the Copy Overlay command. The file has now
grown to 237MB because of the all shorter lines now having a character in column 131.....
(I really like the niggles forum topic!)
And there it is again, the error with the loop. But now twice. Could it be a false alarm?
But it did the job, it succesfully overlayed the 1.7m lines.
Just to be on safe side, this is not a critical review, I really like the editor!
It is only to keep you from going out too much, it is better to fix issues :-).
I am running 7.0.3217.
Kind Regards, Martin
BTW1. Your pop-up message says that a copy of the on screen data is somewhere.
But it isn't, it will be there once you press OK :-).
It is a very cool feature to report like that, you only may want to change the text
so that is says it will be saved when you press OK or something like that.
BTW2. Could you resize your linenumbers to accomodate for having more than 999.999 lines?
Somehow it only shows the last 6 six digits of the actual number of lines, this is confusing.
BTW3. First Crash report.
SPFLite has detected an internal loop
Last Interactions were:
KB Primitive: ENTER
Line Cmnd: M
Primary Cmnd: x 'b' 1 all
Module Back Trace:
06 | sOverlayTextDel
05 | lCmdMM
04 | lCtlCommands
03 | krAttention
02 | kBetaProcess
01 | kAlphaProcess
00 | DlgCallBackUser
Note: A copy of this message is in: D:\Users\User\Documents\SPFLite\SPFLiteCrash.txt
Select OK, to ignore loop and continue execution, or
Cancel to terminate the program
BTW4. Below the third crash report, the second got overwritten. Maybe an idea to add a timestamp in the name?
SPFLite has detected an internal loop
Last Interactions were:
KB Primitive: ENTER
Line Cmnd: C
Primary Cmnd: save
Module Back Trace:
06 | sOverlayText
05 | lCmdCC
04 | lCtlCommands
03 | krAttention
02 | kBetaProcess
01 | kAlphaProcess
00 | DlgCallBackUser
Note: A copy of this message is in: D:\Users\User\Documents\SPFLite\SPFLiteCrash.txt
Select OK, to ignore loop and continue execution, or
Cancel to terminate the program
I was working on a large text file. The file is 170MB.
The file has about 2.6 million records, variable length, longest is 162 characters. Most of them are shorter.
I had excluded about 550.000 lines with the eXclude command.
Then I made a new line with I and entered a character in column 131.
Then I moved that line in overlay mode on the excluded lines.
It seems it did all the overlays, but with the error.
Later in the same file, same session, I excluded another 390718 lines and created a new line etc.
The see if things would change I used a C line command with overlay on the excluded lines.
No error. I then had to delete the C line, that's why I prefer to use Move Overlay.
I had to also do this with another set of lines, now the remainder which was 1.701.550 lines.
I saved the file after eXcludig, but before the Copy Overlay command. The file has now
grown to 237MB because of the all shorter lines now having a character in column 131.....
(I really like the niggles forum topic!)
And there it is again, the error with the loop. But now twice. Could it be a false alarm?
But it did the job, it succesfully overlayed the 1.7m lines.
Just to be on safe side, this is not a critical review, I really like the editor!
It is only to keep you from going out too much, it is better to fix issues :-).
I am running 7.0.3217.
Kind Regards, Martin
BTW1. Your pop-up message says that a copy of the on screen data is somewhere.
But it isn't, it will be there once you press OK :-).
It is a very cool feature to report like that, you only may want to change the text
so that is says it will be saved when you press OK or something like that.
BTW2. Could you resize your linenumbers to accomodate for having more than 999.999 lines?
Somehow it only shows the last 6 six digits of the actual number of lines, this is confusing.
BTW3. First Crash report.
SPFLite has detected an internal loop
Last Interactions were:
KB Primitive: ENTER
Line Cmnd: M
Primary Cmnd: x 'b' 1 all
Module Back Trace:
06 | sOverlayTextDel
05 | lCmdMM
04 | lCtlCommands
03 | krAttention
02 | kBetaProcess
01 | kAlphaProcess
00 | DlgCallBackUser
Note: A copy of this message is in: D:\Users\User\Documents\SPFLite\SPFLiteCrash.txt
Select OK, to ignore loop and continue execution, or
Cancel to terminate the program
BTW4. Below the third crash report, the second got overwritten. Maybe an idea to add a timestamp in the name?
SPFLite has detected an internal loop
Last Interactions were:
KB Primitive: ENTER
Line Cmnd: C
Primary Cmnd: save
Module Back Trace:
06 | sOverlayText
05 | lCmdCC
04 | lCtlCommands
03 | krAttention
02 | kBetaProcess
01 | kAlphaProcess
00 | DlgCallBackUser
Note: A copy of this message is in: D:\Users\User\Documents\SPFLite\SPFLiteCrash.txt
Select OK, to ignore loop and continue execution, or
Cancel to terminate the program
