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.
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
while Truebut preferred to "retry infinitely until success" like the original snippet did if possible :) (eg: using thewhile !method)"$@"or, for one or more args, but not the whole list, something like"$3"or"${@:2:3}". There are no quotes at this point. And yes, I switched toif, since I'm not sure what to do from the third try on. But you could doif ! "$@"; then while ! "$@" --otherarg; do sleep 1; done; fito keep looping on the modified command line.quotethat could be placed (as the example used in my post) on the command passed to the retry function. I know how to escape them (as mentioned and linked to a solution that do this in my post) but don't know how to keep them intact...my guess is that placing single quote around double quote would work but not sure how to do thisretry.sh ls pattern "file name", then you getls,pattern, andfile namein$1,$2and$3."$@"expands to those three words, the same as if the script contained"$1" "$2" "$3"(except that"$@"doesn't require knowing the number of arguments). If you call the script asretry.sh ls pattern file\ name, you get the same. The quotes and escapes are removed when the command line is processed, so when you're in the script, you don't have any quotes to deal with, but individual positional parameters.