History of a terminal window

Question

I've done this successfully in the past, but at the moment I can't figure out how.
The issue is this: I've using a do script find routine that generates many thousands of files. If I redirect the output to a file in the script bundle, I get an incomplete listing. Previously, I was able to get a complete listing by getting the history of the window (which I've identified via "windows of app "terminal"). The history property of the window is defined as "the contents of the entire scrolling buffer of the window."
Since the find routine was initiated in a fresh shell, the history should be what I want, nothing more, nothing less -- and, previously, that's what I got. But now I'm blanking on exactly how I did that. If, in terminal tell block, I use "set H_ to history of (window id), I get only the initial find command.
Better would be a way of having the entire history of the window redirected in the first place.
(The solution well may dawn on me the instant I post this. The solution probably exists in some draft script on my computer, but at the moment I can't find it.)

Answer 1

Thanks for the comment, but, that doesn't seem to fit with what was happening:
• When I first encountered this, I was redirecting the output to a file, with the intention or reading that file.
• But what was in the file was the end of the output I expected.
• And I was using the "busy of Terminal window" approach (which we discussed at length recently) to stall the AS appropriately. Although I didn't see any error in the code, rewriting it has solved the problem, and I'm content (for now) to let sleeping dogs lie.
I like to use "do shell script," as the whole creating files and reading them routine can be avoided. But while "do shell script" seems great for short terminal procedures, for longer ones I seem constantly to be running into problems or annoyances. For Instance:
a do shell script "find" routine I was trying to use repeatedly stalled on a "permission denied" error. When I used "with administrator privileges" (requiring a password) to get past the error, later a second error stalled execution and I wasn't able to figure out the nature of the error (not that I tried very hard).
BUT WITH "DO SCRIPT" the permission error was reported but didn't stall the Terminal execution (requiring no password) AND _the second error didn't show up at all_. These differences persisted
and will still be present if I run both approaches. I know this difference has to do with how "do shell script" and "do script" handle error messages but, for now, I want hide my head in the sand and not see the error in the redirect file (or use a password to get past it).
As to "History," I've also looked at "Content," and I concluded that if everything works properly (as I thought it once did), "set H_ to history of (properly referenced Terminal window)" was an AS command that would avoid the need to redirect and also avoid the hassle of reading the file. I should look at that again, now that things seem to be working properly. I located the script that I had written previously, and that is the command I used, and I think the result was what otherwise I might redirect to a file -- so it would be a time and code saver if it was indeed returning the entire result of the Terminal command!