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.

Hi slm, Thank you for the response. Your solution makes sense and also works.

maGz
– maGz

2013-05-05 19:37:45 +00:00
Commented May 5, 2013 at 19:37
Yup, @Sukminder was a little quicker hitting the submit button, thanks for the question 8-).

slm
– slm ♦

2013-05-05 19:38:37 +00:00
Commented May 5, 2013 at 19:38
1

Note that \s is a GNU extension (inspired by perl) and is short for the standard [[:space:]], not [[:blank:]], that is it includes all the horizontal and vertical spacing characters, not just tab and space. It is also locale dependant. Your solution would also fail to remove the second test3 in "x test3 test3 y"

Stéphane Chazelas
– Stéphane Chazelas

2013-05-05 20:07:13 +00:00
Commented May 5, 2013 at 20:07
@StephaneChazelas, thanks for the improvement. Question, is it better to adjust our answers in situations like this or leave them and let the comments pick up these nuances? You've corrected a couple of my answers, which I appreciate, since I'm learning like everyone else, but I wasn't sure what was the correct thing to do?

slm
– slm ♦

2013-05-05 20:14:24 +00:00
Commented May 5, 2013 at 20:14
Up to you really. I'm not sure there's some consensus on that. You can always ask on meta. Nothing wrong in editing the answer to improve or point out the limitations even if you come to realise that through others' comments IMO.

Stéphane Chazelas
– Stéphane Chazelas

2013-05-05 20:27:52 +00:00
Commented May 5, 2013 at 20:27

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 »