Closed alexkutsan closed 4 years ago
This usually happens when there was an edit conflict and SN makes a conflicted copy of the note.
Renaming the conflicted copy or deleting it should fix the problem.
Found the conflict, fixed. It works! Would be nice to put it in README.md Thank! The only issue is working with non asci name of the notes. I ca see in ls something like this :
''$'\320\220\320\262\320\263\321\203\321\201\321\202'' 2019.txt'
''$'\320\221\321\203\321\205\320\273\320\276'' '$'\320\264\320\273\321\217'' '$'\320\272\320\276\320\272\321\202\320\265\320\273\320\265\320\271''.txt'
''$'\320\221\321\213\321\201\321\202\321\200\321\213\320\265'' '$'\320\270\320\264\320\265\320\270''.txt'
''$'\320\222\320\276\320\277\321\200\320\276\321\201\321\213''.txt'
Should I create issue for that, it this is known one?
I'll explain how to fix the problem in the error message. Added in e8d3f53.
Yes, please create an issue for non-ascii filenames. I'll close this one.
Looks like an issue with non ASCII names was my local bash issue. It reproduces not only on standartnotes-fs dir. Thanks!
Hello, faced with an issue :
what can you suggest?