Comment 26 for bug 156201

Revision history for this message
Vincent Gerris (vgerris) wrote : Re: [Bug 156201] Re: gedit handles opening big files badly

Nano is not a gui desktop editor. Besides that vim is superior to nano in
my opinion. A viable alternative would be an open source editor like Atom,
but it can be useful to have a lightweight simple editor that doesn't blow
up with a big file and is installed by default.

On Wed, Jan 23, 2019, 21:45 madbiologist <<email address hidden> wrote:

> This needs to be fixed. In the meantime, try using nano. Unfortunately
> nano doesn't have syntax highlighting.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/156201
>
> Title:
> gedit handles opening big files badly
>
> Status in gedit:
> Confirmed
> Status in gedit package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: gedit
>
> Opening big text files (400 MB, 750 MB) in gedit is bad
> - from a usability standpoint
> -> There's no progress bar or cancel button for the action, and the
> load takes a long time.
> - from a system standpoint:
> -> In earlier versions, gedit would take so much memory until the
> system swapped all other applications to disk, and the system became
> unusable.
> -> Since Ubuntu 9.04 Beta, gedit crashes without a GUI message, but
> the message "failed to allocate <X> bytes" in the console.
>
>
>
> Original description:
> I just opened a 400 MB text file (mbox mail file) in gedit, and it my
> system has now been unresponsive for minutes. Other editors can open large
> files without a problem. Also, there's no progress bar or cancel button
> that would make it easy to see how long gedit is loading the file or to
> cancel the load.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions
>