RedNotebook shouldn't load backup files as journal files

Bug #705260 reported by Dom Delimar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RedNotebook
Fix Released
Medium
Jendrik Seipp

Bug Description

I don't know if there's some convention about linux *~ backup files but to me at least it was unexpected behavior when I edited my journal file outside RedNotebook (which automatically, based on my preferences, created a backup of the that file with "~" suffix) and started RedNotebook only to find my changes were not applied.
Log explained why this was:

INFO Opening journal at ~/.rednotebook/data
DEBUG Starting to load files in dir "~/.rednotebook/data"
DEBUG Start loading file "~/.rednotebook/data/2011-01.txt"
DEBUG Finished loading file "~/.rednotebook/data/2011-01.txt"
DEBUG Start loading file "~/.rednotebook/data/2011-01.txt~"
DEBUG Finished loading file "~/.rednotebook/data/2011-01.txt~"
DEBUG Finished loading files in dir "~/.rednotebook/data"

So RN read both files and in this case gave higher priority to my backup file.

I don't know if editing journal files directly is supported and if this behavior could thus be considered a simple wishlist and not a bug, but the reason I edited the file outside RN was because I accidentally put a whole lot of data on the wrong date and felt it would be *a lot* easier to just change the date info in the journal file rather than go through tedious copy-pasting. And by storing journal data in plain text you sure made it appealing and easy to do such edits and thanks for that :) - and this certainly isn't even a big bug since all one has to do is remove backup files and everything goes back to normal (some might even have their systems setup in a way they will never hit this bug) but it sure seems to me it wouldn't hurt a bit if RN ignored certain files, backup ones for starters.

And let me just add this is a lovely program you've created. Just started using it and I already can't see myself not using it from now on. Thank you! :)

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

Thanks for the report. This is indeed a bug. It has been fixed in trunk.

Changed in rednotebook:
status: New → Fix Committed
importance: Undecided → Medium
assignee: nobody → Jendrik Seipp (jendrikseipp)
Changed in rednotebook:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.