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*
- 
        This will fail with filenames containing newlines or tabs, so it's not very general. Pasting commands to a shell also feels somewhat iffy, given that there's also a proper solution (in your other answer).ilkkachu– ilkkachu2017-09-29 20:12:10 +00:00Commented Sep 29, 2017 at 20:12
- 
        Correct: as I said it's not a general solution, but it is a useful trick to have in one's tool belt. "Pasting commands" - did you mean "Piping commands"? If so, I disagree that it is iffy: it is actually much safer than a shell script, because I can look at the commands before I execute them.NickD– NickD2017-09-29 20:16:58 +00:00Commented Sep 29, 2017 at 20:16
- 
        yep, I meant piping like that. You'd need to be very careful to double check the commands, otherwise you might end up running commands from the filenames. Which would not happen with a shell script that does its job properly.ilkkachu– ilkkachu2017-09-29 20:20:37 +00:00Commented Sep 29, 2017 at 20:20
- 
        I find the trick valuable in "irregular" situations where a shell script is harder to write. If it's a one-off, why bother writing the script? You'd have to write it, test it, debug it and after all this trouble throw it away. Instead, I can write a file (or better yet write a script that writes the file) that contains exactly the commands I need and pipe it into the shell - and then throw it away.NickD– NickD2017-09-29 20:26:50 +00:00Commented Sep 29, 2017 at 20:26
                    
                        Add a comment
                    
                 | 
            
                
            
        
         
    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