neulab/tldr huggingface dataset:
Line                                     Notes ------------------------------------------------------------ # branch.oid <commit> | (initial)        Current commit. # branch.head <branch> | (detached)      Current branch. # branch.upstream <upstream_branch>      If upstream is set. # branch.ab +<ahead> -<behind>           If upstream is set and the commit is present. ------------------------------------------------------------
Changed Tracked Entries Following the headers, a series of lines are printed for tracked entries. One of three different line formats may be used to describe an entry depending on the type of change. Tracked entries are printed in an undefined order; parsers should allow for a mixture of the 3 line types in any order.
Ordinary changed entries have the following format:
1 <XY> <sub> <mH> <mI> <mW> <hH> <hI> <path>
Renamed or copied entries have the following format:
2 <XY> <sub> <mH> <mI> <mW> <hH> <hI> <X><score> <path><sep><origPath>
Field       Meaning -------------------------------------------------------- <XY>        A 2 character field containing the staged and unstaged XY values described in the short format, with unchanged indicated by a "." rather than a space. <sub>       A 4 character field describing the submodule state. "N..." when the entry is not a submodule. "S<c><m><u>" when the entry is a submodule. <c> is "C" if the commit changed; otherwise ".". <m> is "M" if it has tracked changes; otherwise ".". <u> is "U" if there are untracked changes; otherwise ".". <mH>        The octal file mode in HEAD. <mI>        The octal file mode in the index. <mW>        The octal file mode in the worktree. <hH>        The object name in HEAD. <hI>        The object name in the index. <X><score>  The rename or copy score (denoting the percentage of similarity between the source and target of the move or copy). For example "R100" or "C75". <path>      The pathname.  In a renamed/copied entry, this is the target path. <sep>       When the `-z` option is used, the 2 pathnames are separated with a NUL (ASCII 0x00) byte; otherwise, a tab (ASCII 0x09) byte separates them. <origPath>  The pathname in the commit at HEAD or in the index. This is only present in a renamed/copied entry, and tells where the renamed/copied contents came from. --------------------------------------------------------
Unmerged entries have the following format; the first character is a "u" to distinguish from ordinary changed entries.
u <XY> <sub> <m1> <m2> <m3> <mW> <h1> <h2> <h3> <path>
Field       Meaning -------------------------------------------------------- <XY>        A 2 character field describing the conflict type as described in the short format. <sub>       A 4 character field describing the submodule state as described above. <m1>        The octal file mode in stage 1. <m2>        The octal file mode in stage 2. <m3>        The octal file mode in stage 3. <mW>        The octal file mode in the worktree. <h1>        The object name in stage 1. <h2>        The object name in stage 2. <h3>        The object name in stage 3. <path>      The pathname. --------------------------------------------------------
Other Items Following the tracked entries (and if requested), a series of lines will be printed for untracked and then ignored items found in the worktree.
Untracked items have the following format:
? <path>
Ignored items have the following format:
! <path>
Pathname Format Notes and -z When the -z option is given, pathnames are printed as is and without any quoting and lines are terminated with a NUL (ASCII 0x00) byte.
Without the -z option, pathnames with "unusual" characters are quoted as explained for the configuration variable core.quotePath (see git- config(1)).
The command honors color.status (or status.color — they mean the same thing and the latter is kept for backward compatibility) and color.status.<slot> configuration variables to colorize its output.
If the config variable status.relativePaths is set to false, then all paths shown are relative to the repository root, not to the current directory.
If status.submoduleSummary is set to a non zero number or true (identical to -1 or an unlimited number), the submodule summary will be enabled for the long format and a summary of commits for modified submodules will be shown (see --summary-limit option of git-submodule(1)). Please note that the summary output from the status command will be suppressed for all submodules when diff.ignoreSubmodules is set to all or only for those submodules where submodule.<name>.ignore=all. To also view the summary for ignored submodules you can either use the --ignore-submodules=dirty command line option or the git submodule summary command, which shows a similar output but does not honor these settings.
By default, git status will automatically refresh the index, updating the cached stat information from the working tree and writing out the result. Writing out the updated index is an optimization that isn’t strictly necessary (status computes the values for itself, but writing them out is just to save subsequent programs from repeating our computation). When status is run in the background, the lock held during the write may conflict with other simultaneous processes, causing them to fail. Scripts running status in the background should consider using git --no-optional-locks status (see git(1) for details).
gitignore(5)
pdfunite(1)                  General Commands Manual                 pdfunite(1)
pdfunite - Portable Document Format (PDF) page merger
pdfunite [options] PDF-sourcefile1..PDF-sourcefilen PDF-destfile
pdfunite merges several PDF (Portable Document Format) files in order of their occurrence on command line to one PDF result file.
Neither of the PDF-sourcefile1 to PDF-sourcefilen should be encrypted.
-v     Print copyright and version information.
-h     Print usage information.  (-help and --help are equivalent.)
pdfunite sample1.pdf sample2.pdf sample.pdf
merges all pages from sample1.pdf and sample2.pdf (in that order) and creates sample.pdf
The pdfunite software and documentation are copyright 1996-2004 Glyph & Cog, LLC and copyright 2005-2011 The Poppler Developers - http://poppler.freedesktop.org
pdfdetach(1), pdffonts(1), pdfimages(1), pdfinfo(1), pdftocairo(1), pdftohtml(1), pdftoppm(1), pdftops(1), pdftotext(1) pdfseparate(1), pdfsig(1)
PO4A-GETTEXTIZE(1)     User Contributed Perl Documentation    PO4A-GETTEXTIZE(1)
po4a-gettextize - convert an original file (and its translation) to a PO file
po4a-gettextize -f fmt -m master.doc [-l XX.doc] -p XX.po
(XX.po is the output, all others are inputs)
The po4a (PO for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they were not expected like documentation.
The po4a-gettextize script is in charge of converting documentation files to PO files.  If you start a new translation, po4a-gettextize will extract the translatable strings from the documentation file and write a POT file from it.
If you already have a translated file, po4a-gettextize will try to extract the translations it contains and put them in place in the written PO file. Be warned that very few intelligence is used in this process: the Nth string of the translated file is supposed to be the translation of the Nth string in the original. If it's not the case, you're dead. That's why it is very important that both files share exactly the same structure.
However, po4a-gettextize will diagnose your death by detecting any desynchronisation between files, and reporting where they occur. In that case, you should edit manually the files to solve the reported disparity. Even if no error were reported, you should check carefully that the generated PO file is correct (i.e. that each msgstr is the translation of the associated msgid, and not the one before or after).
Even if the script manages to do its job without any apparent problem, it still marks all extracted translations as fuzzy, to make sure that the translator will have a look at them, and detect any remaining problem.
If the master document has non-ASCII characters, the new generated PO file will be in UTF-8, in order to allow non-standard characters in a culture independent way. Else (if the master document is completely in ASCII), the generated PO will use the encoding of the translated input document.
-f, --format Format of the documentation you want to handle. Use the --help-format option to see the list of available formats.
-m, --master File containing the master document to translate. You can use this option multiple times if you want to gettextize multiple documents.
-M, --master-charset Charset of the file containing the document to translate.
-l, --localized File containing the localized (translated) document. If you provided multiple master files, you may wish to provide multiple localized file by using this option more than once.
-L, --localized-charset Charset of the file containing the localized document.
-p, --po File where the message catalog should be written. If not given, the message catalog will be written to the standard output.
-o, --option Extra option(s) to pass to the format plugin. Specify each option in the 'name=value' format. See the documentation of each plugin for more information about the valid options and their meanings.
-h, --help Show a short help message.
--help-format List the documentation formats understood by po4a.
-V, --version Display the version of the script and exit.
-v, --verbose Increase the verbosity of the program.
-d, --debug Output some debugging information.
--msgid-bugs-address email@address Set the report address for msgid bugs. By default, the created POT files have no Report-Msgid-Bugs-To fields.
--copyright-holder string Set the copyright holder in the POT header. The default value is "Free Software Foundation, Inc."
--package-name string Set the package name for the POT header. The default is "PACKAGE".
--package-version string Set the package version for the POT header. The default is "VERSION".
po4a-normalize(1), po4a-translate(1), po4a-updatepo(1), po4a(7)
Denis Barbier <barbier@linuxfr.org> Nicolas Francois <nicolas.francois@centraliens.net> Martin Quinson (mquinson#debian.org)
Copyright 2002-2012 by SPI, inc.
This program is free software; you may redistribute it and/or modify it under the terms of GPL (see the COPYING file).
monodevelop(1)               General Commands Manual              monodevelop(1)
monodevelop - Free GNOME Development Environment
monodevelop [options] [projectfile]
monodevelop Free GNOME Development Environment
Options --debug Run mono in debug mode
--trace Run mono in trace mode
--profile Run mono in profile mode
--new-window force MD to open a new instance instead of passing to a running one. This option is forced if opening a combine.
MONODEVELOP_CONSOLE_LOG_LEVEL The logging level, possible values are `fatal', `error', `warn', `info' and `debug'. The default is to log fatal, error and warn.
MONODEVELOP_CONSOLE_LOG_USE_COLOUR Use colour in log - true or false. The default is false.
MONODEVELOP_LOG_FILE If set, log is written to the specified file.
MONODEVELOP_FILE_LOG_LEVEL The logging level, possible values are `fatal', `error', `warn', `info' and `debug'. Valid only if MONODEVELOP_LOG_FILE is specified. The default is to log fata, error, warn and info.
mdtool(1), mono(1), mcs(1)
Copyright (C) 2008 Novell, Inc (http://www.novell.com)
Visit http://lists.ximian.com/mailman/listinfo/monodevelop-list for details.
Visit http://www.monodevelop.com for details
ISOINFO(8)                   System Manager's Manual                  ISOINFO(8)
devdump, isoinfo, isovfy, isodump - Utility programs for dumping and verifying iso9660 images.
devdump isoimage
isodump isoimage
isoinfo [ options ] [ find [ find expression ]]
isovfy isoimage
devdump is a crude utility to interactively display the contents of device or filesystem images.  The initial screen is a display of the first 256 bytes of the first 2048 byte sector.  The commands are the same as with isodump.
isodump is a crude utility to interactively display the contents of iso9660 images in order to verify directory integrity.  The initial screen is a display of the first part of the root directory, and the prompt shows you the extent number and offset in the extent.
You can use the 'a' and 'b' commands to move backwards and forwards within the image. The 'g' command allows you to goto an arbitrary extent, and the 'f' command specifies a search string to be used. The '+' command searches forward for the next instance of the search string, and the 'q' command exits devdump or isodump.
isoinfo is a utility to perform directory like listings of iso9660 images.
isovfy is a utility to verify the integrity of an iso9660 image. Most of the tests in isovfy were added after bugs were discovered in early versions of mkisofs.  It isn't all that clear how useful this is anymore, but it doesn't hurt to have this around.
The options common to all programs are -help,-h,-version, i=name,dev=name.  The isoinfo program has additional command line options. The options are:
-h     print a summary of all options.
-d     Print information from the primary volume descriptor (PVD) of the iso9660 image. This includes information about Rock Ridge, Joliet extensions and Eltorito boot information if present.
-f     generate output as if a 'find . -print' command had been run on the iso9660 image. You should not use the -l image with the -f option.  The same output is created by calling isoinfo with -find -print
-find find expression This option acts a separator. If it is used, all isoinfo options must be to the left of the -find option. To the right of the -find option, mkisofs accepts the find command line syntax only.  If the find expression includes a -print or -ls promary, the -l to isoinfo is ignored.  If the find expression evaluates as true, the selected action (e.g.  list the ISO-9660 directory) is performed.
-i iso_image Specifies the path of the iso9660 image that we wish to examine. The options -i and dev=target are mutual exclusive.
-ignore-error Ignore errors.  The commands by default aborts on several errors, such as read errors. With this option in effect, the commands try to continue.  Use with care.
dev=target Sets the SCSI target for the drive, see notes above.  A typical device specification is dev=6,0 .  If a filename must be provided together with the numerical target specification, the filename is implementation specific.  The correct filename in this case can be found in the system specific manuals of the target operating system.  On a FreeBSD system without CAM support, you need to use the control device (e.g.  /dev/rcd0.ctl).  A correct device specification in this case may be dev=/dev/rcd0.ctl:@ .
On Linux, drives connected to a parallel port adapter are mapped to a virtual SCSI bus. Different adapters are mapped to different targets on this virtual SCSI bus.
If no dev option is present, the program will try to get the device from the CDR_DEVICE environment.
If the argument to the dev= option does not contain the characters ',', '/', '@' or ':', it is interpreted as an label name that may be found in the file /etc/default/cdrecord (see FILES section).
The options -i and dev=target are mutual exclusive.
-debug Print additional debug information. This enables e.g. printing of all directory entries if a file has more than one directory entry and printing of more information from the primary volume descriptor.
In debug mode, Rock Ridge information is parsed with -R even if it is not standard compliant.
-l     generate output as if a 'ls -lR' command had been run on the iso9660 image.  You should not use the -f image with the -l option.
The numbers in square brackets are the starting sector number as decimal number (based on 2048 bytes per sector) and the iso9660 directory flags as hexadecimal number as follows:
0x00   A plain file (not really a flag).
0x01   Hide the file name from directory listings.
0x02   A directory.
0x04   An accociated file (e.g. an Apple resource fork).
0x08   Record format in extended attributes is used.
0x10   No read/execute permission in extended attributes.
0x20   reserved
0x40   reserved
0x80   Not the final entry of a multi extent file.
-N sector Quick hack to help examine single session disc files that are to be written to a multi-session disc. The sector number specified is the sector number at which the iso9660 image should be written when send to the cd-writer. Not used for the first session on the disc.
-p     Print path table information.
-R     Extract information from Rock Ridge extensions (if present) for permissions, file names and ownerships.
-s     Print file size infos in multiples of sector size (2048 bytes).
-J     Extract information from Joliet extensions (if present) for file names.
-j charset Convert Joliet file names (if present) to the supplied charset. See mkisofs(8) for details.
-T sector Quick hack to help examine multi-session images that have already been burned to a multi-session disc. The sector number specified is the sector number for the start of the session we wish to display.
-X     Extract files from the image and put them into the filesystem.  If the -find option is not used, all files are extracted.
The isoinfo program supports to extract all files, even multi extent files (files > 4 GB).
Before extracting files using the -X option, it is recommended to change the current directory to an empty directory in order to prevent to clobber existing files.
-x pathname Extract specified file to stdout.  The pathname needs to start with a shlash ('/') and in case of iso9660 names, must match the full pathname of the file inluding the version number (usually ';1').  If the option -R has been specified and the filesystem carries Rock Ridge attributes, the pathname must match the full Rock Ridge pathname of the file.
The author of the original sources (1993 ... 1998) is Eric Youngdale <ericy@gnu.ai.mit.edu> or <eric@andante.jic.com> is to blame for these shoddy hacks.  Joerg Schilling wrote the SCSI transport library and its adaptation layer to the programs and newer parts (starting from 1999) of the utilities, this makes them Copyright (C) 1999-2004 Joerg Schilling. Patches to improve general usability would be gladly accepted.
The user interface really sucks.
These utilities are really quick hacks, which are very useful for debugging problems in mkisofs or in an iso9660 filesystem. In the long run, it would be nice to have a daemon that would NFS export a iso9660 image.
The isoinfo program is probably the program that is of the most use to the general user.
These utilities come with the cdrtools package, and the primary download site is https://sourceforge.net/projects/cdrtools/files/ and many other mirror sites. Despite the name, the software is not beta.
CDR_DEVICE This may either hold a device identifier that is suitable to the open call of the SCSI transport library or a label in the file /etc/default/cdrecord.
RSH    If the RSH environment is present, the remote connection will not be created via rcmd(3) but by calling the program pointed to by RSH.  Use e.g.  RSH=/usr/bin/ssh to create a secure shell connection.
Note that this forces the program to create a pipe to the rsh(1) program and disallows the program to directly access the network socket to the remote server.  This makes it impossible to set up performance parameters and slows down the connection compared to a root initiated rcmd(3) connection.
RSCSI  If the RSCSI environment is present, the remote SCSI server will not be the program /opt/schily/sbin/rscsi but the program pointed to by RSCSI.  Note that the remote SCSI server program name will be ignored if you log in using an account that has been created with a remote SCSI server program as login shell.
/etc/default/cdrecord Default values can be set for the following options in /etc/default/cdrecord.
CDR_DEVICE This may either hold a device identifier that is suitable to the open call of the SCSI transport library or a label in the file /etc/default/cdrecord that allows to identify a specific drive on the system.
Any other label is an identifier for a specific drive on the system.  Such an identifier may not contain the characters ',', '/', '@' or ':'.
Each line that follows a label contains a TAB separated list of items.  Currently, four items are recognized: the SCSI ID of the drive, the default speed that should be used for this drive, the default FIFO size that should be used for this drive and drive specific options. The values for speed and fifosize may be set to -1 to tell the program to use the global defaults.  The value for driveropts may be set to "" if no driveropts are used.  A typical line may look this way:
teac1= 0,5,0   4    8m   ""
yamaha= 1,6,0  -1   -1   burnfree
This tells the program that a drive named teac1 is at scsibus 0, target 5, lun 0 and should be used with speed 4 and a FIFO size of 8 MB.  A second drive may be found at scsibus 1, target 6, lun 0 and uses the default speed and the default FIFO size.
mkisofs(8), cdrecord(1), readcd(1), scg(7), rcmd(3), ssh(1).
W3M(1)                       General Commands Manual                      W3M(1)
w3m - a text based web browser and pager
w3m [OPTION]... [ file | URL ]...
w3m is a text based browser which can display local or remote web pages as well as other documents.  It is able to process HTML tables and frames but it ignores JavaScript and Cascading Style Sheets.  w3m can also serve as a pager for text files named as arguments or passed on standard input, and as a general purpose directory browser.
w3m organizes its content in buffers or tabs, allowing easy navigation between them.  With the w3m-img extension installed, w3m can display inline graphics in web pages.  And whenever w3m's HTML rendering capabilities do not meet your needs, the target URL can be handed over to a graphical browser with a single command.
For help with runtime options, press “H” while running w3m.
When given one or more command line arguments, w3m will handle targets according to content type.  For web, w3m gets this information from HTTP headers; for relative or absolute file system paths, it relies on filenames.
With no argument, w3m expects data from standard input and assumes “text/plain” unless another MIME type is given by the user.
If provided with no target and no fallback target (see for instance option -v below), w3m will exit with usage information.
Command line options are introduced with a single “-” character and may take an argument.
General options -B     with no other target defined, use the bookmark page for startup
-M     monochrome display
-no-mouse deactivate mouse support
-num   display each line's number
-N     distribute multiple command line arguments to tabs.  By default, a stack of buffers is used
-ppc num width of num pixels per character.  Range of 4.0 to 32.0, default 8.0.  Larger values will make tables narrower.  (Implementation not verified)
-ppl num height of num pixels per line.  Range of 4.0 to 64.0. (Implementation not verified)
-title, -title=TERM use the buffer name as terminal title string.  With specified TERM, this sets the title configuration style accordingly
-v     with no other target defined, welcome users with a built-in page
-W     toggle wrapping mode in searches
-X     do not initialize/deinitialize the terminal
+num   go to line num; only effective for num larger than the number of lines in the terminal
Browser options -cols num with stdout as destination; HTML is rendered to lines of num characters
-cookie, -no-cookie use stored cookies and accept new ones, or do neither
-F     render frames
-graph, -no-graph use or do not use graphic characters for drawing HTML table and frame borders
-header string append string to the HTTP(S) request.  Expected to match the header syntax Variable: Value
-m     Render the body of Usenet messages according to the header “Content-type”
-no-proxy do not use proxy
-post file use POST method to upload data defined in file.  The syntax to be used is var1=value1[&var2=value2]...
-4     IPv4 only.  Corresponds to dns_order=4 in configuration files
-6     IPv6 only.  Corresponds to dns_order=6 in configuration files
Text pager options -l num number of lines preserved internally when receiving plain text from stdin (default 10,000)
-r     use caret notation to display special escape characters (such as ANSI escapes or nroff-style backspaces for bold and underlined characters) instead of processing them
-s     squeeze multiple blank lines into one
-t num set tab width to num columns.  No effect on stdout
Data type/encoding options -I charset user defined character encoding of input data
-O charset user defined character encoding of output data
-T type explicit characterization of input data by MIME type
Options for data output, followed by immediate exit -dump  dump rendered page into stdout.  Set implicitly when output is directed to a file or pipe
-dump_source dump the page's source code into stdout
-dump_head dump response of a HEAD request for a URL into stdout
-dump_both dump HEAD, and source code for a URL into stdout
-dump_extra dump HEAD, source code, and extra information for a URL into stdout
-help  show a summary of compiled-in features and command line options
-show-option show all available configuration options
-version show the version of w3m
Options for overriding default settings and resources -bookmark file use file instead of the default bookmark.html file
-config file use file instead of the default configuration file
-debug DO NOT USE
-o option=value modify one configuration item with an explicitly given value; without option=value, equivalent to -show-option
-reqlog log headers of HTTP communication in file ~/.w3m/request.log
Pager-like usage Combine snippets of HTML code and preview the page $ cat header.html footer.html | w3m -T text/html
Compare two files using tabs $ w3m -N config.old config
Browser-like usage Display web content in monochrome terminal $ w3m -M http://w3m.sourceforge.net
Display embedded graphics $ w3m -o auto_image=TRUE http://w3m.sourceforge.net
Display content from Usenet $ w3m -m nntp://news.aioe.org/comp.os.linux.networking
Upload data for a URL using the POST method $ w3m -post - http://example.com/form.php <<<'a=0&b=1'
Filter-like usage Convert an HTML file to plain text with a defined line length $ w3m -cols 40 foo.html > foo.txt
Output the bookmarks page as text with an appended list of links $ w3m -B -o display_link_number=1 > out.txt
Conversion of file format and character encoding $ w3m -T text/html -I EUC-JP -O UTF-8 < foo.html > foo.txt
Start with no input Welcome users with a built-in page $ w3m -v
w3m recognises the environment variable WWW_HOME as defining a fallback target for use if it is invoked without one.
~/.w3m/bookmark.html default bookmark file
~/.w3m/config user defined configuration file; overrides /etc/w3m/config
~/.w3m/cookie cookie jar; written on exit, read on launch
~/.w3m/history browser history - visited files and URLs
~/.w3m/keymap user defined key bindings; overrides default key bindings
~/.w3m/mailcap external viewer configuration file
~/.w3m/menu user defined menu; overrides default menu
~/.w3m/mime.types MIME types file
~/.w3m/mouse user defined mouse settings
~/.w3m/passwd password and username file
~/.w3m/pre_form contains predefined values to fill recurrent HTML forms
README and example files are to be found in the doc directory of your w3m installation.  Recent information about w3m may be found on the project's web pages at ⟨http://w3m.sourceforge.net⟩
w3m has incorporated code from several sources.  Users have contributed patches and suggestions over time.
Akinori ITO ⟨aito@fw.ipsj.or.jp⟩
makepasswd(1)                 UNIX Reference Manual                makepasswd(1)
makepasswd - generate and/or encrypt passwords
makepasswd [ --chars N ] [ --clearfrom file ] [ --count N ] [ --crypt | --nocrypt | --crypt-md5 ] [ --cryptsalt N ] [ --help ] [ --maxchars N ] [ --minchars N ] [ --randomseed N ] [ --rerandom N ] [ --repeatpass N ] [ --string string ] [ --verbose | --noverbose ]
makepasswd generates true random passwords using /dev/urandom, with the emphasis on security over pronounceability.  It can also encrypt plaintext passwords given on the command line.
--chars N Generate passwords with exactly N characters (do not use with options --minchars and --maxchars).
--clearfrom FILE Use password from FILE instead of generating passwords.  Requires the --crypt or the --crypt-md5 options; may not be used with these options: --chars, --maxchars, --minchars, --count, --string, --nocrypt.  Trailing newlines are removed but other white space is not.
--count N Produce a total of N passwords (the default is one).
--crypt Produce encrypted passwords.
--crypt-md5 Produce encrypted passwords using the MD5 digest (hash) algorithm.
--cryptsalt N Use crypt() salt N, a positive number <= 4096.  If random seeds are desired, specify a zero value (the default).
--help Ignore other operands and produce only a help display.
--maxchars N Generate passwords with at most N characters (default = 10).
--minchars N Generate passwords with at least N characters (default = 8).
--nocrypt Do not encrypt the generated password(s) (the default).
--noverbose Display no labels on output (the default).
--randomseed N Use random number seed N, between 0 and 2^32 inclusive.  A zero value results in a real-random seed.  This generates much less secure passwords than the default; not only does it generate predictable passwords due to the fixed seed, but the range of available seeds is 32 bits rather than the default of 256 bits, and cannot be changed without breaking expectations of previous users of this option.  If possible, do not use this option.
--rerandom N Set the random seed value every N values used.  Specify zero to use a single seed value (the default). Specify one to get true- random passwords, though note that doing this too frequently will deplete the supply of entropy available in the kernel's entropy pool.
--repeatpass N Use each password N times (4096 maximum, --crypt must be set and --cryptsalt may not be set).
--string STRING Use the characters in STRING to generate random passwords.
--verbose Display labelling information on output.
makepasswd was originally part of the mkircconf program used to centrally administer the Linux Internet Support Cooperative IRC network.  It may potentially be of use in any situation where passwords must be secure and need not be memorized by humans.
Colin Watson modified it to use Bytes::Random::Secure.
Copyright (c) 1997-1998 by lilo <lilo@linpeople.org>.  All rights are reserved by the author.  This program may be used under the terms of version 2 of the GNU Public License.
passwd(5)
GIT-COMMIT-GRAPH(1)                Git Manual                GIT-COMMIT-GRAPH(1)
git-commit-graph - Write and verify Git commit-graph files
git commit-graph verify [--object-dir <dir>] [--shallow] [--[no-]progress] git commit-graph write <options> [--object-dir <dir>] [--[no-]progress]
Manage the serialized commit-graph file.
--object-dir Use given directory for the location of packfiles and commit-graph file. This parameter exists to specify the location of an alternate that only has the objects directory, not a full .git directory. The commit-graph file is expected to be in the <dir>/info directory and the packfiles are expected to be in <dir>/pack. If the directory could not be made into an absolute path, or does not match any known object directory, git commit-graph ...  will exit with non-zero status.
--[no-]progress Turn progress on/off explicitly. If neither is specified, progress is shown if standard error is connected to a terminal.
write Write a commit-graph file based on the commits found in packfiles. If the config option core.commitGraph is disabled, then this command will output a warning, then return success without writing a commit-graph file.
With the --stdin-packs option, generate the new commit graph by walking objects only in the specified pack-indexes. (Cannot be combined with --stdin-commits or --reachable.)
With the --stdin-commits option, generate the new commit graph by walking commits starting at the commits specified in stdin as a list of OIDs in hex, one OID per line. OIDs that resolve to non-commits (either directly, or by peeling tags) are silently ignored. OIDs that are malformed, or do not exist generate an error. (Cannot be combined with --stdin-packs or --reachable.)
With the --reachable option, generate the new commit graph by walking commits starting at all refs. (Cannot be combined with --stdin-commits or --stdin-packs.)
With the --append option, include all commits that are present in the existing commit-graph file.
With the --changed-paths option, compute and write information about the paths changed between a commit and its first parent. This operation can take a while on large repositories. It provides significant performance gains for getting history of a directory or a file with git log -- <path>. If this option is given, future commit-graph writes will automatically assume that this option was intended. Use --no-changed-paths to stop storing this data.
With the --max-new-filters=<n> option, generate at most n new Bloom filters (if --changed-paths is specified). If n is -1, no limit is enforced. Only commits present in the new layer count against this limit. To retroactively compute Bloom filters over earlier layers, it is advised to use --split=replace. Overrides the commitGraph.maxNewFilters configuration.
With the --split[=<strategy>] option, write the commit-graph as a chain of multiple commit-graph files stored in <dir>/info/commit-graphs. Commit-graph layers are merged based on the strategy and other splitting options. The new commits not already in the commit-graph are added in a new "tip" file. This file is merged with the existing file if the following merge conditions are met:
•   If --split=no-merge is specified, a merge is never performed, and the remaining options are ignored.  --split=replace overwrites the existing chain with a new one. A bare --split defers to the remaining options. (Note that merging a chain of commit graphs replaces the existing chain with a length-1 chain where the first and only incremental holds the entire graph).
•   If --size-multiple=<X> is not specified, let X equal 2. If the new tip file would have N commits and the previous tip has M commits and X times N is greater than M, instead merge the two files into a single file.
•   If --max-commits=<M> is specified with M a positive integer, and the new tip file would have more than M commits, then instead merge the new tip with the previous tip.
Finally, if --expire-time=<datetime> is not specified, let datetime be the current time. After writing the split commit-graph, delete all unused commit-graph whose modified times are older than datetime.
verify Read the commit-graph file and verify its contents against the object database. Used to check for corrupted data.
With the --shallow option, only check the tip commit-graph file in a chain of split commit-graphs.
•   Write a commit-graph file for the packed commits in your local .git directory.
$ git commit-graph write
•   Write a commit-graph file, extending the current commit-graph file using commits in <pack-index>.
$ echo <pack-index> | git commit-graph write --stdin-packs
•   Write a commit-graph file containing all reachable commits.
$ git show-ref -s | git commit-graph write --stdin-commits
•   Write a commit-graph file containing all commits in the current commit-graph file along with those reachable from HEAD.
$ git rev-parse HEAD | git commit-graph write --stdin-commits --append
PLAYERCTL(1)               BSD General Commands Manual              PLAYERCTL(1)
playerctl — control media players via MPRIS
playerctl [-aFhlV] [-f FORMAT] [-i NAME] [-p NAME] command
The playerctl utility controls MPRIS-enabled media players.  In addition to offering play, pause and stop control, playerctl also offers previous and next track support, the ability to seek backwards and forwards in a track, and volume control.  playerctl also supports displaying metadata (e.g., artist, title, album) for the current track, and showing the status of the player.
Players that can be controlled using playerctl include audacious(1), cmus(1), mopidy(1), mpd(1), quodlibet(1), rhythmbox(1), vlc(1) and xmms2(1).  However, any player that implements the MPRIS interface specification can be controlled using playerctl including web browsers.
Playerctl also comes with a daemon called playerctld which keeps track of media player activity. When playerctld is running, playerctl commands will act on the media player with the most recent activity.  Run the command playerctld daemon to start the daemon.
-a, --all-players Apply command to all available players.
-F, --follow Block and output the updated query when it changes.
-f FORMAT, --format FORMAT Set the output of the current command to FORMAT.  See Format Strings.
-h, --help Print this help, then exit.
-i NAME, --ignore-player NAME Ignore the specific player NAME.  Multiple players can be specified in a comma-separated list.
-l, --list-all List the names of running players that can be controlled.
-p NAME, --player NAME Control the specific player NAME.  Multiple players can be specified in a comma-separated list.  Defaults to the first available player.  The name "name" matches both "name" and "name.{INSTANCE}".  Additionally, the name "%any" matches any player.
-s, --no-messages Silence some diagnostic and error messages.
-V, --version Print version number, then exit.
The commands are as follows:
status  Get the current status of the player.
play    Command the player to play.
pause   Command the player to pause.
play-pause Command the player to toggle between play and pause.
stop    Command the player to stop.
next    Command the player to skip to the next track.
previous Command the player to skip to the previous track.
position [OFFSET[+|-]] Print the position of the current track in seconds.  With OFFSET specified, seek to OFFSET seconds from the start of the current track.  With the optional [+|-] appended, seek forward or backward OFFSET seconds from the current position.
volume [LEVEL[+|-]] Print the player's volume scaled from 0.0 (0%) to 1.0 (100%).  With LEVEL specified, set the player's volume to LEVEL.  With the optional [+|-] appended, increase or decrease the player's volume by LEVEL.
metadata [KEY] Print all metadata properties for the current track set by the current player.  If KEY is specified only the value of KEY is printed.
open URI Open URI in the player.  URI may be the name of a file or an external URL.
shuffle [On | Off | Toggle] Print the shuffle status of the player.  With the shuffle status specified, set the shuffle status to either On , Off , or Toggle
loop [None | Track | Playlist] Print the loop status of the player.  With the loop status specified, set the loop status to None (disable looping), Track (loop the current track), or Playlist (loop the current playlist).
Format Strings The output of the position, metadata, status and volume commands can be controlled using a format string.  Variables set by these commands can be included in the format string by enclosing them in curly braces: ‘{{var}}’. These will then be expanded on output.
Each command has access to the following variables:
playerName The name of the current player.
position The time position of the current track, in microseconds.
status  The status of the current player.
volume  The player's volume scaled from 0.0 (0%) to 1.0 (100%).
Each property listed in the metadata command are also set as variables.  It is recommended to check this list for each player, as different players may not set the same properties.  See the MPRIS v2 metadata guidelines for a list of all properties in the MPRIS specification.  The most common properties are as follows:
album, xesam:album The album of the current track.
artist, xesam:artist The artist of the current track.
title, xesam:title The title of the current track.
Helper functions are also available to transform expanded variables into other representations.  They are called in the form ‘{{func(var)}}’.  The helper functions are as follows:
lc(str) Convert string str to lowercase.
uc(str) Convert string str to uppercase.
markup_escape(str) Escape XML characters in string str.
default(str1, str2) Print str1 if set, else print str2.
duration(time) Reformat the microsecond timestamp time in the form ‘hh:mm:ss’. Can only be called with position or mpris:length.
emoji(key) Try to convert the value for key to an emoji representation. Currently implemented for status and volume.
trunc(str, len) Truncate str to a maximum of len characters, adding an ellipsis (…) if necessary.
The template language is also able to perform basic math operations.
References to unknown functions will cause playerctl to exit with an error. References to unknown variables will be expanded to empty strings.  Text not enclosed in braces will be printed verbatim.
The playerctl utility exits 0 on success, and >0 if an error occurs.
Print the player name, playback status in lowercase, and position and length in human readable form:
$ playerctl metadata --format '{{playerName}}: {{lc(status)}} '\ '{{duration(position)}}|{{duration(mpris:length)}}'
MPRIS v2 metadata guidelines, freedesktop.org, https://freedesktop.org/wiki/Specifications/mpris-spec/metadata/, September 18, 2013.
playerctl homepage: https://github.com/altdesktop/playerctl, playerctl API documentation: https://dubstepdish.com/playerctl, GObject introspection language bindings: https://wiki.gnome.org/Projects/GObjectIntrospection/Users
The playerctl utility is maintained by Tony Crisci <tony@dubstepdish.com> and is made available under the GNU Lesser General Public License 3.0.
This reference was written by Nick Morrott <knowledgejunkie@gmail.com> for the Debian GNU/Linux project.  It was later updated and expanded by Stephen Gregoratto <dev@sgregoratto.me>.
KSCREEN-CONSOLE(1)               KScreen Console              KSCREEN-CONSOLE(1)
kscreen-console - lists monitor and screen configuration and their changes
kscreen-console [Qt-options] [KDE-options] [options] [arg(s)]
KScreen-console lists the current monitor setup and screen configuration (like xrandr --verbose). Then kscreen-console waits for further screen/monitor events and lists them. You can exit the program with Ctrl-C
Arguments: arg(s) Arguments for command
Options: --commands Show available commands
Generic options: --help Show help about options
--help-qt Show Qt specific options
--help-kde Show KDE specific options
--help-all Show all options
--author Show author information
-v, --version Show version information
--license Show license information
--     End of options
KDE options: --caption <caption> Use 'caption' as name in the titlebar
--icon <icon> Use 'icon' as the application icon
--config <filename> Use alternative configuration file
--nocrashhandler Disable crash handler, to get core dumps
--waitforwm Waits for a WM_NET compatible windowmanager
--style <style> sets the application GUI style
--geometry <geometry> sets the client geometry of the main widget - see man X for the argument format (usually WidthxHeight+XPos+YPos)
Qt options: --display <displayname> Use the X-server display 'displayname'
--session <sessionId> Restore the application for the given 'sessionId'
--cmap Causes the application to install a private color map on an 8-bit display
--ncols <count> Limits the number of colors allocated in the color cube on an 8-bit display, if the application is using the QApplication::ManyColor color specification
--nograb tells Qt to never grab the mouse or the keyboard
--dograb running under a debugger can cause an implicit --nograb, use --dograb to override
--sync switches to synchronous mode for debugging
--fn, --font <fontname> defines the application font
--bg, --background <color> sets the default background color and an application palette (light and dark shades are calculated)
--fg, --foreground <color> sets the default foreground color
--btn, --button <color> sets the default button color
--name <name> sets the application name
--title <title> sets the application title (caption)
--testability load the testability framework
--visual TrueColor forces the application to use a TrueColor visual on an 8-bit display
--inputstyle <inputstyle> sets XIM (X Input Method) input style. Possible values are onthespot, overthespot, offthespot and root
--im <XIM server> set XIM server
--noxim disable XIM
--reverse mirrors the whole layout of widgets
--stylesheet <file.qss>   applies the Qt stylesheet to the application widgets
--graphicssystem <system> use a different graphics system instead of the default one, options are raster and opengl (experimental)
--qmljsdebugger <port> QML JS debugger information. Application must be built with -DQT_DECLARATIVE_DEBUG for the debugger to be enabled
kdeoptions(7), qtoptions(7)
Alejandro Fiestas Olivares <afiestas@kde.org>
Manual page written by Achim Bohnet <allee@kubuntu.org>
nix-env(1)                   General Commands Manual                  nix-env(1)
Name nix-env - manipulate or query Nix user environments
Synopsis nix-env [--option name value] [--arg name value] [--argstr name value] [{--file | -f} path] [{--profile | -p} *path(] [--system-filter system] [--dry-run] operation [options…] [arguments…]
Description The command nix-env is used to manipulate Nix user environments. User environments are sets of software packages available to a user at some point in time. In other words, they are a synthesised view of the programs available in the Nix store. There may be many user environments: different users can have different environments, and individual users can switch between different environments.
nix-env takes exactly one operation flag which indicates the subcommand to be performed. These are documented below.
Selectors Several commands, such as nix-env -q and nix-env -i, take a list of arguments that specify the packages on which to operate. These are extended regular expressions that must match the entire name of the package. (For details on regular expressions, see regex7.) The match is case-sensitive. The regular expression can optionally be followed by a dash and a version number; if omitted, any version of the package will match. Here are some examples:
• firefox Matches the package name firefox and any version.
• firefox-32.0 Matches the package name firefox and version 32.0.
• gtk\\+ Matches the package name gtk+. The + character must be escaped using a backslash to prevent it from being interpreted as a quantifier, and the backslash must be escaped in turn with another backslash to ensure that the shell passes it on.
• .\* Matches any package name. This is the default for most commands.
• '.*zip.*' Matches any package name containing the string zip. Note the dots: '*zip*' does not work, because in a regular expression, the character * is interpreted as a quantifier.
• '.*(firefox|chromium).*' Matches any package name containing the strings firefox or chromium.
Common options This section lists the options that are common to all operations. These options are allowed for every subcommand, though they may not always have an effect.
• --file / -f path Specifies the Nix expression (designated below as the active Nix expression) used by the --install, --upgrade, and --query --available operations to obtain derivations. The default is ~/.nix-defexpr.
If the argument starts with http:// or https://, it is interpreted as the URL of a tarball that will be downloaded and unpacked to a temporary location. The tarball must include a single top-level directory containing at least a file named default.nix.
• --profile / -p path Specifies the profile to be used by those operations that operate on a profile (designated below as the active profile). A profile is a sequence of user environments called generations, one of which is the current generation.
• --dry-run For the --install, --upgrade, --uninstall, --switch-generation, --delete-generations and --rollback operations, this flag will cause nix-env to print what would be done if this flag had not been specified, without actually doing it.
--dry-run also prints out which paths will be substituted (../glossary.md) (i.e., downloaded) and which paths will be built from source (because no substitute is available).
• --system-filter system By default, operations such as --query --available show derivations matching any platform. This option allows you to use derivations for the specified platform system.