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*
How to Edit
        - 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
        How to Format
    
    - 
                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>
            How to Tag
        
        A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-bash
        
printf '%s\n'do ?printfprints all the arguments from its 2nd argument onward according the the formatting in its first argument. The format string%s\nspecifies that each string should be printed as a string (duh) with a newline after it. Theededitor reads editing commands from standard input and expects these to be on separate lines, that's why. Run theprintfcommand by itself (up to, but not including the|) to see what gets passed toed. Also tryprintf 'name: %s\n' *(without theedbit, as an educational exercise).echo '11m0\nwq' | ed -s bonjour. Also (in case it saves someone time), ed handles range of lines too:echo 11,13m0\nwq | ed -s bonjour.printf 'name: %s\n' *(without the ed bit, as an educational exercise)" – Another TIL!echomay not output\nas a literal newline (or support any other backslash sequences) on some systems or in some shells (it is not standard behaviour). In shells that support it, it could also be turned off by default, or by a user setting (e.g.shopt -u xpg_echoinbash). Usingprintfis therefore more portable.