Why would anyone think it is sensible to provide useful functionality that can only be accessed by closing the application?
When I write Perl scripts I often use gedit to execute the program and capture the output in the editor. Sometimes I want the sequence of output changes preserved, sometimes I don't, but I usually do, so I leave it in the "generate a new file per execution" mode most of the time. But then occasionally I want to clean up and close all the output tabs. Is there a way to do it? Not really. You have to close them one by one, and since gedit thinks they are edited it does the "Are you sure you want to close this" malarky every time. So it turns into a session of click, alt-w, click, alt-w, click, alt-w. And just to make it really exciting, the tab order in gedit, is to be charitable, mildly schizophrenic. Im convinced there is some method to what it does but every time I think I understand what it is gedit does something that doesnt fit, anyway. So on a nearly random basis files that you DO want to keep come to focus, and then have to move the mouse to select a new tab, and half the time you don't notice and close files you do want to keep open. Anyway, this is the kind of GUI software hate that one becomes more or less used to over time. But what really takes the cake is that there is this reasonably useful interface to close/save unsaved files in gedit. But the only way you can access it that I know of (meaning without doing python code and learning gedit object model), is to _close_gedit_. It then pops up a nice useful list of unsaved fails and lets you save them in bulk or ignore them. So the only really convenient way to throw all these files away is close the damn editor. Which of course closes all the files you wanted to keep open. And since gedit only holds 5 files in its "recently used files" list, you just end up seething. hate, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
