Re: Strange error with 'callup'

["Paul Breeze" dmarc-noreply@xxxxxxxx (Redacted sender "paul.breeze" for DMARC)]

Dear Carl
The answer appears to be that for large files, ASPELL.BAT is not
created. I can run the Aspell command in a command prompt on a large
file and I can run the Aspell command with a DO ... from the command
line but if I run the keyboard command it does not work on a large file.
Ah ... how odd. I have the keyboard command set as ASPLGB. When I
remove the GB (GB is set in reg anyway) it works. ASPLGB also works on
the command line.
So, it works now but there is something odd going on, and the odd
behaviour is reproducible. I have just put ASPLGB back into the
keyboard file and the same thing happens, no spelling of a large file,
but fine with a smaller. Remove GB again, and all is fine. Perhaps we
should leave it at that.
There is something else that I have noticed, here and at other times.
Occasionally when I command "Framename"-helpkey it takes me to the entry
in the index of help frames rather than the helpframe. For example
ASPL-helpkey takes me to the index. ASPELL-helpkey takes me to the
ASPELL frame (with ASPL the next frame, below). It is not a big deal as
a search for ASPL will soon find the frame but I wondered if this is
normal, or if I am doing something wrong.

Best wishes

Paul





On 03/03/2018 21:23, Carl Distefano wrote:
Reply to note from "Paul Breeze" 
(Redacted sender "paul.breeze" for DMARC) Sat, 03 Mar 2018 12:37:39
+0000

Paul,

Maybe this is some built-in Aspell limitation?

Definitely not. I just used frame ASPL to spell-check a 2-MB file, then
I ran aspell.exe from the Windows command line to check a 32-MB file,
and both commands worked flawlessly.

Try this: Frame ASPL creates a batch file named ASPELL.BAT, located in
Editor's directory. Command ASPL against a big file, then run
ASPELL.BAT from a Windows command prompt. You can also try running the
aspell.exe command itself (4th line of ASPELL.BAT). Any difference?