Edit - Unix & Linux Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1

You left out the :%s/.*/"&"/ step -- because, in this case, you know that every filename contains at least one space.

G-Man Says 'Reinstate Monica'
– G-Man Says 'Reinstate Monica'

2014-11-21 20:44:22 +00:00
Commented Nov 21, 2014 at 20:44
1

This will bite you if the file names contain spaces or other special characters. You need to quote them properly. Reviewing a list of commands isn't particularly likely to catch errors. There are far better ways to review commands before running them, such as runing echo mv instead of mv, and then removing the echo if you're happy.

Gilles 'SO- stop being evil'
– Gilles 'SO- stop being evil'

2014-11-21 23:16:22 +00:00
Commented Nov 21, 2014 at 23:16
Spotting a mistake like filenames-with-spaces is precisely what this technique will help with :-)

Tom Rees
– Tom Rees

2014-11-21 23:40:28 +00:00
Commented Nov 21, 2014 at 23:40

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »