Skip to content
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

Workspaces not being saved properly #92

Open
tprotopopescu opened this issue Dec 5, 2022 · 3 comments
Open

Workspaces not being saved properly #92

tprotopopescu opened this issue Dec 5, 2022 · 3 comments

Comments

@tprotopopescu
Copy link

Describe the bug

Sorry, I'm not entirely sure how to describe this... Saving a workspace (Shift+Enter) uses some random block of text from a currently open file (but the text is not selected or in clipboard) as the name of the (or a new?) workspace. After that the workspace selection modal does not work reliably. It displays only some of the previously saved workspaces plus the new 'huge block of text' name, and selecting a different workspace does not work.

After restarting Obsidian the list of workspaces is back to normal, the big block is gone, but changes are not saved.

Saving a workspace using Shift and mouse select works.

To Reproduce
Steps to reproduce the behavior:

  1. Make some changes to a previously created workspace.
  2. Open workspace modal
  3. Select the workspace you were working on.
  4. Click Shift+Enter

Expected behavior

Workspace is saved, and pop up message saying "Workspace saved successfully" is displayed.

Screenshots

Peek 2022-12-05 11-09

Desktop (please complete the following information):

  • OS: Linux, Opensuse 15.4
  • Browser: Firefox 102.5.0
  • Version 0.3.3

Additional context
Add any other context about the problem here.

@jsmorabito
Copy link
Collaborator

hi @tprotopopescu is this working for you with the latest fix?

@tprotopopescu
Copy link
Author

Hi, no unfortunately not. I only got this problem after the latest fix (Patch for Obsidian 1.0.0 - version 0.3.3). I guess since no one else is reporting this issue it is something about my set up.

I've rolled back to 0.3.2 via BRAT and I use this fix (#86 (comment)).

@tim-hilde
Copy link

I have the same issue and using the mentioned fix solved the problem as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants