From: Stephen Hemminger <stephen@networkplumber•org>
To: John Kodis <john.m.kodis@nasa•gov>
Cc: netdev@vger•kernel.org
Subject: Re: Bad escapes in ip -online
Date: Thu, 7 Sep 2017 09:56:21 -0700 [thread overview]
Message-ID: <20170907095621.085155ee@xeon-e3> (raw)
In-Reply-To: <b4972c84-c827-3a05-2267-bbcadf101260@nasa.gov>
On Thu, 7 Sep 2017 12:08:56 -0400
John Kodis <john.m.kodis@nasa•gov> wrote:
> The -online option to the 'ip link', 'ip addr', and perhaps others is
> putting out a backslash in places where a newline character should go,
> as so:
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
> DEFAULT group default qlen 1000\ link/loopback 00:00:00:00:00:00 brd
> 00:00:00:00:00:00
>
> -- John.
>
The backslash is the virtual line separator in the one line format.
It is has always been that way, and programs parse the oneline output.
prev parent reply other threads:[~2017-09-07 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 16:08 Bad escapes in ip -online John Kodis
2017-09-07 16:56 ` Stephen Hemminger [this message]
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=20170907095621.085155ee@xeon-e3 \
--to=stephen@networkplumber$(echo .)org \
--cc=john.m.kodis@nasa$(echo .)gov \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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