|
|
|
git-column(1)
|
|
|
|
=============
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
|
|
|
git-column - Display data in columns
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
|
|
|
[verse]
|
|
|
|
'git column' [--command=<name>] [--[raw-]mode=<mode>] [--width=<width>]
|
|
|
|
[--indent=<string>] [--nl=<string>] [--padding=<n>]
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
|
|
|
This command formats the lines of its standard input into a table with
|
|
|
|
multiple columns. Each input line occupies one cell of the table. It
|
|
|
|
is used internally by other git commands to format output into
|
|
|
|
columns.
|
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
-------
|
|
|
|
--command=<name>::
|
|
|
|
Look up layout mode using configuration variable column.<name> and
|
|
|
|
column.ui.
|
|
|
|
|
|
|
|
--mode=<mode>::
|
|
|
|
Specify layout mode. See configuration variable column.ui for option
|
|
|
|
syntax in linkgit:git-config[1].
|
|
|
|
|
|
|
|
--raw-mode=<n>::
|
|
|
|
Same as --mode but take mode encoded as a number. This is mainly used
|
|
|
|
by other commands that have already parsed layout mode.
|
|
|
|
|
|
|
|
--width=<width>::
|
|
|
|
Specify the terminal width. By default 'git column' will detect the
|
|
|
|
terminal width, or fall back to 80 if it is unable to do so.
|
|
|
|
|
|
|
|
--indent=<string>::
|
|
|
|
String to be printed at the beginning of each line.
|
|
|
|
|
|
|
|
--nl=<string>::
|
|
|
|
String to be printed at the end of each line,
|
|
|
|
including newline character.
|
|
|
|
|
|
|
|
--padding=<N>::
|
|
|
|
The number of spaces between columns. One space by default.
|
|
|
|
|
|
|
|
EXAMPLES
|
|
|
|
--------
|
|
|
|
|
|
|
|
Format data by columns:
|
|
|
|
------------
|
|
|
|
$ seq 1 24 | git column --mode=column --padding=5
|
|
|
|
1 4 7 10 13 16 19 22
|
|
|
|
2 5 8 11 14 17 20 23
|
|
|
|
3 6 9 12 15 18 21 24
|
|
|
|
------------
|
|
|
|
|
|
|
|
Format data by rows:
|
|
|
|
------------
|
|
|
|
$ seq 1 21 | git column --mode=row --padding=5
|
|
|
|
1 2 3 4 5 6 7
|
|
|
|
8 9 10 11 12 13 14
|
|
|
|
15 16 17 18 19 20 21
|
|
|
|
------------
|
|
|
|
|
|
|
|
List some tags in a table with unequal column widths:
|
|
|
|
------------
|
|
|
|
$ git tag --list 'v2.4.*' --column=row,dense
|
|
|
|
v2.4.0 v2.4.0-rc0 v2.4.0-rc1 v2.4.0-rc2 v2.4.0-rc3
|
|
|
|
v2.4.1 v2.4.10 v2.4.11 v2.4.12 v2.4.2
|
|
|
|
v2.4.3 v2.4.4 v2.4.5 v2.4.6 v2.4.7
|
|
|
|
v2.4.8 v2.4.9
|
|
|
|
------------
|
|
|
|
|
docs: add CONFIGURATION sections that fuzzy map to built-ins
Add a CONFIGURATION section to the documentation of various built-ins,
for those cases where the relevant config/NAME.txt doesn't map only to
one git-NAME.txt. In particular:
* config/blame.txt: used by git-{blame,annotate}.txt. Since the
git-annotate(1) documentation refers to git-blame(1) don't add a
"CONFIGURATION" section to git-annotate(1), only to git-blame(1).
* config/checkout.txt: maps to both git-checkout.txt and
git-switch.txt (but nothing else).
* config/init.txt: should be included in git-init(1) and
git-clone(1).
* config/column.txt: We should ideally mention the relevant subset of
this in git-{branch,clean,status,tag}.txt, but let's punt on it for
now. We will when we eventually split these sort of files into
e.g. config/column.txt and
config/column/{branch,clean,status,tag}.txt, with the former
including the latter set.
Things that are being left out, and why:
* config/{remote,remotes,credential}.txt: Configuration that affects
how we talk to remote repositories is harder to untangle. We'll need
to include some of this in git-{fetch,remote,push,ls-remote}.txt
etc., but some of those only use a small subset of these
options. Let's leave this for now.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Reviewed-by: Matheus Tavares <matheus.bernardino@usp.br>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2 years ago
|
|
|
CONFIGURATION
|
|
|
|
-------------
|
|
|
|
|
|
|
|
include::includes/cmd-config-section-all.txt[]
|
|
|
|
|
|
|
|
include::config/column.txt[]
|
|
|
|
|
|
|
|
GIT
|
|
|
|
---
|
|
|
|
Part of the linkgit:git[1] suite
|