Settings documentation update

[danieluhl]

Took me 30 mins to find this settings file this morning so I thought I'd save future users the hassle.

[dimikot]

Absolutely. Thanks!

But could you please revert back newlines (\n) trailing all files involved
in the commit? According to Unix best practices, a text file is better to
have a newline character (I saw you've eaten a couple of them) in the end
of the very last line. Why do so best practices exist? E.g. for the
purpose of echo "...">>... or cat a.txt b.txt could work correctly and do
not glue lines. Also, in vim you cannot even save a text file with no
trailing newline.

Then I'll merge the pull request.

On Wednesday, August 19, 2015, Daniel notifications@github.com wrote:

Took me 30 mins to find this settings file this morning so I thought I'd

save future users the hassle.

You can view, comment on, or merge this pull request online at:

#23
Commit Summary

• added settings info to documentation
• added back trailing whitespace

File Changes

• M README.md
  https://github.com/DmitryKoterov/dklab_realsync/pull/23/files#diff-0
  (4)
• M README.txt
  https://github.com/DmitryKoterov/dklab_realsync/pull/23/files#diff-1
  (5)

Patch Links:

• https://github.com/DmitryKoterov/dklab_realsync/pull/23.patch
• https://github.com/DmitryKoterov/dklab_realsync/pull/23.diff

—
Reply to this email directly or view it on GitHub
#23.

[danieluhl]

Ah, good catch. I found the sublimetext3 setting to fix this:
"ensure_newline_at_eof_on_save": true,
"default_line_ending": "unix",