From: Malte Wedel <ich@malte.de>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: macOS client issue with line breaks in the configuration
Date: Mon, 6 Dec 2021 19:19:24 +0100 [thread overview]
Message-ID: <7838e77c-33a2-f829-81d2-c7d43a91a4e5@malte.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Hello,
I had an interesting issue with the macOS client, where I used copy and
paste from an e-mail to fill in the configuration. Although everything
looked syntactically correct, it was not syntax highlighted correctly
and could not be saved. It took me a while to realize, this was caused
by DOS line breaks in the source mail, which were copied with the text
and could not be parsed properly.
From my perspective, either the parser should be able to deal with
unexpected line breaks, or line breaks should be normalized, when text
is pasted to the text area, to avoid such an issue, which is hard to
understand for the average user.
Regards,
Malte
[-- Attachment #2: wireguard.png --]
[-- Type: image/png, Size: 58064 bytes --]
reply other threads:[~2021-12-08 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7838e77c-33a2-f829-81d2-c7d43a91a4e5@malte.de \
--to=ich@malte.de \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).