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.

1

oh my, +1, before seing this I always did "commands \<CR> | commands" (which has the advantage of being quite readable, though, as the pipe begin the line, clearly visible. But having to remember to add the "\<CR>" makes it cumbersome)

Olivier Dulac
– Olivier Dulac

2013-07-09 09:11:17 +00:00
Commented Jul 9, 2013 at 9:11
Related: Where are bash line continuations after && and || documented?

Wildcard
– Wildcard

2016-05-13 20:50:57 +00:00
Commented May 13, 2016 at 20:50

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 »