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

you could even use exemple1 on such things as a dd output, etc.

Olivier Dulac
– Olivier Dulac

2017-09-11 16:04:55 +00:00
Commented Sep 11, 2017 at 16:04
interresting side note : grep is more efficient the bigger the known part of the regexp is (ex: looking for the string or regexp s is much, mush slower than matching something and this is much slower than matching something even much longer (the latter allowing the regexp match to skip larger portions of the input when differing). On huge files, it basically "divides" the time to parse it by the length ratio (ie, grepping 1 known character is almost 40 times slower than matching a string of 40 known characters. I didn't prof it but it is really noticeable.)

Olivier Dulac
– Olivier Dulac

2017-09-11 16:08:12 +00:00
Commented Sep 11, 2017 at 16:08

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 »