https://bugs.documentfoundation.org/show_bug.cgi?id=105057
Justin L <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=10
| |1302
Keywords| |difficultyInteresting,
| |easyHack
--- Comment #4 from Justin L <[email protected]> ---
I think this could fairly easily be implemented by resurrecting bug 89394's
commit 93eefe54f5d6b6092371bad1e86444489d29eee2 and changing it to use:
OUString sSysTempPath;
if( osl::FileBase::getTempDirURL( sSysTempPath ) == osl::FileBase::E_None )
bIsInTempPath = !sSysTempPath.isEmpty() && sURL.startsWith( sSysTempPath );
However, as IT support, I might like the debugging ability to see a recently
edited file in the tmp folder that a user claims they worked on and is now
lost. If you see that they only worked on a temporary copy, then it isn't a
surprise that it is lost. [But that scenario is less of an issue now, since
saving doesn't recommend the tmp folder since LO 5.4's tdf#80807 guisaveas:
never recommend system's tempdir.]
So there are some pros and cons in implementing this. Someone will probably
complain if this bug report is fixed (since I had complaints about bug 80807
from someone who liked repeatedly saving to /tmp/). Regardless, I'll mark this
as an EasyHack. Make sure you read and understand the arguments from bug 89394.
The ideal fix would be a threaded approach as described in bug 101302 - but
that is beyond EasyHack.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
