Bug 123958 - Files saved by Kate should be added to the File - Open Recent menu
Summary: Files saved by Kate should be added to the File - Open Recent menu
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-20 04:05 UTC by Shriramana Sharma
Modified: 2011-06-24 17:03 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shriramana Sharma 2006-03-20 04:05:49 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
OS:                Linux

Bug #85654 says that for KWrite files once saved are included in the Open Recent menu and I confirm that. But certainly in Kate in KDE 3.51 files which are saved are not available from the Open Recent menu.

Steps to Reproduce:
1. Type some text into a blank document in Kate.
2. Save it.
3. Close the document.

Expected behaviour:
I should be able to find the file under File - Open Recent.

Actual Behaviour:
I am NOT able to find the file under File - Open Recent. 

Only a file which has been once *opened* by Kate using File - Open are later available under File - Open Recent. This limitation is counter-intuitive and therefore should be fixed.
Comment 1 Maciej Pilichowski 2006-03-27 15:18:33 UTC
I just add another comment to this one because it is very similar.

Run kate. Open several documents. Make sure that you session settings is set to "open last visited". Close kate. Run kate. All documents should be opened. Close any document. Check "open recent" -- this document is forgotten.
Comment 2 John lanser 2007-08-20 10:48:40 UTC
I can confirm this behaviour still occurs files created in Kate are not added to the recently opened documents list
KDE 3.5.7
opensuse 10.2
Comment 3 Glen Stewart 2008-09-10 03:54:05 UTC
Confirmed to be still a problem with KDE 4.1.1's kate, running Kubuntu Hardy Heron.

This behavior is not consistent with industry-standard (and appreciated) behavior.  I consider it to be a bug.
Comment 4 Kishore 2008-09-11 15:20:35 UTC
This behavior is still present. In fact, kate does not list *any* documents as recent documents 
Comment 5 mario tuling 2008-09-11 15:49:22 UTC
its really a bug, not a wish in my opinion, i hope it is right. so ill change it. i confirm also for 4.1.1.
Comment 6 Andreas Pakulat 2008-09-11 19:15:47 UTC
The initial report means handling newly created-and-saved documents the same way as documents that have been explicitly opened. Thats a new feature and not a bug, thus changing back. I agree it makes quite some sense to have this behaviour.
Comment 7 Burkhard Lück 2008-09-11 22:13:30 UTC
quoting Andreas Pakulat:
"The initial report means handling newly created-and-saved documents the same
way as documents that have been explicitly opened".

I have just check this behaviour in several kde-apps from kde 3 +4 :
kword, kspread, kedit, khexedit, okteta, kolourpaint, kdevelop ...

*All* these apps treat newly created-and-saved documents the same
way as documents that have been explicitly opened.

That makes me believe, this is the default behaviour in kde, and kate/kwrite handle this different and do it the wrong way.

Strange for a desktop environment, that different apps handle the same issue in a different way.
That should definitely be consistent!
Comment 8 Paul van Erk 2009-01-27 09:15:21 UTC
Using openSUSE's upcoming KDE 4.2 and I've been experiencing this _bug_ for quite a while (4.1 as well). Opened or newly created, none of them appear in the recent files list. And other KDE apps do treat it the correct way. Kate has a bug, simple as that. This is not a wish.
Comment 9 doc.evans 2009-01-28 22:02:49 UTC
Yep, this is certainly not the expected behaviour at all. I can't think of a single other application that behaves this way.

And I don't understand what difference is thought to exist between files that have been opened and saved with kate compared to other files.

I haven't been able to find a single scenario in which the "Open Recent" menu contains any recently opened files (except the one that is currently being edited, under some scenarios). In other words, comment #8 is correct. The "Open Recent" menu simply does not work.

FWIW, intrepid 64-bit Kate 3.1.4, KDE 4.1.4 here.

Comment 10 Shriramana Sharma 2009-01-29 11:29:05 UTC
Nearing three years since I reported this bug. Unfortunately I do not know enough coding to fix this myself, but I estimate this is not really a "big" (i.e. hard to fix) bug. Can developers please look into this? I also confirm that this continues with KDE 4.2 (tested on Kubuntu Jaunty).
Comment 11 Andreas Pakulat 2009-01-29 12:07:40 UTC
(In reply to comment #9)
> I haven't been able to find a single scenario in which the "Open Recent" menu
> contains any recently opened files (except the one that is currently being
> edited, under some scenarios). In other words, comment #8 is correct.

No its not, if you use File->Open... to open a file, that file shows up in the "Open Recent" menu. Works just fine here (running KDE from svn), if it doesn't work for you I suggest to file a bugreport with your distribution.
Comment 12 Paul van Erk 2009-01-29 14:48:55 UTC
So multiple distributions have the same bug? I start kate, open a file, it shows in recent, I close the file, it's still in recent, I close kate, I open kate: recent is empty. This is openSUSE Factory 4.2 but it hasn't been working since 4.0. I'll file the bug at opensuse, but perhaps it's just very recently been fixed for 4.2.1 (since you're using SVN)?
Comment 13 Andreas Pakulat 2009-01-29 16:14:13 UTC
(In reply to comment #12)
> So multiple distributions have the same bug?

Its not uncommon for distro's to share patches.

> I start kate, open a file, it
> shows in recent, I close the file, it's still in recent, I close kate, I open
> kate: recent is empty.

Works fine for me.

> This is openSUSE Factory 4.2 but it hasn't been working
> since 4.0. I'll file the bug at opensuse, but perhaps it's just very recently
> been fixed for 4.2.1 (since you're using SVN)?

No changes in kate (the app) between branching 4.2 and current trunk thats running here that could explain such a bug. So this particular error is most probably a bug introduced by distributions.

Comment 14 doc.evans 2009-01-29 17:17:08 UTC
(In reply to comment #12)
> So multiple distributions have the same bug? I start kate, open a file, it
> shows in recent, I close the file, it's still in recent, I close kate, I open
> kate: recent is empty. 

Yep; that's what I see too (in Kubuntu 8.10).

I suppose it's a legitimate argument for developers to say in effect: "program X has different behaviour from every other program in the known universe and we're not going to change it". They are in charge, after all.

But, man, it sure is annoying every time I waste time trying to find recently-edited files (which is several times per day).




Comment 15 Maciej Pilichowski 2009-01-30 22:24:22 UTC
Please keep this open, because:
a) there are many test-cases to check this bug, and just opening a file is not the only one
b) it is possible, but not very likely, that there is one patch shared amongst all the distros
c) there is popular misconception about "recent files" -- unfortunately kate now is partially among the flawed designed apps 

ad.c) recent files should not list active files, because as the name of the entry there are not _current_ files, but recent, if you open 30 files, the menu would be populated with the current files, and "recent files" would be not useful at all (because all recent entries would be removed)
This menu should hold _only_ recently closed files, which are no longer edited (opened) 

For now -- kate does not list opened files and closed ones, on the other hand it list currently edited files.

Andreas, are you sure I should file a bug report about it? For me, it is just duplicating reports, because in fact each report would state the same "please provide correctly working recent files feature". I admit, with Kate and sessions it is not straightforward to do, but anyway, the aim is only one and it is clear. 
Comment 16 Andreas Pakulat 2009-01-31 01:44:51 UTC
(In reply to comment #15)
> Please keep this open, because:

Nobody said this report was going to be closed. But this report is about adding filenames that are being saved to the recent-files list (just as kwrite does). Implementing this is not exactly trivial (I had a quick look) as it needs some knowledge about how katepart works internally (else I would've simply created a patch and posted it).

However, the open recent menu is properly populated _and_ stored to disk _and_ also reloaded on next start here with kate from svn. Hence the only way this could break (the code is really, really easy) is if somebody changes his sources. Thats the part that is now hopefully resolved, but was never part of this report.

> For now -- kate does not list opened files and closed ones, on the other hand
> it list currently edited files.

Kate properly lists the files it has opened in the recently opened files submenu here. At least here and so far it seems nobody who's building from svn has different behaviour.

> Andreas, are you sure I should file a bug report about it? For me, it is just
> duplicating reports,

There's no duplication, this report is about adding files that have been saved under a different name (or new files saved for the first time) should be added to the recent-files menu. If you have any other problem with that menu, thats a separate problem and hence needs a separate report.

Andreas

Comment 17 Maciej Pilichowski 2009-01-31 09:58:52 UTC
Andreas, thank you, the report about "open recent != recently opened" bug can be found here:
https://bugs.kde.org/show_bug.cgi?id=182543
Comment 18 doc.evans 2009-02-02 00:07:55 UTC
(In reply to comment #16)

> 
> > For now -- kate does not list opened files and closed ones, on the other hand
> > it list currently edited files.
> 
> Kate properly lists the files it has opened in the recently opened files
> submenu here. At least here and so far it seems nobody who's building from svn
> has different behaviour.

I have just tested with a completely up-to-date kde4daily VM . The behaviour is no different from that reported for OpenSuse and Kubuntu. This lists itself as Kate 3.2.0 and KDE 4.2.00.

In my daily (hourly, probably) use, I have yet to see anything appear in the Recent Menu other than the file that I am  currently editing.


Comment 19 Andreas Pakulat 2009-02-02 00:25:14 UTC
(In reply to comment #18)
> (In reply to comment #16)
> > > For now -- kate does not list opened files and closed ones, on the other hand
> > > it list currently edited files.
> > 
> > Kate properly lists the files it has opened in the recently opened files
> > submenu here. At least here and so far it seems nobody who's building from svn
> > has different behaviour.
> 
> I have just tested with a completely up-to-date kde4daily VM . The behaviour is
> no different from that reported for OpenSuse and Kubuntu. This lists itself as
> Kate 3.2.0 and KDE 4.2.00.

Well, apparently the list of recently-opened-files is stored in the session, hence anybody using an empty session on kate-startup will always get an empty menu. There's a separate wish for changing that.
 
> In my daily (hourly, probably) use, I have yet to see anything appear in the
> Recent Menu other than the file that I am  currently editing.

Ever closed a file? It'll still be in that menu (unless you also closed kate and use the above empty-session-on-startup option).
Comment 20 doc.evans 2009-02-02 00:47:33 UTC
I'm just a simple user trying to use Kate to edit text files, and to help developers by reporting behaviour that doesn't make any sense to me. I don't understand at least half of what's being said here. In particular, I've never heard of the "empty-session-on-startup" option. 

All I know is that prior to KDE4 there was an Open Recent menu that contained what I expected it to contain (i.e., a list of files that I had recently used; like every other application I use that has a similar menu) and now all it contains is the name of the file I'm currently editing. My behaviour hasn't changed, but that of Kate most definitely has, and not in a helpful way.


Comment 21 Andreas Pakulat 2009-02-02 01:03:30 UTC
(In reply to comment #20)
> I'm just a simple user trying to use Kate to edit text files, and to help
> developers by reporting behaviour that doesn't make any sense to me. I don't
> understand at least half of what's being said here. In particular, I've never
> heard of the "empty-session-on-startup" option. 

Then I suggest to check it out, unfortunately I don't have a kate at hand right now so can't give you a hand as to where you can enable/disable it. But its probably either in the configure kate dialog or the one for configuring sessions.

> All I know is that prior to KDE4 there was an Open Recent menu that contained
> what I expected it to contain (i.e., a list of files that I had recently used;
> like every other application I use that has a similar menu) and now all it
> contains is the name of the file I'm currently editing. My behaviour hasn't
> changed, but that of Kate most definitely has, and not in a helpful way.

Are you saying that after opening two files in the same kate window you still have only one entry? If so I suggest you send a new bugreport, because that would be a bug, though I can't reproduce that here at all.
Comment 22 Kishore 2009-02-02 04:49:14 UTC
(In reply to comment #21)
> (In reply to comment #20)
> > I'm just a simple user trying to use Kate to edit text files, and to help
> > developers by reporting behaviour that doesn't make any sense to me. I don't
> > understand at least half of what's being said here. In particular, I've never
> > heard of the "empty-session-on-startup" option. 
> 
> Then I suggest to check it out, unfortunately I don't have a kate at hand right
> now so can't give you a hand as to where you can enable/disable it. But its
> probably either in the configure kate dialog or the one for configuring
> sessions.
> 
> > All I know is that prior to KDE4 there was an Open Recent menu that contained
> > what I expected it to contain (i.e., a list of files that I had recently used;
> > like every other application I use that has a similar menu) and now all it
> > contains is the name of the file I'm currently editing. My behaviour hasn't
> > changed, but that of Kate most definitely has, and not in a helpful way.
> 
> Are you saying that after opening two files in the same kate window you still
> have only one entry? If so I suggest you send a new bugreport, because that
> would be a bug, though I can't reproduce that here at all.
> 

Thanks for the explanation I now understand how to work around this bug/feature. It is clear that kate is meant for advanced users and kwrite is the general purpose editor!

Here is what you need to do. In kate, go to Settings -> Configure Kate -> Sessions. Here, select "Load last-used session" and "Save session".
Comment 23 doc.evans 2009-02-03 00:38:40 UTC
(In reply to comment #21)

> > All I know is that prior to KDE4 there was an Open Recent menu that contained
> > what I expected it to contain (i.e., a list of files that I had recently used;
> > like every other application I use that has a similar menu) and now all it
> > contains is the name of the file I'm currently editing. My behaviour hasn't
> > changed, but that of Kate most definitely has, and not in a helpful way.
> 
> Are you saying that after opening two files in the same kate window you still
> have only one entry? If so I suggest you send a new bugreport, because that
> would be a bug, though I can't reproduce that here at all.
> 

Not at all. I'm saying the same thing I've been saying all the way along. 
 
In KDE3:

1. edit "q" in kate.
2. Close kate.
3. edit "w" in kate.
4. Look in the Recent menu. "q" is there.

In KDE4:

1. edit "q" in kate.
2. Close kate.
3. edit "w" in kate.
4. Look in the Recent menu. "q" is NOT there.

The KDE3 behaviour matches every other text editor I regularly use. I have never seen any program that behaves like the KDE4 version.

This isn't anything like as hard as you seem to be making it. Nothing about "sessions" or options or multiple files being opened in windows, or anything else. The simple, basic behaviour has changed: the "Open Recent" menu used to list... er... the files that had been opened recently; now it doesn't. To this poor user, that just simply doesn't make sense.






Comment 24 Andreas Pakulat 2009-02-03 11:47:29 UTC
(In reply to comment #23)
> This isn't anything like as hard as you seem to be making it. Nothing about
> "sessions" or options or multiple files being opened in windows, or anything
> else.

Yes it is, because the list of recently opened files is stored in the session. So if you either start with a new session every time kate starts up or if you don't save your session before exiting kate you'll get exactly that behaviour.

Note: I'm not saying this is correct, I'm just explaining what the code currently does and why you're having the problem.

> The simple, basic behaviour has changed: the "Open Recent" menu used to
> list... er... the files that had been opened recently; now it doesn't.

It still does, but with added semantics due to the improved session support in kate/kde4.

Anyway, there's a separate bugreport about moving this list out of the session into the global config, so please add your vote there. This bugreport here is about a different thing.
Comment 25 Andreas Pakulat 2009-02-03 12:19:57 UTC
address bounces due to a stupid spam-checker that wants a confirmation for every mail it receives.
Comment 26 Anders Lund 2009-02-03 16:34:37 UTC
Did I mention before that what we should do (I wrote a patch for it at the Kate developer meeting even, which was never applied due to practical issues) is to make the default session stored in katerc?
Comment 27 doc.evans 2009-02-03 16:34:48 UTC
(In reply to comment #24)

> > The simple, basic behaviour has changed: the "Open Recent" menu used to
> > list... er... the files that had been opened recently; now it doesn't.
> 
> It still does, but with added semantics due to the improved session support in
> kate/kde4.
>

I simply can't respond to that, except to say that I take enormous offense at being called a liar. Goodbye.
Comment 28 Bartemius Crouch 2009-06-04 23:19:46 UTC
Is this bug still "NEW" after more than 3 years?  (I'm talking about the original bug, "files which are saved are not available from the Open Recent menu" just to be clear)

Are there any plans to fix it for the KDE3 Kate?
Are there any plans to fix it for the KDE4 Kate?

Thanks!
(Mandriva, KDE 3.5.9)
Comment 29 Scott 2011-01-10 21:50:56 UTC
I just came here to report this bug... turns out it's been open for nearly 5 years now!! Will this ever be fixed?
Comment 30 Dominik Haumann 2011-01-10 22:42:53 UTC
true, wasn't aware of this. change severity to normal instead of wishlist item.
Comment 31 Christoph Cullmann 2011-06-24 17:03:26 UTC
Git commit 8b94efe87c45d8541061d6347662f12aaf441b0a by Christoph Cullmann.
Committed on 24/06/2011 at 19:02.
Pushed by cullmann into branch 'master'.

add saved files to recent files
BUG: 123958

M  +16   -2    kate/app/kateviewmanager.cpp     
M  +2    -0    kate/app/kateviewmanager.h     
M  +1    -1    part/document/katedocument.cpp     

http://commits.kde.org/kate/8b94efe87c45d8541061d6347662f12aaf441b0a