On 02/24/2016 02:14 PM, John Jason Jordan wrote: > On Wed, 24 Feb 2016 13:32:40 -0800 > David <[email protected]> dijo: > >> On 02/24/2016 01:31 PM, Rich Shepard wrote: >>> On Wed, 24 Feb 2016, Denis Heidtmann wrote: >>> >>>> I just created a file named Desktop in the folder Desktop. >>> >>> Denis, >>> >>> Interesting. I didn't know it could be done. >> >> The directory and file may not be at the same level, but they may be >> nested without issues. > > But I continued to get the same error message even after I renamed the > file. Thus, the file and directory name were different. And Catfish > said that no file with the same name as the folder existed.
Having no experience with Catfish, I can't help you here. Perhaps the filesystem has a phantom memory of a file or directory with the exact name you are trying to create. To clear this, try to umount the partition and run fsck on it. If that isn't possible, you may also consider a 'find' on the directory with the _exact_ name as the target. > Regarding spaces and scripts, I have only a couple very short scripts > that I use, and they do not access files or folders with spaces in > them. Furthermore, I usually use Gnome terminal, which happily > automatically escapes all spaces in files that I copy and paste into > it. I would say that the majority of files that I create have spaces in > them, and I never have a problem. If your tools suit your needs, please continue to use them. You appear to be a power user and I have more of an operations background where scripts that call lists and use variables for operations, the spaces are more difficult to escape or predict in behavior. I'm naturally pointy-clicky averse, so my experience is different than yours. > As for the 'funky' ½ character, that is a valid codepoint in UTF-8. Is > Xubuntu or ext4 not UTF-8 compliant? I use far 'funkier' characters in > filenames all the time when I need a transcription in IPA. In my experience, any character that requires multiple keystrokes are equally avoided for the above reasons. There is nothing wrong with them, but they may break other things in odd ways down the road. I can only hope this is NOT the case for you. > Considering that the error messages that Thunar and Gnome terminal are > giving me say 'the *file* already exists' leads me to conclude that > somehow the filesystem thinks I am creating a file rather than a folder. > Moreover, the file that it thinks exists does not actually exist. Yes, the inode table seems to think the name is in use in that directory. See my above remarks about fsck and find. Good luck. dafr _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
