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

Good advise all around. Also, much cleaner regex. My failure for not reading closer into sed to discover the 'e' flag. I think we can close this off. I appreciate everyone's attention and responses.

Rohn Wood
– Rohn Wood

2018-09-07 22:46:02 +00:00
Commented Sep 7, 2018 at 22:46
@RohnWood, note that StackExchange is more like a wiki than a support request site. We don't close off requests there. As the original poster, you can accept one of the answers (using the tick box) which indicates that you are happy with the answer given and think it's the best for your need, but that doesn't stop people from suggesting other answers which may be useful to you or other people with similar needs. Questions may be closed through a voting system if they're deemed inappropriate by the community but that's not the case here.

Stéphane Chazelas
– Stéphane Chazelas

2018-09-07 23:20:02 +00:00
Commented Sep 7, 2018 at 23:20

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 »