Closed
Bug 27799
Opened 26 years ago
Closed 26 years ago
rename of local mail folder renames it in the ui, but not on disk
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M14
People
(Reporter: sspitzer, Assigned: sspitzer)
Details
(Whiteboard: [PDT+])
the problem is caused by the api change of Rename().
Rename(const char *) got changed to Rename(const PRUnichar *)
nsMsgLocalMailFolder::Rename() was not updated
so when we call rename, we fall to nsMsgFolder::Rename()
I've got the fix, and checking in now.
| Assignee | ||
Comment 1•26 years ago
|
||
marking m14, beta1, accepting.
| Assignee | ||
Comment 2•26 years ago
|
||
fixed.
Comment 3•26 years ago
|
||
whoops, thanks Seth.
| Assignee | ||
Comment 4•26 years ago
|
||
marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
2000-02-16-08m14 mozilla build on linux rh6.0: renames both the folder file and
its .msf file upon OK to the rename dialog, OK through exit.
2000-02-16-08m14 commercial build on mac OS 9.0: renames both the folder file
and its .msf file upon OK to the renmae dialog, OK through exit.
2000-02-16-08m14 mozilla build on NT 4.0: renames only the folder file and not
the .msf file. Builds a new .msf file next time folder opened.
Seth, David: OK to mark verified given the behavior of win32 (not renaming .msf
but creating a new one)?
For win32 behavior. This would leave around useless files on people's Win32
systems. I don't think that's good behavior.
Whiteboard: [PDT+] → [PDT+] feb16: verified, but need info about Win32 result
| Assignee | ||
Comment 7•26 years ago
|
||
that's weird that is only win32.
can you open up a new bug on that on me?
Marking this bug verified.
Carrying forward win32 issue of creating new .msf file instead of renaming and
using old one to bug #28225
Status: RESOLVED → VERIFIED
Whiteboard: [PDT+] feb16: verified, but need info about Win32 result → [PDT+]
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•