I just came across this weirdness: I want to do the equivalent of dragging a directory inside another (moving it). Trival day-to-day task for a GUI.
here is my tree:
.
├── assemble.py
├── Basic Information Retrieval.ipynb
├── Basic Information Retrieval.tex
├── Book
│ ├── book.aux
│ ├── book.log
│ ├── Book_master.tex
│ ├── book.out
│ ├── book.pdf
│ ├── book.tex
│ ├── book.toc
│ ├── build.sh
│ ├── chapter_0.tex
│ ├── chapter_1.tex
│ ├── chapter_2.tex
│ ├── chapter_3.tex
│ ├── chapter_4.tex
│ ├── chapter_5.tex
│ ├── Cosine Similarity_files
│ │ ├── Cosine Similarity_17_0.png
│ │ └── Cosine Similarity_22_0.png
│ ├── Language Models_files
│ │ └── Language Models_5_0.png
│ └── nb_preamble.tex
├── convert_to_latex.sh
├── convert_to_pdf.sh
├── corpus_zika
├── Cosine Similarity_files
│ ├── Cosine Similarity_17_0.png
│ └── Cosine Similarity_22_0.png
├── Cosine Similarity.ipynb
├── Cosine Similarity.tex
├── Dicionario_zika.dict
├── Language Models_files
│ └── Language Models_5_0.png
├── Language Models.ipynb
├── Language Models.tex
├── Probabilistic Text Models.ipynb
├── Probabilistic Text Models.tex
├── README.md
├── Topic Modeling.ipynb
└── Topic Modeling.tex
I want to move Cosine Similarity_files
into Book/
, eventualy overwriting it if it is already there. I issue the natural command:
mv Cosine\ Similarity_files Book/
and I get the message Directory not empty
WTF!? But it gets better if I ask it to move one level deeper:
mv Cosine\ Similarity_files Book/Cosine\ Similarity_files
It dutifully does what it wouldn't do before! it writes the source directory into the target directory!! WTF²!?!
Why is that? Does it make any sense?
Book/Cosine\ Similarity_files/Cosine\ Similarity_files