mv

I often find myself using mv to rename a file. E.g. mv app/models/keywords_builder.rb app/models/keywords_generator.rb Doing so I need to write (ok, tab complete) the path for the second parameter. In this example it isn't too bad but sometimes the path is deeply nested and it seems like quite a bit of extra typing. Is there a more efficient way to do this? You can use history expansion like this: mv app/modules/keywords_builder.rb !#^:h/keywords_generator.rb ! introduces history expansion. # refers to the command currently being typed ^ means the first argument :h is a modifier to get the

So, if I'm in my home directory and I want to move foo.c to ~/bar/baz/foo.c , but those directories don't exist, is there some way to have those directories automatically created, so that you would only have to type mv foo.c ~/bar/baz/ and everything would work out? It seems like you could alias mv to a simple bash script that would check if those directories existed and if not would call mkdir and then mv, but I thought I'd check to see if anyone had a better idea. KarstenF How about this one-liner (in bash): mkdir --parents ./some/path/; mv yourfile.txt $_ Breaking that down: mkdir --parents

I moved a file using git mv . Now I would like to do a diff on the new file to compare it with the old file (with the old, now non-existent name). How do I do this? You need to use -M to let git autodetect the moved file when diffing. Using just git diff as knittl mentioned does not work for me. So simply: git diff -M should do it. The documentation for this switch is: -M[<n>], --find-renames[=<n>] Detect renames. If n is specified, it is a threshold on the similarity index (i.e. amount of addition/deletions compared to the file’s size). For example, -M90% means git should consider a delete

I have a list of certain files that I see using the command below, but how can I copy those files listed into another folder, say ~/test? find . -mtime 1 -exec du -hc {} + Ankur Adding to Eric Jablow's answer, here is a possible solution (it worked for me - linux mint 14 /nadia) find /path/to/search/ -type f -name "glob-to-find-files" | xargs cp -t /target/path/ You can refer to " How can I use xargs to copy files that have spaces and quotes in their names? " as well. Thiyagu ATR Actually, you can process the find command output in a copy command in two ways: If the find command's output doesn

If I am reading a file stored on an NTFS filesystem, and I try to move/rename that file while it is still being read, I am prevented from doing so. If I try this on a UNIX filesystem such as EXT3, it succeeds, and the process doing the reading is unaffected. I can even rm the file and reading processes are unaffected. How does this work? Could somebody explain to me why this behaviour is supported under UNIX filesystems but not NTFS? I have a vague feeling it has to do with hard links and inodes, but I would appreciate a good explanation. Unix filesystems use reference counting and a two-layer

I have a project under git . One day I moved all project files from current directory to foo/bar/ under the project. I did it using git mv . Then I added some more files and did some changes to already existing files. As a result, now when I look at the history of foo/bar/file.c , I can only see changes that I did after I moved the file. I tried to fix this in various ways ( filter-branch with subdirectory filter, etc), but nothing helped, so I am pretty stacked here. I'll appreciate any help that you can give me. Thanks! Dan Moulding To rewrite the history with the files moved: If you want