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.

Required fields*

Rev

@stéphane-chazelas , feel free to add comments to this answer, or suggest other improvements to the OPs code, but the bash script I pasted here was intentionally the minimal change to the OPs script to make it work, and while the aside about other shells is a perfectly good point, the answer isn't incorrect without it.

Jonathan Dursi
– Jonathan Dursi

2014-07-03 16:57:15 +00:00
Commented Jul 3, 2014 at 16:57
However, the answer is incorrect with bugs and bad practises without the fixes I suggested. I agree those errors were in the question in the first place, and it's your answer, you do whatever you want with it, but my view would be to make sure answers always contain correct code if possible, as people may end up copy-pasting code from it (while they wouldn't do that from the question)

Stéphane Chazelas
– Stéphane Chazelas

2014-07-03 18:41:49 +00:00
Commented Jul 3, 2014 at 18:41

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 »