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

1

This is how I would go about it to. Not to much thinking required.

Lieven Keersmaekers
– Lieven Keersmaekers

2016-09-08 04:56:14 +00:00
Commented Sep 8, 2016 at 4:56
1

I do this when it's quick to type but try replacing (for example) database passwords that can look like this -> ]Xqysmw#IUeO"g@bp9y}BCj<-@|?X.3 The point is the content of the words shouldn't suddenly make copying with the mouse faster.

Miati
– Miati

2016-09-08 05:13:17 +00:00
Commented Sep 8, 2016 at 5:13
1

We have edit history, tagging on "Edit" with some extra information makes your post less readable. Think about all future readers, you should integrate your changes to make your answer a consistent whole that is easy to read and understand. Tagging on your thoughts this way doesn't achieve that.

Anthon
– Anthon

2016-09-08 05:15:07 +00:00
Commented Sep 8, 2016 at 5:15

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 »