After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 605978 - problem at presenting big text files
problem at presenting big text files
Status: RESOLVED DUPLICATE of bug 127731
Product: gedit
Classification: Applications
Component: general
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-03 20:19 UTC by chn.schuster
Modified: 2013-11-06 19:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
My program, the source code from it and the problem-making-file (384.58 KB, application/rar)
2010-01-03 20:19 UTC, chn.schuster 		Details

Description chn.schuster 2010-01-03 20:19:25 UTC 
Created attachment 150754 [details]
My program, the source code from it and the problem-making-file

When I tried my program for prime numbers, I notized that gedit presents one line upon the other. That just happens with very big files, my file had 1.5 MB. When I tried to open the file with "vi" or with "less", there wasn't a problem so I think the problem is gedit and not the file althougt littler files of my program worked fine.
 
I send you the file and my program in the attachment if the problem is there.

BTW: I really like gedit, you all do a great job
Comment 1 Ricardo Varas 2013-11-05 23:03:21 UTC 
I think the problem could be related to how Gedit handles columns.
For testing purposes, I modified your output file and instead of storing the prime numbers in a long line separated by the "," char, I replaced your "," by a "\n" so Gedit uses one line per number. In this way, the file is opened quickly and as expected.

Gedit info:
Name        : gedit
Arch        : i686
Epoch       : 2
Version     : 3.10.1
Release     : 1.fc20
Comment 2 Sébastien Wilmet 2013-11-06 19:28:24 UTC 

*** This bug has been marked as a duplicate of bug 127731 ***