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.

Thanks, the [[ tip works well. Also "$()" makes sense too.

Script Kitty
– Script Kitty

2017-01-15 03:33:41 +00:00
Commented Jan 15, 2017 at 3:33
@ScriptKitty Note the "$i" as well.

heemayl
– heemayl

2017-01-15 03:34:06 +00:00
Commented Jan 15, 2017 at 3:34
@ScriptKitty did $i have spaces in filename ?

Sergiy Kolodyazhnyy
– Sergiy Kolodyazhnyy

2017-01-15 04:01:29 +00:00
Commented Jan 15, 2017 at 4:01
@Serg Why not follow the usual and safer route rather than confirming? :)

heemayl
– heemayl

2017-01-15 04:02:22 +00:00
Commented Jan 15, 2017 at 4:02
1

@heemayl by "safe and usual" route , I assume you mean quoting the variables - with which I absolutely agree , and that should be done in first place. I'm just curious what's user's specific case is :)

Sergiy Kolodyazhnyy
– Sergiy Kolodyazhnyy

2017-01-15 04:04:37 +00:00
Commented Jan 15, 2017 at 4:04

| Show 1 more 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 »