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

GitError Error 12 #1535

Closed
nth-chile opened this issue May 31, 2023 · 7 comments
Closed

GitError Error 12 #1535

nth-chile opened this issue May 31, 2023 · 7 comments
Assignees
Labels

Comments

@nth-chile
Copy link
Contributor

Description

This alert shows when I do CMD+S. I think I broke git by saving a few times rapidly. Now I get the alert every time I try to save any file.

Screenshot 2023-05-30 at 10 56 18 PM

To Reproduce

This one might be hard to repro. I've never seen it before today. Today I was about to leave my computer, and I was trying to type something and then save and close the app, but I saved the file a few times rapidly. Maybe type a word, save, change a letter, save, change the letter back to what it was, save again?

Expected behavior

No response

FSNotes version

6.3.0

macOS/iOS version

Ventura 13.3.1 (a)

Additional context

No response

@glushchenko
Copy link
Owner

error - 12 is equal to "New files not found"

@glushchenko glushchenko removed the bug label Jun 1, 2023
glushchenko added a commit that referenced this issue Jun 1, 2023
@nth-chile
Copy link
Contributor Author

Is it a bug, or is there something I need to do to fix it on my end?

@glushchenko
Copy link
Owner

It doesn't look like an error, this status means you don't have new files to commit. Maybe the repository is not configured, I don't know.

@nth-chile
Copy link
Contributor Author

I'm not sure if this is the same issue or not. I updated to 6.3.3 today. I just pressed cmd+S on a file a bunch of times really fast, and now any time I try to save, I get this error:

Screenshot 2023-07-15 at 1 25 25 AM

@nth-chile
Copy link
Contributor Author

Oh nevermind, that's just what happens when you try to save but there have been no changes. If I change the file, I can save without getting the error. But I think it's not a common pattern in applications for the "there are no changes to save" alert, so I just wasn't expecting it

@glushchenko
Copy link
Owner

This mean that all files already committed and no new files.

glushchenko added a commit that referenced this issue Jul 23, 2023
@glushchenko
Copy link
Owner

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

No branches or pull requests

2 participants