desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #146351
[Bug 761781] Re: Gedit takes many minutes to start if there are many files in directory
Hello Michael, thank you, perhaps I should be pleased that someone has
responded to my report.
However, frankly my overwhelming reaction is that this is far too
typical of how Ubuntu reports are handled. It goes like this:
* a report is filed.
* nothing is done about it, zip, nada, rien, not even a response.
* FOUR AND A HALF YEARS OF SILENCE
* "Hi, we're looking at your detailed report but we haven't made the slightest attempt to reproduce it"
* 60 days pass
* bug is closed, devs congratulate themselves on closing many bugs
Is this really the best we can do to get the community enthused and
helping one another?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/761781
Title:
Gedit takes many minutes to start if there are many files in directory
Status in gedit package in Ubuntu:
Incomplete
Bug description:
Binary package hint: gedit
Gedit takes forever (many minutes) to start up if there are a lot of
files in the same directory. It also takes a similar time to exit.
I had about 70,000 small text files (each around 1K) in a directory.
Double clicking on one in Nautilus resulted in many minutes before
GEdit appeared. In contrast, other editors work instantly, e.g.
nano, vim. Even Open Office opens any of these files quickly!
Perhaps http://ubuntuforums.org/showthread.php?t=922587&page=2 post #18 has a clue to why there is this horrendous delay.
"I think I know why it takes so long to load: How many files/folders does the directory you are trying to load have? gedit remembers the last directory, and it could be the fact that your last used directory has a lot of files/folders to be read."
It sounds as if GEdit is trying to be too clever, and whatever it's
doing with the last used directory needs to be rethought. Though I
don't think this is the complete explanation, because I believe this
was the first time I'd tried to use GEdit in this directory.
Using Ubuntu 10.10.
gedit:
Installed: 2.30.3-1ubuntu1
Candidate: 2.30.3-1ubuntu1
Version table:
*** 2.30.3-1ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/761781/+subscriptions