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

[BUG] File inaccessible #15069

Open
1 task done
worldor opened this issue Apr 30, 2024 · 5 comments
Open
1 task done

[BUG] File inaccessible #15069

worldor opened this issue Apr 30, 2024 · 5 comments

Comments

@worldor
Copy link

worldor commented Apr 30, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Description of the Issue

Repeatedly shown the following popup:
File inaccessible
Some files from your past session are inaccessible. They can be opened as empty and read-only documents asplaceholders.
Would you like to create those placeholders?
NOTE: Choosing not to create the placeholders or closing them later, your session WILL BEMODIFIED ON EXIT! We suggest you backup your “session.xml" now.

Steps To Reproduce

Repeatedly shown the following popup:
File inaccessible
Some files from your past session are inaccessible. They can be opened as empty and read-only documents asplaceholders.
Would you like to create those placeholders?
NOTE: Choosing not to create the placeholders or closing them later, your session WILL BEMODIFIED ON EXIT! We suggest you backup your “session.xml" now.

Current Behavior

Repeatedly shown the following popup:
File inaccessible
Some files from your past session are inaccessible. They can be opened as empty and read-only documents asplaceholders.
Would you like to create those placeholders?
NOTE: Choosing not to create the placeholders or closing them later, your session WILL BEMODIFIED ON EXIT! We suggest you backup your “session.xml" now.

Expected Behavior

Can you please stop this? Can you find a solution? Can you explain which file is inaccessible and its latest path so that we try to find it? And if it does not exist, I suppose the only option is to close the placeholder as the file is lost?
The current popup does not help to carry out a solution nor its explanatory.

Debug Information

Can you please stop this? Can you find a solution? Can you explain which file is inaccessible and its latest path so that we try to find it? And if it does not exist, I suppose the only option is to close the placeholder as the file is lost?
The current popup does not help to carry out a solution nor its explanatory.

Anything else?

No response

@xomx
Copy link
Contributor

xomx commented Apr 30, 2024

npp-placeholders

@worldor
Copy link
Author

worldor commented May 2, 2024

Thanks. I am also worried if this warning denotes data loss? I mean, I can disable the warning itself but I need to ensure no data is lost whatsoever. I am backing up to the cloud which may be risky for that "inaccessible data" warning.
Maybe an improvement to mirror all the data locally in case something is inaccessible, would be good? Also to retry accessing the data? Maybe Notepad++ starts too fast especially upon reboot and this triggers that warning?

@worldor
Copy link
Author

worldor commented May 3, 2024

npp-placeholders

This does not work or is not applicable. My file named "new 34" does not have any filepath whatsoever.

@xomx
Copy link
Contributor

xomx commented May 3, 2024

@worldor
Seems to me that you are mixing together two different things.


  1. N++ placeholders
  • by checking the Preferences > Backup > "Remember inaccessible files from past session" you ensure that your N++ session opened file list will be intact when you relaunch the N++ app with a N++ session file temporarily inaccessible
  • but the read-only-empty-session-placeholder file-substitute will be opened only for a missing real file, not for a never manually saved "new xxx" N++ tab filebuffer
  • then if the N++ detects that a previously missing session file is available again, it will offer you to reload real data of the relevant file/tab (this behavior depends on another N++ setting in Preferences > MISC. > "File status Auto-Detection" combobox - default is "Enable" (which means for the active N++ tab only))

npp-placeholder-1

npp-placeholder-2

npp-placeholder-3

npp-placeholder-4

More details in: https://npp-user-manual.org/docs/session/#inaccessible-files


  1. auto-backing of the N++ "new xxx" tabs
  • when have checked the Preferences > Backup > "Enable session snapshot and periodic backup", the N++ backup engine handles the automatic storage for any "new xxx" N++ tab data
  • data from such tabs are automatically written to the given location in the "Backup path" edit-field in the form of files named like "new 1@yyyy-mm-dd_hhmmss"
  • these N++ internal file-backups have no placeholder equivalent, so if one closes the N++ and then e.g. delete/rename such a backup-file, after relaunching the N++ the corresponding N++ session tab will be gone forever

npp-backup-for-newxxx

More details in: https://npp-user-manual.org/docs/preferences/#backup

@worldor
Copy link
Author

worldor commented May 5, 2024

Thanks but that's the situation actually, I got the "File Inaccessible" warning for a "new xxx" tab/file.
I do have the session snapshot backup enabled and its path is a cloud path.

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

2 participants