[ jEdit-devel ] [ jedit-Bugs-1777803 ] Bogus warnings with new installation

Bugs item #1777803, was opened at 2007-08-20 11:23
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1777803&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: Charles Kennedy (charles_kennedy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bogus warnings with new installation

Initial Comment:
With a new installation of jedit (4.3pre10), the following warning is displayed on the console:

2:08:43 PM [warning] IOUtilities: Error moving file: java.io.FileNotFoundException: /home/ckennedy/.jedit/activity.log (No such file or directory) : /home/ckennedy/.jedit/activity.log (No such file or directory)

Additionally, on exit similar warnings are displayed for the following files:  history, recent.xml, killring.xml, and properties.

These warnings are technically correct, but we're being warned about an expected and normal condition--which is confusing.

Since these files are created during the first usage, the warnings are not displayed the second time around.


----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2007-10-30 19:20

Message:
Logged In: YES 
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (vanza)
Date: 2007-10-15 20:39

Message:
Logged In: YES 
user_id=75113
Originator: NO

I don't think this is something that needs fixing, especially since the
code that prints the exception is generic and ignoring the error just in
certain cases would cause unneeded code churn.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1777803&group_id=588