Is there a way to refer to multiple files in a directory without retyping the whole path?

Question

In a bash shell, when I have to remove multiple files in the same directory, I currently need to do something like this:

rm /some/path/file1 /some/path/file2

Is there a shorter way to write this so I don't have to retype /some/path/ without using a variable or changing the working directory?

Perhaps something similar to:

rm /some/path/(file1,file2)

score 63 · Accepted Answer · answered May 23 '13 at 00:02

63

You're close:

rm /some/path/{file1,file2}

or even

rm /some/path/file{1,2}

Related, and supported by other shells, is a pattern like

rm /some/path/file[12]

The first two are expanded to two explicit file name arguments; the third is a pattern against which all files in /some/path are matched.

answered May 23 '13 at 00:02

chepner

7,501

3

May be helpful to note that the commas must not have spaces after them. Tripped me up at first. – Isius Mar 03 '16 at 13:43
Handy for mv commands as well. I believe this is called brace expansion. – Ben Creasy Oct 22 '16 at 20:03
How could I combine this {..,..} syntax with a wildcard (*)? – Melroy van den Berg Feb 14 '23 at 21:05
Brace expansion happens first, so something like foo {bar,bar}* is the same as foo bar* baz*. The result of the brace expansion is subject to further pathname expansion. – chepner Feb 15 '23 at 17:01

score 9 · Answer 2 · answered May 23 '13 at 16:14

Alternatively you can take advantage of the Readline library in Bash. This is a bit of a workaround, but relatively easy to type.

ls /some/path/
rm ESC.file1 ESC.file2

(Assuming your meta prefix is the ESC key.)

The extra ls in the first command puts the path in the history as the last argument of the previous command, ESC. (or as the manual states M-. or even M-_):

Insert[s] the last argument to the previous command (the last word of the previous history entry).

Thus you're effectively typing the last path before the file names. (Please note the trailing slash in the ls line).

score 3 · Answer 3 · edited May 27 '13 at 07:39

In addition to those insightful answers, there's numerous patterns you can use to match groups of files. With filename expansion and pattern matching, you can tell bash to match things like all files in a directory, all files starting with something, all files with the same extension, etc.

Of course, if your using rm, you have to be very careful not to delete things you don't want to. I recommend using ls first, to list what the path argument will show.

Here's a few examples.

Say you want to match all files in a directory, to look at what an rm command would process, look with ls. You could use the asterisk (*) glob operator to match any amount of characters.
```
ls /some/path/*
```
Or maybe all files starting with test:
```
ls /some/path/test*`
```
How about all files starting with test, with one character, and ending with a .sh. You could use the question mark (?) character to match one character.
```
ls /some/path/test?.sh
```
Let's say you have nine files test1.sh, test2.sh, etc, up to test9.sh, and want to delete these test scripts. You also have a testa.sh you want to keep. You could search for all files starting with test, the numbers one through nine or non-alphabetic classes, and ending with .sh. These use the brackets ([]) to match groups of characters.
```
ls /some/path/test[1-9].sh
ls /some/path/test[!:alpha:].sh
```

Matches such as these can be scripted fairly simply too, enabling very fine tuned or broad groupings of files within scripts for automation.

Lri · Answer 4 · 2014-01-05T13:39:12.170

0

If you use bash, you can make M-r repeat the last argument by adding this line to ~/.inputrc:

"\er": "!#:$\e^"

!# is the current line, $ is the last argument, and \e^ is history-expand-line.

edited Jan 05 '14 at 13:39

answered May 23 '13 at 15:48

Lri

5,223

Is there a way to refer to multiple files in a directory without retyping the whole path?

4 Answers4

Linked