When one of the directorys begins with a pound, it reads the overall content of the parent directory. When a filename contains a pound it displays unable to open file.
What do you mean with "it reads the overall content of the parent directory." ?
For example for a folder located in my Desktop parent folder : If I prefix a folder by # and I try to read a PDF file located in this folder, it opens all the readable content of the parent folder (the Desktop and it's other child folders.) In my case all .png files were read.
Created attachment 128414 [details] Screenshot
Can't reproduce on Linux. Adding the Windows folks
Edited the subject (pond -> pound sign) to reflect the problem. Perhaps an explicit "#" in the subject would be better? I'd also ask whether the problem is only for a leading # in the file name or can it be anywhere?
Hello, No this behavior occur only with a leading # in the folder name. All my other tests showed that for any other occurrence of # in the path make the file unreadable by Okular (error message).