On Mon, Mar 5, 2018 at 7:25 PM, Willy Tarreau <w...@1wt.eu> wrote:
> I tend to think (first idea out of my head) that for such file types,
> we could very well consider that the command reads multiple lines and
> stops at the first empty line. That's very convenient to use in scripts
> and even by hand in copy-paste sessions. It would work with almost all
> of the data types we have to feed via the CLI, including the maps/acls.
It looks like a clean way to do.
> And a script writing there would just have to run grep -v "^$" to be
> save, which is pretty easy.
> In fact that's already the format used for the output : the output of
> each command is defined as running till the first empty line.
> I also thought about escaping end of lines with a backslash but that
> becomes very painful to place in scripts.
Yes, I also thought about that but discarded the idea since I wanted
something that could easily be used on the command line without major
> Just my two cents, I'm also interested in people's ideas regarding this.
Thanks for the comments, I will think about it and continue to monitor