use json output and familiarize yourself with JQ.On Wednesday, August 23,
2023 at 02:53:23 AM EDT, Roland wrote:
Hi,
> Hi Roland, is `lvs --reportformat json` or `lvs --nameprefixes` good enough?
good when using scripting / automated processing - but not good, when we need
it
Hi,
> Hi Roland, is `lvs --reportformat json` or `lvs --nameprefixes` good
enough?
good when using scripting / automated processing - but not good, when we
need it human readable.
i'd even would call it a bug, when using same strings for "translated"
names.
would anybody accept something like
Hi Roland, is `lvs --reportformat json` or `lvs --nameprefixes` good enough?
On Sat, Aug 19, 2023 at 6:06 PM Roland wrote:
> > furthermore, it's a little bit weird that some columns being printed
> by default when using -o, is
> > there an easier way to remove those besides explictly removing
Am 21.08.23 um 18:17 schrieb David Teigland:
On Sat, Aug 19, 2023 at 06:05:58PM +0200, Roland wrote:
furthermore, it's a little bit weird that some columns being printed by
default when using -o, is there an easier way to remove those besides
explictly removing them one by one with several -o
On Sat, Aug 19, 2023 at 06:05:58PM +0200, Roland wrote:
> furthermore, it's a little bit weird that some columns being printed by
> default when using -o, is there an easier way to remove those besides
> explictly removing them one by one with several -o options ?
> "-o-opt1,-opt2,..." doesn't
> furthermore, it's a little bit weird that some columns being printed
by default when using -o, is
> there an easier way to remove those besides explictly removing them
one by one with several -o options ? "-o-opt1,-opt2,..." doesn't work
sorry for this noise, i was too dumb for that ,
hello,
does somebody know how we can have native (i.e. non translated) column
field names in first line of output of pvs ?
in its current implementation, output is hard to read , difficult to
distinguish and also not scriptable/parseable, as whitespace is used for
field separator and there
