In part it is in preparation for the merging of tests/Makefile into the too-level makefile, but mostly it's a "while at it" refactoring (introducing, among other things, a more idiomatic usage of the
Seasons greetings, This is a resubmission[1][2] of the rename(1), with attempt to move it from util-linux package to coreutils. Various compiler warnings are removed, make syntax-check passes, --test
The implementation is completely rewrote without chaning existing command line syntax. This implementation adds --exec option, which will allow use of a string manipulation command, such as 'tr' or '
Hello, The next coreutils and util-linux releases are going to be made close to each others to avoid 'su' coming from multiple source, or being missing. At same go moving 'rename' could make sense. I
Hi Sami, Thanks for the fixes. There is too much new and untested code to include this new program in the upcoming release. A few things should be changed regardless. For consistency with other GNU t
BSD has a bit more advanced rename. http://rename.berlios.de/ I guess that is not much in use because the only version of on line manual page I found was in Google cache. http://webcache.googleuserco
To rename a file a user need to use mv command and specify the DEST dir: mv /some/very/long/path/file /some/very/long/path/ This makes it not so easy to use when typing a command but also makes a scr
Sounds reasonable. After hearing what you and others has said I made couple modifications to the command. o Support recursion. o Support input from stdin, and have a switch for null terminated names.
We already have. And POSIX 2008 already acted on that. While you quoted rename(2) (which was intentionally not changed), you forgot to also read the POSIX wording on mv(1): http://pubs.opengroup.org/
'If the old argument and the new argument resolve to either .... or different directory entries for the same existing file, rename() shall return successfully and perform no other action.' It's incre
mv is from coreutils BTW. Here is the related comment from the source: "Set *UNLINK_SRC if we've determined that the caller wants to do `rename (a, b)' where `a' and `b' are distinct hard links to th
2011/6/27 Pádraig Brady <address@hidden>: That is true as well. To be honest if the command would not already exist it should not be taken to any package. Now when it already is in use making it goo
Well it's not linux specific. So I suppose it fits more here, than in util-linux. I've never used rename actually, instead using find | sed | sh in the rare times I've had to do something like this.
* tests/tail-2/F-vs-rename.sh: Keep stdout and stderr separate, so that interspersion doesn't impact regex checks. Also wait for each file's data to be printed to avoid multiple writes to a file to b
Hi, I don't think this is really portable, the 'p' prefix was added to fix Debian bug #304705. In fact I don't know if, where and under which name this rename Perl script can be found in other distri
md5sum.c will be the base for all digest functions, so rename accordingly. * src/md5sum.c: Rename to ... * src/digest.c: ... renamed from md5sum.c * scripts/git-hooks/commit-msg: Allow digest: commit
md5sum.c will be the base for all digest functions, so rename accordingly. * src/md5sum.c: Rename to ... * src/digest.c: ... renamed from md5sum.c * scripts/git-hooks/commit-msg: Allow digest: commit
Use renameat2 to avoid a rename race condition, on recent-enough GNU/Linux. * bootstrap.conf (gnulib_modules): Add renameat2. * src/shred.c: Include renameat2.h. (wipename): Use renameat2 instead of
Good point. perl: /usr/bin/prename That one supports -f for "force" too, but -n means "test" rather than "noclobber". Of course the replacement syntax is different and is more like my find | sed | sh
Hello coreutilitarians, I have been lately making some util-linux patches and while doing so I found rename command. It did not take long to realize that the command would be much better if it would