>2017 >text editors still can't open a text file with

>>60776402
You have bigger problems then the text editor if you are regularly working with 100 MB text files

either way I think this is more of a b8 post then you having any interest in discussing text editors so sage

>>60776402
>2017
>100 MB text file for whatsoever reason

JUST

>>60776402
vim loads large files just fine for me

use editpad

>>60776445
>>60776419
>using databases
>not saving everything to text files

>>60776402
>text file with a size of 100 MB
wut

>>60776454
Yeah but u cant close it :(

>>60776402
Hey the easiest solution is to just press alt-f4 :)
Always there to help ya!

>>60776482
>u cant close it
You have to be fucking retarded to not know how to close vim. It even tells you when you try to ^C out of it.

Ran into this problem with a Data dump.

Parse it by chunks and remove irrelevant information.

>>60776402
notepad++ can open pretty big files senpai

>>60776402
What is SlickEdit.

>>60776530
No, it actually can't. I'm not sure what the limit is, but it's well below 100mb and closer to 1mb.

>100 MB without hours of loadind and freezing

Time to throw that Pentium 3 CPU and get a job so you can buy something from this century you fucking freetard.

>>60776402
works fine with vi and nano.

>>60776419
>You have bigger problems
lmao what a cuck mentality
>i can't do this
>YOU DONT NEED IT!!!!

>>60776445
log files can be big sometimes.

>>60776625
>all this anger

Relax anonymous poster, and love your enemies for you can't fight love. Cheers.

>>60776665
tail, grep, etc.?

>>60776498
But..but...but...
Nevermind i am smart enuf to understand how shit works

File: 17553396_1279996008720757_6834375656803886239_n.jpg (50KB, 411x580px) Image search: [Google]

50KB, 411x580px

>>60776402
>tfw 2TB wordlist

use ed or ex

Vim and Emacs do it.
Use a real editor instead of a web browser.

ed or sam can load a terabyte

File: file.png (68KB, 933x519px) Image search: [Google]

68KB, 933x519px

>>60776600
????

>>60776836
why

>>60776937
>134
>"pretty big"

no

>>60777149
>Moving goalposts

File: 0002.gif (18KB, 128x128px) Image search: [Google]

18KB, 128x128px

>>60776402
Did it the other with leafpad. Ten seconds to load. Not too shabby.

https://github.com/jhallen/joes-sandbox/tree/master/editor-perf

Use mcedit, senpai.

>>60777033
hacking of course

>>60777033
Because I didn't see the option to split it into smaller files. Text files compress very well so it shouldn't be too bad after tar and gzip

>>60776402
>>60776643
Most FOSS editors can't do it because most don't use the right data structures and don't account for long lines, including vim.

Unironically use professional text editors like UltraEdit, EmEdit, 101Editor.

>>60779375
Never heard of any of these.
Why are they 'professional' editors?

>>60780363
Because they do it for money.
That is what professional means.
Only plebs use it to descibe 'competent'.

Anyway, the point is that they focus on what's important in text editors: Editing text. And if that's a 50GB SQL file, so be it.

>>60779375
vim does it just fine idiot :^)

>>60776402
>Windows

>>60776643
hes right though

>>60777149
>x can do this
>x can't do 1% of this!
>x can do over this
>no

blame syntax highlighting

>>60780881
that's what beginners beliebe

>>60776402
>what's sublime text

>>60783089
there is a chance it can open 100 mb files, since it isn't based on shit tier technologies and the author manages to do the basic work, aka creating a rendered GUI for it, so there is a chance he's capable of implementing a sufficient rope text structure

So, can it open 5GB and bigger files?

>>60783125
Depends on the system i guess, but there is a benchmarks list on github

>>60783159
This, and it said it can't.
And even the LargeFiles plugin fails in some situation.

That's what you get for using a split-buffer.

>>60783230
>>60783159

Oh, nvm, I thought you were the VIM guy