It’s possible that the reason that renaming failed is that the file is still open. Even if you are closing the file, it could be held open because of (for example): A file handle is inherited by a subprocess of your process An anti-virus program is scanning the file for viruses, and so has it … Read more
Yes you can do this. In Python you can use the move function in shutil library to achieve this. Let’s say on Linux, you have a file in /home/user/Downloads folder named “test.txt” and you want to move it to /home/user/Documents and also change the name to “useful_name.txt”. You can do both things in the same … Read more
I can only speak for Debian. The two programs are called /usr/bin/rename.ul from the util-linux package (hence the .ul suffix) /usr/bin/prename from the perl package The actual rename command works via the /etc/alternatives mechanism, whereby /usr/bin/rename is a symlink to /etc/alternatives/rename /etc/alternatives/rename is a symlink to /usr/bin/prename The same problem has been bugging me on … Read more
To rename a file you can use NSFileManager’s moveItemAtURL. Moving the file with moveItemAtURL at the same location but with two different file names is the same operation as “renaming”. Simple example: Swift 2 do { let path = NSSearchPathForDirectoriesInDomains(.DocumentDirectory, .UserDomainMask, true)[0] let documentDirectory = NSURL(fileURLWithPath: path) let originPath = documentDirectory.URLByAppendingPathComponent(“currentname.pdf”) let destinationPath = documentDirectory.URLByAppendingPathComponent(“newname.pdf”) … Read more
For Java 1.7+, use java.nio.file.Files.move(Path source, Path target, CopyOption… options) with CopyOptions “REPLACE_EXISTING” and “ATOMIC_MOVE”. See API documentation for more information. For example: Files.move(src, dst, StandardCopyOption.ATOMIC_MOVE);
Starting Git 2.0.1 (June 25th, 2014), a git mv will just work on a case-insensitive OS. See commit baa37bf by David Turner (dturner-tw). mv: allow renaming to fix case on case-insensitive filesystems “git mv hello.txt Hello.txt” on a case-insensitive filesystem always triggers “destination already exists” error, because these two names refer to the same path … Read more
Now that file.name is a read-only property, I’ve found this to be the best method to rename a File object in the browser: const myNewFile = new File([myFile], ‘new_name.png’, {type: myFile.type});
Select file in project explorer and press -> Shift + F6 Select file with right click + Refactor -> Rename
In your code: Shouldn’t it be : File from = new File(directory, currentFileName); instead of File from = new File(directory, “currentFileName”); For safety, Use the File.renameTo() . But check for directory existence before renaming it! File dir = Environment.getExternalStorageDirectory(); if(dir.exists()){ File from = new File(dir,”from.mp4″); File to = new File(dir,”to.mp4″); if(from.exists()) from.renameTo(to); } Refer: http://developer.android.com/reference/java/io/File.html#renameTo%28java.io.File%29
Yes and no. rename() is atomic assuming the OS does not crash. It cannot be split by any other filesystem op. If the system crashes you might see a ln() operation instead. Also note, when operating on a network filesystem, you might get ENOENT when the operation succeeded successfully. Local filesystem can’t do that to … Read more