> At what directory is the path undefined? In other words, where does the > path stop existing?
Interesting enough, but bash seems to be alright with those extra slashes — it still can access the needed directory and create file there if I do something like zoresvit@shekel:~$ touch .local/share///sage/temp//mytemp.txt zoresvit@shekel:~$ ls -al .local/share///sage/temp/// | grep mytemp.txt -rw-r--r-- 1 zoresvit zoresvit 0 Jun 4 16:38 mytemp.txt Nevermind, I found out that the problem is in my own script — due to incorrect call of CryptoMiniSat I've tried to read the temp file which hasn't been written before which caused the error. So sorry for disturbance. However it was a surprise for me that extra slashes in the path are alright. -- Sincerely, Ruslan Kiyanchuk -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
