From: ludo@gnu.org (Ludovic Courtès)
To: Steve Sprang <steve.sprang@gmail.com>
Cc: 30053@debbugs.gnu.org
Subject: [bug#30053] [PATCH 1/3] Improve appearance of tabular output.
Date: Thu, 11 Jan 2018 22:32:29 +0100 [thread overview]
Message-ID: <878td4nksy.fsf@gnu.org> (raw)
In-Reply-To: <CA+xn8YBKpjVYmrhKbR7Y=wZnnfr+ALuEMHo_b5AEFMAOTEkDxA@mail.gmail.com> (Steve Sprang's message of "Tue, 9 Jan 2018 14:34:46 -0800")
Hello Steve,
Long time no see! ;-)
Steve Sprang <steve.sprang@gmail.com> skribis:
> I noticed when listing installed or available packages that the output
> is often pretty jumbled up because columns in each row have an
> inconsistent width.
>
> This series of patches adds a new procedure for printing tabular data
> (pretty-print-table) and modifies the code for --list-installed,
> --list-available, and --list-generations to utilize it.
I have a disappointing explanation I’m afraid: the reason columns look
this way is because they are tab-separated, which in turn makes it easy
to filter with ‘cut’:
--8<---------------cut here---------------start------------->8---
$ guix package -A | cut -f1 | head
0ad
0ad-data
0xffff
4store
4ti2
a2ps
aalib
abbaye
abc
abcde
--8<---------------cut here---------------end--------------->8---
An example from the manual (info "(guix) Invoking guix build"):
guix build --quiet --keep-going \
`guix package -A | cut -f1,2 --output-delimiter=@`
The idea was to have this shell-scripting-friendly format, and to
provide fancier output in other commands, such as --search (which is in
fact script-friendly as well thanks to recutils).
Silly? Awesome? Ugly? What do people think? :-)
Thank you,
Ludo’.
next prev parent reply other threads:[~2018-01-11 21:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 22:34 [bug#30053] [PATCH 1/3] Improve appearance of tabular output Steve Sprang
2018-01-09 22:37 ` [bug#30053] [PATCH 2/3] " Steve Sprang
2018-01-09 22:37 ` [bug#30053] [PATCH 3/3] " Steve Sprang
2018-01-11 21:32 ` Ludovic Courtès [this message]
2018-01-11 23:32 ` [bug#30053] [PATCH 1/3] " Steve Sprang
2018-01-12 13:28 ` Roel Janssen
2018-01-13 19:59 ` Steve Sprang
2018-01-16 14:16 ` Ludovic Courtès
2018-01-16 23:56 ` Steve Sprang
2021-07-15 5:39 ` Maxim Cournoyer
2021-07-15 17:36 ` [bug#30053] [PATCH 1/3 v2] " Maxim Cournoyer
2021-07-15 20:15 ` bug#30053: [PATCH 1/3] " Maxim Cournoyer
2021-07-21 16:56 ` [bug#30053] " Ludovic Courtès
2021-07-21 21:43 ` Maxim Cournoyer
2021-07-15 22:05 ` Sarah Morgensen via Guix-patches via
2021-07-16 1:25 ` Maxim Cournoyer
2018-01-12 14:56 ` Danny Milosavljevic
2018-01-12 15:26 ` Leo Famulari
2018-01-12 15:50 ` bug#30087: "guix package -A" hangs with attached package set Danny Milosavljevic
2020-12-03 0:10 ` zimoun
2020-12-22 16:12 ` zimoun
2021-01-11 12:29 ` zimoun
2018-01-13 13:47 ` [bug#30053] [PATCH 1/3] Improve appearance of tabular output Ludovic Courtès
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=878td4nksy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30053@debbugs.gnu.org \
--cc=steve.sprang@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.