dail8859 / NotepadNext

A cross-platform, reimplementation of Notepad++
GNU General Public License v3.0
9.26k stars 553 forks source link

Erro after force macOS shutdown #650

Open brunos0 opened 1 month ago

brunos0 commented 1 month ago

Operating System and Version

Macos 14.7

Distribution

Dmg file

Description

I'm using 0.8 version on my macos 14.7. Yesterday, after my job o force my macos tô shutdown and when i tried to use notepad next i got the erro from image.

Sorry, but i can send more information because my macos was a security policies that Prevent me to copy more data that i send here.

By the way there some way to copy temporário (nota saved file), to backup my data? Maybe remove the app and ALL data could bem fiz my problem.

Kind regards.

Steps to Reproduce

  1. Install notepad 0.8 on macos 14.7
  2. Create some filés on It
  3. While app is openned, try to shutdown the macos without close notepad next

Additional Details

e.g. screenshots, logs, etc IMG_20241018_093321681

brunos0 commented 1 month ago

I found a solution.

On macos ALL unsaved files was temporarily keeps at /Users/Xxxxxx/Library/Application Support/Notepad next/session/

I copied ALL filés tô another folder and deleted ALL files on that source folder. Then i was able to open the Application without error.

Now Just need tô open ALL backup filés and get previous data.

I Hope that this helps someone tô Prevent loose yours filés after a force shutdown.

bsdooby commented 1 month ago

Great you found a solution for your issue. Maybe mine is related to yours (?) ; see #649

dail8859 commented 1 month ago

On macos ALL unsaved files was temporarily keeps at /Users/Xxxxxx/Library/Application Support/Notepad next/session/

Yes the temporary files are saved to disk. I cannot say for sure why it was giving the error but there was most likely something corrupted in the ini file that saves all of Notepad Next's settings (including information about those session files). If you do have this happen again I would be very interested in looking into the ini file more to make sure there is plenty of error catching to prevent this kind of error.