neulab/tldr huggingface dataset:
--docker-env-metadata-whitelist=""      a comma-separated list of environment variable keys matched with specified prefix that needs to be collected for docker containers
--docker-only=false      Only report docker containers in addition to root stats
--docker-root="/var/lib/docker"      DEPRECATED: docker root is read from docker info (this is a fallback, default: /var/lib/docker)
--docker-tls=false      use TLS to connect to docker
--docker-tls-ca="ca.pem"      path to trusted CA
--docker-tls-cert="cert.pem"      path to client certificate
--docker-tls-key="key.pem"      path to private key
--enable-load-reader=false      Whether to enable cpu load reader
--event-storage-age-limit="default=0"      Max length of time for which to store events (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is a duration. Default is applied to all non-specified event types
--event-storage-event-limit="default=0"      Max number of events to store (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is an integer. Default is applied to all non-specified event types
--global-housekeeping-interval=1m0s      Interval between global housekeepings
--housekeeping-interval=10s      Interval between container housekeepings
--insecure-skip-tls-verify=false      If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
--kubeconfig=""      Path to the kubeconfig file to use for CLI requests.
--log-backtrace-at=:0      when logging hits line file:N, emit a stack trace
--log-cadvisor-usage=false      Whether to log the usage of the cAdvisor container
--log-dir=""      If non-empty, write log files in this directory
--log-file=""      If non-empty, use this log file
--log-file-max-size=1800      Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited.
--log-flush-frequency=5s      Maximum number of seconds between log flushes
--logtostderr=true      log to standard error instead of files
--machine-id-file="/etc/machine-id,/var/lib/dbus/machine-id" Comma-separated list of files to check for machine-id. Use the first one that exists.
--match-server-version=false      Require server version to match client version
-n, --namespace=""      If present, the namespace scope for this CLI request
--one-output=false      If true, only write logs to their native severity level (vs also writing to each lower severity level)
--password=""      Password for basic authentication to the API server
--profile="none"      Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex)
--profile-output="profile.pprof"      Name of the file to write the profile to
--referenced-reset-interval=0      Reset interval for referenced bytes (container_referenced_bytes metric), number of measurement cycles after which referenced bytes are cleared, if set to 0 referenced bytes are never cleared (default: 0)
--request-timeout="0"      The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.
-s, --server=""      The address and port of the Kubernetes API server
--skip-headers=false      If true, avoid header prefixes in the log messages
--skip-log-headers=false      If true, avoid headers when opening log files
--stderrthreshold=2      logs at or above this threshold go to stderr
--storage-driver-buffer-duration=1m0s      Writes in the storage driver will be buffered for this duration, and committed to the non memory backends as a single transaction
--storage-driver-db="cadvisor"      database name
--storage-driver-host="localhost:8086"      database host:port
--storage-driver-password="root"      database password
--storage-driver-secure=false      use secure connection with database
--storage-driver-table="stats"      table name
--storage-driver-user="root"      database username
--tls-server-name=""      Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
--token=""      Bearer token for authentication to the API server
--update-machine-info-interval=5m0s      Interval between machine info updates.
--user=""      The name of the kubeconfig user to use
--username=""      Username for basic authentication to the API server
-v, --v=0      number for the log level verbosity
--version=false      Print version information and quit
--vmodule=      comma-separated list of pattern=N settings for file-filtered logging
--warnings-as-errors=false      Treat warnings received from the server as errors and exit with a non-zero exit code
# Return snapshot logs from pod nginx with only one container kubectl logs nginx
# Return snapshot logs from pod nginx with multi containers kubectl logs nginx --all-containers=true
# Return snapshot logs from all containers in pods defined by label app=nginx kubectl logs -l app=nginx --all-containers=true
# Return snapshot of previous terminated ruby container logs from pod web-1 kubectl logs -p -c ruby web-1
# Begin streaming the logs of the ruby container in pod web-1 kubectl logs -f -c ruby web-1
# Begin streaming the logs from all containers in pods defined by label app=nginx kubectl logs -f -l app=nginx --all-containers=true
# Display only the most recent 20 lines of output in pod nginx kubectl logs --tail=20 nginx
# Show all logs from pod nginx written in the last hour kubectl logs --since=1h nginx
# Show logs from a kubelet with an expired serving certificate kubectl logs --insecure-skip-tls-verify-backend nginx
# Return snapshot logs from first container of a job named hello kubectl logs job/hello
# Return snapshot logs from container nginx-1 of a deployment named nginx kubectl logs deployment/nginx -c nginx-1
kubectl(1),
January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!
yacas(1)                     General Commands Manual                    yacas(1)
yacas, yacas_client â€” small and flexible general-purpose computer algebra system
yacas [options]  [{filename}]
This manual page documents briefly the yacas and yacas_client commands.
Yacas (Yet Another Computer Algebra System) is a small and highly flexible general-purpose computer algebra language. The syntax uses a infix-operator grammar parser. The distribution contains a small library of mathematical functions, but its real strength is in the language in which you can easily write your own symbolic manipulation algorithms. The core engine supports arbitrary precision arithmetic, and is linked with the GNU arbitrary precision math library, and is able to execute symbolic manipulations on various mathematical objects by following user- defined rules.
This manual page was written for the Debian GNU/Linux distribution because the original program does not have a manual page.
A summary of options is given below
-c        Inhibit printing of prompts "In>" and "Out>". Useful for non- interactive sessions.
-f        Reads standard input as one file, but executes only the first statement in it. (You may want to use a statement block to have several statements executed.)
-p        Does not use terminal capabilities, no fancy editing on the command line and no escape sequences printed. Useful for non- interactive sessions.
-t        Enable some extra history recall functionality in console mode: after executing a command from the history list, the next unmodified command from the history list will be automatically entered on the command line.
{filename} Reads and executes commands in the filename and exits. Equivalent to "Load()".
-v        Prints version information and exits.
-d        Prints the path to the Yacas library directory and exits
The default operation of  Yacas is to run in the interactive console mode. Yacas accepts several options that modify its operation.  Options can be combined.
In addition to the console mode, an experimental persistent session facility is provided through the script yacas_client. By means of this script, the user can configure third-party applications to pass commands to a constantly running "Yacas server" and get output.  The "Yacas server" is automatically started by yacas_client. It may run on a remote computer; in that case the user should have a user account on the remote computer and privileges to execute yacas_client there, as well as rsh or ssh access. The purpose of yacas_client is to enable users to pass commands to Yacas within a persistent session while running another application such as a text editor.
The script yacas_client reads yacas commands from the standard input and passes them to the running "Yacas server"; it then waits 2 seconds and prints whatever output yacas produced up to this time. Usage may looks like this:
8:20pm Unix>echo "x:=3" | yacas_client Starting server. [editvi] [gnuplot] True; To exit Yacas, enter  Exit(); or quit or Ctrl-c. Type ?? for help. Or type ?function for help on a function. Type 'restart' to restart Yacas. To see example commands, keep typing Example(); In> x:=3 Out> 3; In> 8:21pm Unix>echo "x:=3+x" | yacas_client In> x:=3+x Out> 6; In> 8:23pm Unix>yacas_client -stop In> quit Quitting... Server stopped. 8:23pm Unix>
Persistence of the session means that yacas remembered the value of "x" between invocations of yacas_client. If there is not enough time for Yacas to produce output within 2 seconds, the output will be displayed the next time you call yacas_client.
The "Yacas server" is started automatically when first used and can be stopped either by quitting yacas or by an explicit option yacas_client -stop, in which case yacas_client does not read standard input.
The script yacas_client reads standard input and writes to standard output, so it can be used via remote shell execution. For instance, if an account "user" on a remote computer "remote.host" is accessible through ssh, then yacas_client can be used remotely like this:
echo "x:=2;" | ssh user@remote.host yacas_client
On a given host computer running the "Yacas server", each user currently may have only one persistent Yacas session.
/usr/share/yacas/documentation/books.html (link to URL file:/usr/share/yacas/documentation/books.html)        or http://www.xs4all.nl/~apinkus/manindex.html (link to URL http://www.xs4all.nl/~apinkus/manindex.html)  for more information.
yacas was written by Ayal Pinkus (apinkus@xs4all.nl). yacas is available at http://www.xs4all.nl/~apinkus/yacas.html (link to URL http://www.xs4all.nl/~apinkus/yacas.html) .
This manual page was written by Gopal Narayanan (gopal@debian.org) for the Debian GNU/Linux system (but may be used by others).
LRZUNTAR.1(1)          User Contributed Perl Documentation         LRZUNTAR.1(1)
lrzuntar - Extract whole tarball from .tar.lrz files
lrzuntar [options] DIRECTORY.tar.lrz
lrzuntar is identical to "lrztar -d" used to decompress lrzip compressed tarballs.
See lrzip(1)
lrzip.conf(5), lrztar(1), lrzip(1), lrunzip(1), lrzcat(1), lrz(1), bzip2(1), gzip(1), lzop(1), rzip(1), zip(1)
This manual page was written by Con Kolivas <kernel@kolivas.org> (but may be used by others). Released under license GNU GPL version 2 or (at your option) any later version. For more information about license, visit <http://www.gnu.org/copyleft/gpl.html>.
UNIQ(1P)                    POSIX Programmer's Manual                   UNIQ(1P)
uniq — report or filter out repeated lines in a file
uniq [-c|-d|-u] [-f fields] [-s char] [input_file [output_file]]
The uniq utility shall read an input file comparing adjacent lines, and write one copy of each input line on the output. The second and succeeding copies of repeated adjacent input lines shall not be written. The trailing <newline> of each line in the input shall be ignored when doing comparisons.
Repeated lines in the input shall not be detected if they are not adjacent.
The uniq utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines, except that '+' may be recognized as an option delimiter as well as '-'.
-c        Precede each output line with a count of the number of times the line occurred in the input.
-d        Suppress the writing of lines that are not repeated in the input.
-f fields Ignore the first fields fields on each input line when doing comparisons, where fields is a positive decimal integer. A field is the maximal string matched by the basic regular expression:
[[:blank:]]*[^[:blank:]]*
If the fields option-argument specifies more fields than appear on an input line, a null string shall be used for comparison.
-s chars  Ignore the first chars characters when doing comparisons, where chars shall be a positive decimal integer. If specified in conjunction with the -f option, the first chars characters after the first fields fields shall be ignored. If the chars option-argument specifies more characters than remain on an input line, a null string shall be used for comparison.
-u        Suppress the writing of lines that are repeated in the input.
input_file A pathname of the input file. If the input_file operand is not specified, or if the input_file is '-', the standard input shall be used.
output_file A pathname of the output file. If the output_file operand is not specified, the standard output shall be used. The results are unspecified if the file named by output_file is the file named by input_file.
The standard input shall be used only if no input_file operand is specified or if input_file is '-'.  See the INPUT FILES section.
The input file shall be a text file.
The following environment variables shall affect the execution of uniq:
LC_CTYPE  Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files) and which characters constitute a <blank> in the current locale.
The standard output shall be used if no output_file operand is specified, and shall be used if the output_file operand is '-' and the implementation treats the '-' as meaning standard output. Otherwise, the standard output shall not be used.  See the OUTPUT FILES section.
If the -c option is specified, the output file shall be empty or each line shall be of the form:
"%d %s", <number of duplicates>, <line>
otherwise, the output file shall be empty or each line shall be of the form:
"%s", <line>
0    The utility executed successfully.
If the collating sequence of the current locale has a total ordering of all characters, the sort utility can be used to cause repeated lines to be adjacent in the input file. If the collating sequence does not have a total ordering of all characters, the sort utility should still do this but it might not. To ensure that all duplicate lines are eliminated, and have the output sorted according the collating sequence of the current locale, applications should use:
LC_ALL=C sort -u | sort
To remove duplicate lines based on whether they collate equally instead of whether they are identical, applications should use:
When using uniq to process pathnames, it is recommended that LC_ALL, or at least LC_CTYPE and LC_COLLATE, are set to POSIX or C in the environment, since pathnames can contain byte sequences that do not form valid characters in some locales, in which case the utility's behavior would be undefined. In the POSIX locale each byte is a valid single-byte character, and therefore this problem is avoided.
The following input file data (but flushed left) was used for a test series on uniq:
#01 foo0 bar0 foo1 bar1 #02 bar0 foo1 bar1 foo1 #03 foo0 bar0 foo1 bar1 #04 #05 foo0 bar0 foo1 bar1 #06 foo0 bar0 foo1 bar1 #07 bar0 foo1 bar1 foo0
What follows is a series of test invocations of the uniq utility that use a mixture of uniq options against the input file data. These tests verify the meaning of adjacent.  The uniq utility views the input data as a sequence of strings delimited by '\n'.  Accordingly, for the fieldsth member of the sequence, uniq interprets unique or repeated adjacent lines strictly relative to the fields+1th member.
1. This first example tests the line counting option, comparing each line of the input file data starting from the second field:
uniq -c -f 1 uniq_0I.t 1 #01 foo0 bar0 foo1 bar1 1 #02 bar0 foo1 bar1 foo1 1 #03 foo0 bar0 foo1 bar1 1 #04 2 #05 foo0 bar0 foo1 bar1 1 #07 bar0 foo1 bar1 foo0
The number '2', prefixing the fifth line of output, signifies that the uniq utility detected a pair of repeated lines. Given the input data, this can only be true when uniq is run using the -f 1 option (which shall cause uniq to ignore the first field on each input line).
2. The second example tests the option to suppress unique lines, comparing each line of the input file data starting from the second field:
uniq -d -f 1 uniq_0I.t #05 foo0 bar0 foo1 bar1
3. This test suppresses repeated lines, comparing each line of the input file data starting from the second field:
uniq -u -f 1 uniq_0I.t #01 foo0 bar0 foo1 bar1 #02 bar0 foo1 bar1 foo1 #03 foo0 bar0 foo1 bar1 #04 #07 bar0 foo1 bar1 foo0
4. This suppresses unique lines, comparing each line of the input file data starting from the third character:
uniq -d -s 2 uniq_0I.t
In the last example, the uniq utility found no input matching the above criteria.
Some historical implementations have limited lines to be 1080 bytes in length, which does not meet the implied {LINE_MAX} limit.
Earlier versions of this standard allowed the -number and +number options. These options are no longer specified by POSIX.1‐2008 but may be present in some implementations.
comm, sort
topydo(1)                                                              topydo(1)
topydo - An advanced todo.txt terminal utility for managing tasks
SYNOPSIS topydo [-ahv] [-c <config>] [-C <colormode>] [-d <archive>] [-t <todo.txt>] subcommand [help|args]
topydo [--info]
DESCRIPTION This is a command line tool for managing and displaying tasking information.
Tasks are stored in a plain text file using the todo.txt format.  There are a number of tools, across operating systems, that support collaboratively managing a common tasking file.
OPTIONS -info  Print out current configuration information for topydo, including the path the executable and the tasking file.
-a     Do not archive todo items on completion.
-c     Specify an alternative configuration file.
-C     Specify color mode (0 = disable, 1 = enable 16 colors, 16 = enable 16 colors, 256 = enable 256 colors, auto (default))
-d     Specify an alternative archive file (done.txt)
-h     This help text
-t     Specify and alternative todo file
-v     Print the version and exit
BUILT-IN ACTIONS Run "topydo help <subcommand> for additional help.
• add|a “THING I NEED TO DO +project @context”
Adds THING I NEED TO DO to your todo.txt file on its own line.
Project and context notation optional.
Quotes optional.
• append|app ITEM# “TEXT TO APPEND”
app ITEM# "TEXT TO APPEND"
Adds TEXT TO APPEND to the end of the task on line ITEM#.
• del|rm ITEM# [TERM]
Deletes the task on line ITEM# in todo.txt.
If TERM specified, deletes only TERM from the task.
• depri|dp ITEM#[, ITEM#, ITEM#, ...]
Deprioritizes (removes the priority) from the task(s)
on line ITEM# in todo.txt.
• do ITEM#[, ITEM#, ITEM#, ...]
Marks task(s) on line ITEM# as done in todo.txt.
• ls [TERM...]
Displays all tasks that contain TERM(s) sorted by priority with line numbers.  Each task must match all TERM(s) (logical AND); to display tasks that contain any TERM (logical OR), use “TERM1|TERM2|...” (with quotes), or TERM1\|TERM2 (unquoted).  Hides all tasks that contain TERM(s) preceded by a minus sign (i.e. -TERM).  If no TERM specified, lists entire todo.txt.
• listcon|lscon [TERM...]
Lists all the task contexts that start with the @ sign in todo.txt.  If TERM specified, considers only tasks that contain TERM(s).
• listprojexts|lsprj [TERM...]
Lists all the projects (terms that start with a + sign) in todo.txt. If TERM specified, considers only tasks that contain TERM(s).
• postpone ITEM# Postpone the task.
• pri ITEM# PRIORITY
Adds PRIORITY to task on line ITEM#.  If the task is already prioritized, replaces current priority with new PRIORITY.  PRIORITY must be a letter between A and Z.
• revert ITEM#
Revert a previous task.
TODO.TXT TASK FORMAT A todo.txt task is a single line of text, which may contain specially notated words to define metadata for the task.  These tags are all optional.
• (<PRIORITY>)
A task priority can be defined by prepending a single letter in parenthesis, followed by a space.  By convention, capital letters are used, with `A' denoting the highest priority.
• +<PROJECT>
A word in the task beginning with “+” defines the project associated with the task.  This provides a means to group tasks according to the tasks assocated with a particular effort.
• @<CONTEXT>
A word in the task beginning with the “@” character defines the context associated with the task.  Possible contexts are @phone, @email, or @home.  This provides a means to group tasks according to the context of when they can be completed.
• due:<yyyy-mm-dd>
Define the due date of the task.
• x <TASK>
A task may be marked complete by prepending an “x” followed by a space. This is used by the utility to remove tasks from active task lists without affecting the line numbers of the remaining tasks.
A task may also contain one or two bare dates that define the creation and completion date of the task.  A completed task should have the completion date following the “x”.
The core todo.txt format is described in full at https://github.com/todotxt/todo.txt.
The format is extended by topydo with the following features:
• rec:[+][n][d|w|m|y]
Recur a task upon completion.  The + indicates strict recurrance, which bases the new date on the due date.  Otherwise, the closing date is used.
• t:<yyy-mm-dd>
The threshold, or start date.  Tasks with a threshold date in the future are generally not shown.
CONFIGURATION FILE Configuration files may be stored in the following locations:
• /etc/topydo.conf
• ~/.config/topydo/config
• ~/.topydo
• .topydo (in the current working directory)
• topydo.conf (in the current working directoy)
• topydo.ini (in the current working directoy)
The files are read in that order, with variables in later files overriding earlier ones.
See the Configuration topic in /usr/share/doc/topydo/docs/index.html for detail on the configuration file format and variables.
SEE ALSO todo.txt(1), topydo.conf(5), vitodo(1), edittodo(1), listtodo(1), todo.txt-base(8)
The file /usr/share/doc/topydo/docs/index.html contains extensive information about topydo, including the configuration file format.
GOPASS(1)                         User Commands                        GOPASS(1)
gopass - The standard Unix password manager
gopass [global options] command [command options] [,arguments...]
--alsoclip, --C, Copy the password and show everything
--clip, --c, Copy the password value into the clipboard
--noparsing, --n, Do not parse the output.
--password, --o, Display only the password. Takes precedence over all other flags.
--qr,  Print the password as a QR Code
--revision, Show a past revision. Does NOT support RCS specific shortcuts. Use exact revision or -N to select the Nth oldest revision of this entry.
--unsafe, --u, --force, --f, Display unsafe content (e.g. the password) even if safecontent is enabled
--yes, --y, Always answer yes to yes/no questions
alias Manage domain aliases
Manages domain aliases. Note: this command might change or go away.
audit Decrypt all secrets and scan for weak or leaked passwords
This command decrypts all secrets and checks for common flaws and (optionally) against a list of previously leaked passwords.
cat Print content of a secret to stdout, or insert from stdin
This command is similar to the way cat works on the command line. It can either be used to retrieve the decoded content of a secret similar to 'cat file' or vice versa to encode the content from STDIN to a secret.
clone Clone a password store from a git repository
This command clones an existing password store from a git remote to a local password store. Can be either used to initialize a new root store or to add a new mounted sub-store.Needs at least one argument (git URL) to clone from. Accepts a second argument (mount location) to clone and mount a sub-store, e.g. 'gopass clone git@example.com/store.git foo/bar'
--crypto, Select crypto backend [age]
--path, Path to clone the repo to
config Display and edit the configuration file
This command allows for easy printing and editing of the configuration. Without argument, the entire config is printed. With a single argument, a single key can be printed. With two arguments a setting specified by key can be set to value.
convert Convert a store to different backends
Convert a store to a different set of backends
--crypto, Which crypto backend? [age]
--move, Replace store?
--storage, Which storage backend? []
--store, Specify which store to convert
copy Copy secrets from one location to another
This command copies an existing secret in the store to another location. This also works across different sub-stores. If the source is a directory it will automatically copy recursively. In that case, the source directory is re-created at the destination if no trailing slash is found, otherwise the contents are flattened (similar to rsync).
--force, --f, Force to copy the secret and overwrite existing one
create Easy creation of new secrets
This command starts a wizard to aid in creation of new secrets.
--force, --f, Force path selection
--store, --s, Which store to use
delete Remove one or many secrets from the store
This command removes secrets. It can work recursively on folders. Recursing across stores is purposefully not supported.
--force, --f, Force to delete the secret
--recursive, --r, Recursive delete files and folders
edit Edit new or existing secrets
Use this command to insert a new secret or edit an existing one using your $EDITOR. It will attempt to create a secure temporary directory for storing your secret while the editor is accessing it. Please make sure your editor doesn't leak sensitive data to other locations while editing. Note: If $EDITOR is not set we will try 'editor'. If that's not available either we fall back to 'vi'. Consider using 'update-alternatives --config editor to change the defaults.
--create, --c, Create a new secret if none found
--editor, --e, Use this editor binary
env Run a subprocess with a pre-populated environment
This command runs a sub process with the environment populated from the keys of a secret.
find Search for secrets
This command will first attempt a simple pattern match on the name of the secret.  If there is an exact match it will be shown directly; if there are multiple matches, a selection will be shown.
--clip, --c, Copy the password into the clipboard
--unsafe, --u, --force, --f, In the case of an exact match, display the password even if safecontent is enabled
fsck Check store integrity
Check the integrity of the given sub-store or all stores if none are specified. Will automatically fix all issues found.
--decrypt, Decrypt and reencryt during fsck.  WARNING: This will update the secret content to the latest format. This might be incompatible with other implementations. Use with caution!
fscopy Copy files from or to the password store
This command either reads a file from the filesystem and writes the encoded and encrypted version in the store or it decrypts and decodes a secret and writes the result to a file. Either source or destination must be a file and the other one a secret. If you want the source to be securely removed after copying, use 'gopass binary move'
fsmove Move files from or to the password store
This command either reads a file from the filesystem and writes the encoded and encrypted version in the store or it decrypts and decodes a secret and writes the result to a file. Either source or destination must be a file and the other one a secret. The source will be wiped from disk or from the store after it has been copied successfully and validated. If you don't want the source to be removed use 'gopass binary copy'
generate Generate a new password
Dialog to generate a new password and write it into a new or existing secret. By default, the new password will replace the first line of an existing secret (or create a new one).
--clip, --c, Copy the generated password to the clipboard
--edit, --e, Open secret for editing after generating a password
--force, --f, Force to overwrite existing password
--generator, --g, Choose a password generator, use one of: cryptic, memorable, xkcd or external. Default: cryptic
--lang, --xkcdlang, --xl, Language to generate password from, currently de (german) and en (english, default) are supported
--print, --p, Print the generated password to the terminal
--sep, --xkcdsep, --xs, Word separator for generated passwords. If no separator is specified, the words are combined without spaces/separator and the first character of words is capitalised.
--strict, Require strict character class rules
--symbols, --s, Use symbols in the password
git Run a git command inside a password store (init, remote, push, pull)
If the password store is a git repository, execute a git command specified by git-command-args.WARNING: Deprecated. Please use gopass sync.
grep Search for secrets files containing search-string when decrypted.
This command decrypts all secrets and performs a pattern matching on the content.
--regexp, --r, Interpret pattern as RE2 regular expression
history Show password history
Display the change history for a secret
--password, --p, Include passwords in output
init Initialize new password store.
Initialize new password storage and use gpg-id for encryption.
--path, --p, Set the sub-store path to operate on
--storage, Select storage backend []
--store, --s, Set the name of the sub-store
insert Insert a new secret
Insert a new secret. Optionally, echo the secret back to the console during entry. Or, optionally, the entry may be multiline. Prompt before overwriting existing secret unless forced.
--append, --a, Append data read from STDIN to existing data
--echo, --e, Display secret while typing
--force, --f, Overwrite any existing secret and do not prompt to confirm recipients
--multiline, --m, Insert using $EDITOR
link Create a symlink
This command creates a symlink from one entry in a mounted store to another entry.Important: Does not cross mounts!
list List existing secrets
This command will list all existing secrets. Provide a folder prefix to list only certain subfolders of the store.
--flat, --f, Print a flat list
--folders, --d, Print a flat list of folders
--limit, --l, Display no more than this many levels of the tree
--strip-prefix, --s, Strip this prefix from filtered entries
merge Merge multiple secrets into one
This command implements a merge workflow to help deduplicate secrets. It requires exactly one destination (may already exist) and at least one source (must exist, can be multiple). gopass will then merge all entries into one, drop into an editor, save the result and remove all merged entries.
--delete, --d, Remove merged entries
--force, --f, Skip editor, merge entries unattended
mounts Edit mounted stores
This command displays all mounted password stores. It offers several subcommands to create or remove mounts.
move Move secrets from one location to another
This command moves a secret from one path to another. This also works across different sub-stores. If the source is a directory, the source directory is re-created at the destination if no trailing slash is found, otherwise the contents are flattened (similar to rsync).
--force, --f, Force to move the secret and overwrite existing one
otp Generate time- or hmac-based tokens
Tries to parse an OTP URL (otpauth://). URL can be TOTP or HOTP. The URL can be provided on its own line or on a key value line with a key named 'totp'.
--clip, --c, Copy the time-based token into the clipboard
--password, --o, Only display the token
--qr,  --q, Write QR code to FILE
pwgen Generate passwords
Print any number of password to the console.
--ambiguous, --B, Do not include characters that could be easily confused with each other, like '1' and 'l' or '0' and 'O'
--no-capitalize, --A, Do not include capital letter in the generated passwords.
--no-numerals, --0, Do not include numerals in the generated passwords.
--one-per-line, --1, Print one password per line
--sep, --xkcdsep, --xs, Word separator for generated xkcd style password. If no separator is specified, the words are combined without spaces/separator and the first character of words is capitalised. This flag implies -xkcd
--symbols, --y, Include at least one symbol in the password.
--xkcd, --x, Use multiple random english words combined to a password. By default, space is used as separator and all words are lowercase
recipients Edit recipient permissions
This command displays all existing recipients for all mounted stores. The subcommands allow adding or removing recipients.
setup Initialize a new password store
This command is automatically invoked if gopass is started without any existing password store. This command exists so users can be provided with simple one-command setup instructions.
--alias, Local mount point for the given remote
--create, Create a new team (default: false, i.e. join an existing team)
--email, EMail for unattended GPG key generation
--name, Firstname and Lastname for unattended GPG key generation
--remote, URL to a git remote, will attempt to join this team
show Display the content of a secret
Show an existing secret and optionally put its first line on the clipboard. If put on the clipboard, it will be cleared after 45 seconds.
sum Compute the SHA256 checksum
This command decodes an Base64 encoded secret and computes the SHA256 checksum over the decoded data. This is useful to verify the integrity of an inserted secret.
sync Sync all local stores with their remotes
Sync all local stores with their git remotes, if any, and check any possibly affected gpg keys.
--store, --s, Select the store to sync
templates Edit templates
List existing templates in the password store and allow for editing and creating them.
unclip Internal command to clear clipboard
Clear the clipboard if the content matches the checksum.
--force, Clear clipboard even if checksum mismatches
--timeout, Time to wait
update Check for updates
This command checks for gopass updates at GitHub and automatically downloads and installs any missing update.
version Display version
This command displays version and build time information along with version information of important external commands. Please provide the output when reporting issues.
Report bugs to <https://github.com/gopasspw/gopass/issues/new>
Copyright Â© 2021 Gopass Authors This program is free software; you may redistribute it under the terms of the MIT license. This program has absolutely no warranty.
RC-STATUS(8)                 System Manager's Manual                RC-STATUS(8)
rc-status â€” show status info about runlevels
rc-status [-aclsuC] [-f ini] [runlevel]
rc-status gathers and displays information about the status of services in different runlevels.  The default behavior is to show information about the current runlevel and any unassigned services that are not stopped, but any runlevel can be quickly examined.
If an active service is being supervised by supervise-daemon(8,) the amount of time the daemon has been active along with the number of times it has been respawned in the current respawn period will be displayed.
-a, --all             Show all runlevels and their services.
-c, --crashed         List all services that have crashed.
-f, --format          Select a format for the output. Currently, the only one that can be specified is ini, which outputs in *.ini format.
-l, --list            List all defined runlevels.
-m, --manual          Show all manually started services.
-r, --runlevel        Print the current runlevel name.
-S, --supervised      Show all supervised services.
-s, --servicelist     Show all services.
-u, --unused          Show services not assigned to any runlevel.
-C, --nocolor         Disable color output.
runlevel              Show information only for the named runlevel.
rc-status exits 0, except when checking for crashed services and it doesn't find any.
rc-status tries to list services within each runlevel in the presently resolved dependency order if the dependency tree is available.
openrc(8), rc-update(8) supervise-daemon(8)
Roy Marples <roy@marples.name>
CRYSTAL(1)        Crystal Compiler Command Line Reference Guide       CRYSTAL(1)
crystal â€” Compiler for the Crystal language.
crystal command [switches] programfile -- [arguments]
Crystal is a statically type-checked programming language. It was created with the beauty of Ruby and the performance of C in mind.
You can compile and run a program by invoking the compiler with a single filename:
crystal some_program.cr
Crystal files usually end with the .cr extension, though this is not mandatory.
Alternatively you can use the run command:
crystal run some_program.cr
To create an executable use the build command:
crystal build some_program.cr
This will create an executable named "some_program".
Note that by default the generated executables are not fully optimized.  To turn optimizations on, use the --release flag:
crystal build --release some_program.cr
Make sure to always use --release for production-ready executables and when performing benchmarks.
The optimizations are not turned on by default because the compile times are much faster without them and the performance of the program is still pretty good without them, so it allows to use the crystal command almost to be used as if it was an interpreter.
The crystal command accepts the following options
init TYPE [DIR | NAME DIR]
Generates a new Crystal project.
TYPE is one of:
lib       Creates a library skeleton app       Creates an application skeleton
This initializes the lib/app project folder as a git repository, with a license file, a README file, a shard.yml for use with shards (the Crystal dependency manager), a .gitignore file, and src and spec folders.
DIR  - directory where project will be generated
NAME - name of project to be generated (default: basename of DIR)
-f, --force Force overwrite existing files. -s, --skip-existing Skip existing files.
build [options] [programfile] [--] [arguments]
Compile program.
Generate documentation from comments using a subset of markdown. The output is saved in html format on the created docs/ folder. More information about documentation conventions can be found at https://crystal-lang.org/docs/conventions/documenting_code.html.
--project-name NAME Set the project name. The default value is extracted from shard.yml if available.
In case no default can be found, this option is mandatory. --project-version VERSION Set the project version. The default value is extracted from current git commit or shard.yml if available.
In case no default can be found, this option is mandatory. --json-config-url URL Set the URL pointing to a config file (used for discovering versions). --source-refname REFNAME Set source refname (e.g. git tag, commit hash). The default value is extracted from current git commit if available.
If this option is missing and can't be automatically determined, the generator can't produce source code links. --source-url-pattern URL Set URL pattern for source code links. The default value is extracted from git remotes ("origin" or first one) if available and the provider's URL pattern is recognized.
Supported replacement tags:
%{refname}  commit reference %{path}     path to source file inside the repository %{filename} basename of the source file %{line}     line number
If this option is missing and can't be automatically determined, the generator can't produce source code links. -o DIR, --output DIR Set the output directory (default: ./docs). -b URL, --canonical-base-url URL Indicate the preferred URL with rel="canonical" link element. -b URL, --sitemap-base-url URL Set the sitemap base URL. Sitemap will only be generated when this option is set. --sitemap-priority PRIO Set the priority assigned to sitemap entries (default: 1.0). --sitemap-changefreq FREQ Set the changefreq assigned to sitemap entries (default: never).
env [variables]
Print Crystal-specific environment variables in a format compatible with shell scripts. If one or more variable names are given as arguments, it prints only the value of each named variable on its own line.
Variables:
CRYSTAL_CACHE_DIR Please see ENVIRONMENT VARIABLES.
CRYSTAL_LIBRARY_PATH Please see ENVIRONMENT VARIABLES.
CRYSTAL_PATH Please see ENVIRONMENT VARIABLES.
CRYSTAL_VERSION Contains Crystal version.
eval[options][source]
Evaluate code from arguments or, if no arguments are passed, from the standard input. Useful for experiments.
-d,--debug Generate the output with symbolic debug symbols.  These are read when debugging the built program with tools like lldb, gdb, valgrind etc. and provide mappings to the original source code for those tools. --no-debug Generate the output without any symbolic debug symbols. -DFLAG,--defineFLAG Define a compile-time flag. This is useful to conditionally define types, methods, or commands based on flags available at compile time. The default flags are from the target triple given with --target-triple or the hosts default, if none is given. --error-trace Show full error trace. --release Turn on optimizations for the generated code, which are disabled by default. -s,--stats Print statistics about the different compiler stages for the current build. Output time and used memory for each compiler process. -p,--progress Print statistics about the progress for the current build. -t,--time Print statistics about the execution time. --no-color Disable colored output.
play[options][file]
Starts the crystal playground server on port 8080, by default.
-pPORT,--portPORT Run the playground on the specified port. Default is 8080. -bHOST,--bindingHOST Bind the playground to the specified IP. -v,--verbose Display detailed information of the executed code.
run[options][programfile][--][arguments]
The default command. Compile and run program.
Options: Same as the build options.
spec[options][files]
Compile and run specs (in spec directory).
tool[tool][switches][programfile][--][arguments]
Run a tool. The available tools are: context, format, hierarchy, implementations, and types.
Tools:
context Show context for given location.
expand  Show macro expansion for given location.
format  Format project, directories and/or files with the coding style used in the standard library. You can use the --checkflag to check whether the formatter would make any changes.
hierarchy Show hierarchy of types from file. Also show class and struct members, with type and size. Types can be filtered with a regex by using the -eflag.
implementations Show implementations for a given call. Use --cursorto specify the cursor position. The format for the cursor position is file:line:column.
types   Show type of main variables of file.
help,--help,-h
Show help. Option --help or -h can also be added to each command for command-specific help.
version,--version,-v
CRYSTAL_CACHE_DIR Defines path where Crystal caches partial compilation results for faster subsequent builds. This path is also used to temporarily store executables when Crystal programs are run with 'crystal run' rather than 'crystal build'.
CRYSTAL_LIBRARY_PATH Defines paths where Crystal searches for (binary) libraries. Multiple paths can be separated by ":".  These paths are passed to the linker as `-L` flags.
The pattern '$ORIGIN' at the start of the path expands to the directory where the compiler binary is located. For example, '$ORIGIN/../lib/crystal' resolves the standard library path relative to the compiler location in a generic way, independent of the absolute paths (assuming the relative location is correct).
CRYSTAL_PATH Defines paths where Crystal searches for required source files. Multiple paths can be separated by ":".
The pattern '$ORIGIN' at the start of the path expands to the directory where the compiler binary is located. For example, '$ORIGIN/../share/crystal/src' resolves the standard library path relative to the compiler location in a generic way, independent of the absolute paths (assuming the relative location is correct).
CRYSTAL_OPTS Defines options for the Crystal compiler to be used besides the command line arguments. The syntax is identical to the command line arguments. This is hany when using Crystal in build setups, for example 'CRYSTAL_OPTS=--debug make build'.
shards(1) https://crystal-lang.org/                     The official web site. https://github.com/crystal-lang/crystal       Official Repository.
PNGCHECK(1)                       User Commands                      PNGCHECK(1)
pngcheck - tests PNG, JNG or MNG image files for corruption, and prints size/type info.
pngcheck [-7cpqtv] file.{png|jng|mng} [file2.{png|jng|mng} [...]] ... | pngcheck [-7cpqstvx] pngcheck [-7cpqstvx] file-containing-PNGs...
PNGcheck, version 3.0.2 of 31 January 2021, by Alexander Lehmann, Andreas Dilger and Greg Roelofs.
Test PNG, JNG or MNG image files for corruption, and print size/type info.
-7     print contents of tEXt chunks, escape chars >=128 (for 7-bit terminals)
-c     colorize output (for ANSI terminals)
-p     print contents of PLTE, tRNS, hIST, sPLT and PPLT (can be used with -q)
-q     test quietly (output only errors)
-s     search for PNGs within another file
-t     print contents of tEXt chunks (can be used with -q)
-v     test verbosely (print most chunk data)
-vv    test very verbosely (decode & print line filters)
-w     suppress windowBits test (more-stringent compression check)
-x     search for PNGs within another file and extract them when found
MNG support is more informational than conformance-oriented.
pngsplit(1), png-fix-IDAT-windowsize(1)
QCMD(1)                      General Commands Manual                     QCMD(1)
qmv, qcp - Rename or copy files quickly, editing the file names in a text editor
qcp [OPTION]... [FILE]...
qmv [OPTION]... [FILE]...
qcmd --command=COMMAND [OPTION]... [FILE]...
This manual page document describes the qcp, qmv and qcmd commands.
The qmv program allows files to be renamed by editing their names in any text editor. By changing a letter in a text document, a letter in a filename can be changed. Since the files are listed after each other, common changes can be made more quickly.
The qcp program works like qmv, but copies files instead of moving them.
The qmv program was built with safety in mind - bogus renames caused by human error are avoided by performing as many checks as possible. Because of this, qmv supports an interactive mode where each step in the rename procedure can be executed manually. The default is to start qmv in non-interactive mode. However, when there is a conflict or error, qmv will drop to interactive mode (instead of losing all user-made changes). For more information on the renaming process and interactive mode, see below. This also applies to qcp.
The qcmd program works just like qmv and qcp but allows you to specify which command to execute.
The ls(1) program is used to list files to rename or copy. Therefore qmv, qcp, and qcmd accepts some ls options.
RENAMING/COPYING PROCESS The process of renaming or copying files consists of many steps. They are:
List files Generate a list files to rename from command-line arguments by using ls(1).
Create an editable text file The edit format creates an editable text file with the file names.
Start the editor Start the text editor and wait until the user has finished editing it.
Read the edited text file The edit format reads the edited text file now with updated file names.
Check rename and reorder to resolve conflicts (qmv only) This is a complicated step which involves the following tasks:
Tag renames where the destination file already exists, renames where the old file is now missing or inaccessible, and renames renames where the new name was not changed. Perform a topologic sort on the renames, so that renaming b->c, a->b is possible. Resolve cross references by renaming into temporary names, so that renaming e->f, f->e (or e->f, f->g, g->e and so on) is possible.
This step results in a plan of renames.
Display the plan. Display the plan to the user.
Apply the plan. Apply the plan by actually renaming or copying files (unless --dummy was specified).