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

Unable to save changes to newly duplicated file that is immediately moved to another folder. #5770

Closed
Ephron-WL opened this issue Jul 1, 2023 · 1 comment

Comments

@Ephron-WL
Copy link

Ephron-WL commented Jul 1, 2023

Describe the bug
After duplicating and optionally moving a file within the File view before saving changes to the file leads to an inability to save the file and a cycle of save and save file dialog prompts.

To Reproduce

  1. In the Files view right click and select Duplicate
  2. Rename the file.
  3. Edit the file. Do not save.
  4. Move the document to another folder.
  5. Click the document in the new folder.
  6. Prompted to save or discard. Discard causes the changes to be lost (expected). Click Save causes the bug.
  7. Click save displays the save file dialog, which should not be required since Typora knows the location of the file and a new file doesn't need to be defined. I click Cancel.
  8. Click the file name again. repeat step 7 in a loop.

Alternative steps causing a similar problem

  1. In the Files view right click and select Duplicate
  2. Delete the file just created through duplication
  3. Click a file. This causes the Save/Discard dialog box and loop if Save is clicked. Why? No changes had occurred to any document in Typora. Only files are managed on the file system.

Expected behavior
If a click Save then the file should just save to the current location, which is correctly reflected in the File view.

Desktop (please complete the following information):
Windows 10

Typora Version
1.6.7

@abnerlee
Copy link
Contributor

abnerlee commented Nov 7, 2023

I cannot reproduce this in version 1.7.6

If it still happens in v1.7.6 could you attach a screencast for us to reproduce this bug?

@abnerlee abnerlee closed this as completed Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants