- Do you know a text editor that can open large text files? "Large" means around 100 megs of data. ^_^;; I use wordpad, but it becomes very slow.
Did you try notepad? 
NotTheCommonDose wrote:
Did you try notepad?
Only on Windows 2000, Windows XP, and Windows Vista does Notepad work with huge text files. Notepad of Windows 95, Windows 98, and Windows Millennium Edition is limited to 32 KiB or so.
I use Notepad++ as my primary text editor. Have you already tried that one?
Never knew it existed.
NotTheCommonDose wrote:
Did you try notepad?
Did YOU try Notepad with a file 85MB large?
never needed to.
I use textpad and it's fine.
EditPadLite can open any size file I believe. Might want to double check first though.
It takes a long time for any computer to word-wrap 100 MB of text. What is in this large text file, and why must it be edited as one file?
Probably a CPU emulator tracelog.
Wordwrapping can be disabled.
Wordwrapping can be disabled.
use HxD, under "View->Visible Columns" Set to "text" and then select "View->Adapt to window width", it won't handle newline but you can edit very large files 
hap wrote:
Probably a CPU emulator tracelog.
Wordwrapping can be disabled.
Wordwrapping can be disabled.
Bingo.
Well, the generated log looks much like what Nintendulator does, except it has no flags information. Just for having a comparision about the text format and file size.
Why do you need to open a "huge" text file anyway?
NotTheCommonDose wrote:
Why do you need to open a "huge" text file anyway?
With the CPU executing hundreds of thousands of instructions per second, you can imagine that a log can get pretty large very quickly. He probably needs to verity a certain emulation behavior in that log.
NotTheCommonDose wrote:
Why do you need to open a "huge" text file anyway?
- Why? That's odd, but fine. I need to read trace logs of CPU/APU, general NES emulation. Wordpad can edit those big files, but it's slow when the size is greater than 30 megs.
tokumaru wrote:
With the CPU executing hundreds of thousands of instructions per second, you can imagine that a log can get pretty large very quickly. He probably needs to verity a certain emulation behavior in that log.
Then wouldn't it be more efficient to make some sort of program in Perl or something that can diff the logs between the new emulator and some reference emulator?
The diff isn't enough. I would need a full backtrace depending of the problem.