4 ms·
I once made the mistake of trying to edit a 50MB SQL file in Sublime Text. It took about 10 minutes to open. Once it had, every edit I made, every line I scroll
by georgerobinson 11y ago
I once made the mistake of trying to edit a 50MB SQL file in Sublime Text. It took about 10 minutes to open. Once it had, every edit I made, every line I scrolled froze Sublime Text for another 2 to 3 minutes. I can only presume Sublime Text reads and renders the entire file at once, re-rendering on each edit, even if your window only shows 100 of the 10,000 lines. I love Sublime Text, however it is just impossible to use for large files. I suppose this is why we have stream editors like sed.
- dagw 11y agoHow long ago was this? I just opened a 40MB SQL file in Sublime Text2 and it took less than 40 seconds to open. Once open, editing and scrolling takes no time at all and searching takes maybe a second or 2. Doing a replace on a sting that appeared in every line took about 90 seconds. I agree the Sublime Text isn't as good as some other editors when it comes to large files, but 50 MB is generally not a problem
- georgerobinson 11y agoThis was about 1 year ago, Sublime Text 2.0.2, same version I run now. I'm waiting on Sublime Text 3 to be released before I upgrade.
- dagw 11y agoI'm also running 2.02 and, as I mentioned, have none of the problems you described.
- josteink 11y agoFunny how "untrendy" editors like Emacs (from the 70s!) handles 50MB files and larger without even raising an eyebrow, while all the "modern" editors seem crippled when asked to to do the same things. I'll stick to what works, thank you.
- deleted 11y ago[deleted]
- kropotkinlives 11y agoOr textpad. I regularly edit 400Mb files in that no problems at all, running macros and all sorts. Shame it is unicode challenged though :(
- xrstf 11y agoSublime Text's performance highly depends on the line length of the loaded files. A 5 MB JSON file as one long line can kill ST, but neatly formatted in 50k lines is no problem. For this reason, I generally use Notepad2 to handle larger text files (5 to 300 MB).
- girvo 11y ago> stream editors > sed Oh. Now I know where the name comes from!
- TimWolla 11y agoIt's also explained on the man page: NAME sed - stream editor for filtering and transforming text
- jbrooksuk 11y agoFWIW the latest dev builds have changed syntax highlighting and the speed improvements can be massive. My suggestion though is to turn of SQL highlighting and disable word wrapping when opening a large file (I do the exact same with SQL and CSV files).
- davidgerard 11y agoThere's a reason I stick to vim, which treats multi-gigabyte files as a supported use case. (My daily use case: McKeithing through bloody huge log files.)
- anonfunction 11y agoMay I ask the meaning and origin of the verb McKeithing?
- davidgerard 11y agoAlternative medicine fake doctor. https://en.wikipedia.org/wiki/Gillian_McKeith#Diagnostic_techniques https://en.wikipedia.org/wiki/Gillian_McKeith#Diagnostic_tec... "the awful poo lady". A phrase for grovelling through log files. Anyone in the UK will understand the term immediately.
- rplnt 11y agoI edited (not once) an assembly for AI that was almost 100MB in size in notepad. Took a few minutes to load, but then worked just fine. That was almost ten years back. I can't comprehend how something today can't open a 2MB file.