1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
//
// No copyright is claimed. This code is in the public domain; do with
// it what you wish.
//
// po4a: entry man manual
// Written by Andries E. Brouwer (aeb@cwi.nl)
// Placed in the public domain
= rename(1)
:doctype: manpage
:man manual: User Commands
:man source: util-linux {release-version}
:page-layout: base
:command: rename
== NAME
rename - rename files
== SYNOPSIS
*rename* [options] _expression replacement file_...
== DESCRIPTION
*rename* will rename the specified files by replacing the first occurrence of _expression_ in their name by _replacement_.
== OPTIONS
*-s*, *--symlink*::
Do not rename a symlink but change where it points.
*-v*, *--verbose*::
Show which files were renamed, if any.
*-n*, *--no-act*::
Do not make any changes; add *--verbose* to see what would be made.
*-a*, *--all*::
Replace all occurrences of _expression_ rather than only the first one.
*-l*, *--last*::
Replace the last occurrence of _expression_ rather than the first one.
*-o*, *--no-overwrite*::
Do not overwrite existing files. When *--symlink* is active, do not overwrite symlinks pointing to existing targets.
*-i*, *--interactive*::
Ask before overwriting existing files.
include::man-common/help-version.adoc[]
== WARNING
The renaming has no safeguards by default or without any one of the options *--no-overwrite*, *--interactive* or *--no-act*. If the user has permission to rewrite file names, the command will perform the action without any questions. For example, the result can be quite drastic when the command is run as root in the _/lib_ directory. Always make a backup before running the command, unless you truly know what you are doing.
== EDGE CASES
If the _expression_ is empty, then by default _replacement_ will be added to the start of the filename. With *--all*, _replacement_ will be inserted in between every two characters of the filename, as well as at the start and end.
Normally, only the final path component of a filename is updated. (Or with *--symlink*, only the final path component of the link.) But if either _expression_ or _replacement_ contains a _/_, the full path is updated. This can cause a file to be moved between folders. Creating folders, and moving files between filesystems, is not supported.
== INTERACTIVE MODE
As most standard utilities rename can be used with a terminal device (tty in short) in canonical mode, where the line is buffered by the tty and you press ENTER to validate the user input. If you put your tty in cbreak mode however, rename requires only a single key press to answer the prompt. To set cbreak mode, run for example:
....
sh -c 'stty -icanon min 1; "$0" "$@"; stty icanon' rename -i from to files
....
== EXIT STATUS
*0*::
all requested rename operations were successful
*1*::
all rename operations failed
*2*::
some rename operations failed
*4*::
nothing was renamed
*64*::
unanticipated error occurred
== EXAMPLES
Given the files _foo1_, ..., _foo9_, _foo10_, ..., _foo278_, the commands
....
rename foo foo00 foo?
rename foo foo0 foo??
....
will turn them into _foo001_, ..., _foo009_, _foo010_, ..., _foo278_. And
....
rename .htm .html *.htm
....
will fix the extension of your html files. Provide an empty string for shortening:
....
rename '_with_long_name' '' file_with_long_name.*
....
will remove the substring in the filenames.
== SEE ALSO
*mv*(1)
include::man-common/bugreports.adoc[]
include::man-common/footer.adoc[]
ifdef::translation[]
include::man-common/translation.adoc[]
endif::[]
|
