4 ms·
The size limitation seems like a killer, and rather hard to fix. In my main editor, opening a 100mb file is not unheard of.
by wglb 13y ago
The size limitation seems like a killer, and rather hard to fix. In my main editor, opening a 100mb file is not unheard of.
- 1qaz2wsx3edc 13y agoSure, it's not unheard of, but I think for most users, for most of the time, it's not a typical thing to happen. You instead work on a tree of small files. The odd time, I need to edit a huge file like a database dump, I'll pop open vim or nano/pico, but that isn't where I spend the majority of my time developing. I think the trade-offs are worth it, and I think it's also something that can be improved in the future. I don't view it as a critical feature.
- subsection1h 13y ago> You instead work on a tree of small files. I open all the files in the project(s) I'm working on. I currently have thousands of files open in Emacs. My Org mode wiki alone contains more than 2,000 files that remain permanently open.
- barrkel 13y agoAt my previous job, two of the most important C files exceeded 500k - 20k lines in one, 25k lines in the other (expression parser and declaration parser, respectively). Emacs doesn't do so well on those files either, for reasons I don't quite understand. C-Home (M-<) from the end of the file took 3+ seconds on an 3.8GHz i7 machine, yet the command those keys are bound to - beginning-of-buffer - was instantaneous, as was M-g g 1 (go to line 1).
- rjzzleep 13y agoi would assume it's the syntax highlighting. emacs uses gap buffers for it's data store. i faintly remember that it regexes can be slow in it. but maybe my memory is failing me on this one http://scienceblogs.com/goodmath/2009/02/18/gap-buffers-or-why-bother-with-1/ http://scienceblogs.com/goodmath/2009/02/18/gap-buffers-or-w...
- xixixao 13y agoI really hope those files are well structured, but it baffles me that no one would think about splitting them up...
- barrkel 13y agoMultiple files would mostly just make them more fiddly to work with, juggling all these buffers. In my experience, the modern fashion for tiny source files is not intrinsically better, especially when all the code is related to a functional area (and is mutually recursive, in a compiler's parser). You'd still rely on search to navigate, and whether it's in the same file or a different file is just an IDE / editor detail. If anything, fewer source code files meant you always knew which file to switch to to find any given function, which you could in turn find with an incremental search.
- aryastark 13y agoWhat are you editing a 100 meg file for? Genuinely curious. I regularly work with 2GB+ files, but I don't need to edit them. I use "less". If I really needed to make a change, I'd use some combination of sed/awk most likely.
- wglb 13y agoOn rare occasion a daily log file.
- babby 13y agoI tried opening an 98MB SQL dump the other day to restore some wiped data. Sublime choked incredibly hard where the editor was unusable and turning off syntax highlighting did nothing. I eventually just used something else. Really would have thought Sublime, being native, could handle a measly 100mb.