-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with leftover backing directory #47
Comments
I can not reproduce this, you are seeing this behavior in what version of SiriKali. |
All, up to 1.3.1.
…On Nov 5, 2017 11:52 AM, "mhogomchungu" ***@***.***> wrote:
I can not reproduce this, you are seeing this behavior in what version of
SiriKali.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAif1fSwGDULsNKS5Q-YpnfRASwLQCLZks5szefhgaJpZM4QSb1v>
.
|
Neither can I, reliably. I'll leave this here and expand if it happens again. |
Best I can figure, this is actually a different thing. If the directory is already open in a File window on the desktop, another isn't opened, and it isn't brought to the front. So, not a Sirikali bug, though it would be convenient if the window were promoted somehow. |
If there is a problem during a session, the backing dir in ~/.Sirikali may remain. On subsequent mounts, !/.Sirikali/
(2) is created and used. In this situation, the "Open Folder" operation does not work.The text was updated successfully, but these errors were encountered: