.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "LS++.CONF 1"
.TH LS++.CONF 1 2023-07-29 "perl v5.38.0" "User Contributed Perl Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH NAME
ls++.conf \- ls++ configuration file
.SH DESCRIPTION
.IX Header "DESCRIPTION"
ls++.conf is the configuration file for ls++(1). ls++ first searches for it at
~/.config/ls++/ls++.conf then at ~/.ls++.conf then at ./ls++.conf and finally at
/etc/ls++.conf.
.PP
Lines beginning with a '#' character are comments. All other non-empty lines
are live Perl code. This gives a lot of power to the end user, but it also
allows for fuckups.
.PP
Please don't fuckup.
.SH ENVIRONMENT
.IX Header "ENVIRONMENT"
.ie n .IP @d 8
.el .IP \f(CW@d\fR 8
.IX Item "@d"
Array containting the characters to use for delimiting the columns.
.ie n .IP @c 8
.el .IP \f(CW@c\fR 8
.IX Item "@c"
Array containing the colors to be used.
.ie n .IP $colorscheme 8
.el .IP \f(CW$colorscheme\fR 8
.IX Item "$colorscheme"
Colorscheme to be used.
.ie n .IP %ls_colors 8
.el .IP \f(CW%ls_colors\fR 8
.IX Item "%ls_colors"
A hash where its keys are patterns (possibly valid regular expressions) to be
matched against the files. The values should be attributes or colors which will
be added to the output.
.Sp
This does the same thing as LS_COLORS, except that you can match against the
full filname, and not only the extension. Using LS_COLORS, you could never match
README or Makefile for example. Those two are matched by default.
.Sp
The special value IGNORE will ignore all files matching the key pattern.
.SH COLORS
.IX Header "COLORS"
The default colortable left here for reference (ANSI colors).
.PP
.Vb 10
\&    0    NULL              black
\&    1    NULL              bright black
\&    2    K                 red
\&    3    G, sec            bright red
\&    4    day               green
\&    5    +x                bright green
\&    6    +r                yellow
\&    7    +w, M             bright yellow
\&    8    other             blue
\&    9    hour              bright blue
\&    10                     magenta
\&    11   +s                bright magenta
\&    12                     cyan
\&    13   link              bright cyan
\&    14   B, month, delim   white
\&
\&    15
\&    16                      reset
\&    17                      bold
.Ve
.SH AUTHOR
.IX Header "AUTHOR"
.Vb 4
\&  Magnus Woldrich
\&  CPAN ID: WOLDRICH
\&  magnus@trapd00r.se
\&  http://japh.se
.Ve
.SH "REPORTING BUGS"
.IX Header "REPORTING BUGS"
Report bugs and/or feature requests on <https://github.com/trapd00r/ls\-\-/issues>
or to magnus@trapd00r.se
.SH COPYRIGHT
.IX Header "COPYRIGHT"
Copyright (C) 2010 Magnus Woldrich. All right reserved.
This program is free software; you can redistribute it and/or modify it under
the same terms as Perl itself.