neulab/tldr huggingface dataset:
Other standard GNOME options not listed here are also supported.
The documentation may be accessed by pressing F1 in the application or via the application menu.
For further information, visit the website https://wiki.gnome.org/Apps/Nautilus
Bug reports can be found and filed at https://gitlab.gnome.org/GNOME/nautilus/issues
FLOCK(1)                          User Commands                         FLOCK(1)
flock - manage locks from shell scripts
flock [options] file|directory command [arguments]
flock [options] file|directory -c command
flock [options] number
This utility manages flock(2) locks from within shell scripts or from the command line.
The first and second of the above forms wrap the lock around the execution of a command, in a manner similar to su(1) or newgrp(1). They lock a specified file or directory, which is created (assuming appropriate permissions) if it does not already exist. By default, if the lock cannot be immediately acquired, flock waits until the lock is available.
The third form uses an open file by its file descriptor number. See the examples below for how that can be used.
-c, --command command Pass a single command, without arguments, to the shell with -c.
-E, --conflict-exit-code number The exit status used when the -n option is in use, and the conflicting lock exists, or the -w option is in use, and the timeout is reached. The default value is 1. The number has to be in the range of 0 to 255.
-F, --no-fork Do not fork before executing command. Upon execution the flock process is replaced by command which continues to hold the lock. This option is incompatible with --close as there would otherwise be nothing left to hold the lock.
-e, -x, --exclusive Obtain an exclusive lock, sometimes called a write lock. This is the default.
-n, --nb, --nonblock Fail rather than wait if the lock cannot be immediately acquired. See the -E option for the exit status used.
-o, --close Close the file descriptor on which the lock is held before executing command. This is useful if command spawns a child process which should not be holding the lock.
-s, --shared Obtain a shared lock, sometimes called a read lock.
-u, --unlock Drop a lock. This is usually not required, since a lock is automatically dropped when the file is closed. However, it may be required in special cases, for example if the enclosed command group may have forked a background process which should not be holding the lock.
-w, --wait, --timeout seconds Fail if the lock cannot be acquired within seconds. Decimal fractional values are allowed. See the -E option for the exit status used. The zero number of seconds is interpreted as --nonblock.
--verbose Report how long it took to acquire the lock, or why the lock could not be obtained.
The command uses <sysexits.h> exit status values for everything, except when using either of the options -n or -w which report a failure to acquire the lock with an exit status given by the -E option, or 1 by default. The exit status given by -E has to be in the range of 0 to 255.
When using the command variant, and executing the child worked, then the exit status is that of the child command.
Note that "shell> " in examples is a command line prompt.
shell1> flock /tmp -c cat; shell2> flock -w .007 /tmp -c echo; /bin/echo $? Set exclusive lock to directory /tmp and the second command will fail.
shell1> flock -s /tmp -c cat; shell2> flock -s -w .007 /tmp -c echo; /bin/echo $? Set shared lock to directory /tmp and the second command will not fail. Notice that attempting to get exclusive lock with second command would fail.
shell> flock -x local-lock-file echo 'a b c' Grab the exclusive lock "local-lock-file" before running echo with 'a b c'.
(; flock -n 9 || exit 1; # ... commands executed under lock ...; ) 9>/var/lock/mylockfile The form is convenient inside shell scripts. The mode used to open the file doesn’t matter to flock; using > or >> allows the lockfile to be created if it does not already exist, however, write permission is required. Using < requires that the file already exists but only read permission is required.
[ ${FLOCKER} != $0 ] && exec env FLOCKER="$0 flock -en $0 $0 $@ || This is useful boilerplate code for shell scripts. Put it at the top of the shell script you want to lock and it’ll automatically lock itself on the first run. If the env var $FLOCKER is not set to the shell script that is being run, then execute flock and grab an exclusive non-blocking lock (using the script itself as the lock file) before re-execing itself with the right arguments. It also sets the FLOCKER env var to the right value so it doesn’t run again.
shell> exec 4<>/var/lock/mylockfile; shell> flock -n 4 This form is convenient for locking a file without spawning a subprocess. The shell opens the lock file for reading and writing as file descriptor 4, then flock is used to lock the descriptor.
H. Peter Anvin <hpa@zytor.com>
Copyright © 2003-2006 H. Peter Anvin. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
flock(2)
The flock command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
ANSIBLE(1)               System administration commands               ANSIBLE(1)
ansible - Define and run a single task 'playbook' against a set of hosts
usage: ansible [-h] [--version] [-v] [-b] [--become-method BECOME_METHOD] [--become-user BECOME_USER] [-K | --become-password-file BECOME_PASSWORD_FILE] [-i INVENTORY] [--list-hosts] [-l SUBSET] [-P POLL_INTERVAL] [-B SECONDS] [-o] [-t TREE] [--private-key PRIVATE_KEY_FILE] [-u REMOTE_USER] [-c CONNECTION] [-T TIMEOUT] [--ssh-common-args SSH_COMMON_ARGS] [--sftp-extra-args SFTP_EXTRA_ARGS] [--scp-extra-args SCP_EXTRA_ARGS] [--ssh-extra-args SSH_EXTRA_ARGS] [-k | --connection-password-file CONNECTION_PASSWORD_FILE] [-C] [--syntax-check] [-D] [-e EXTRA_VARS] [--vault-id VAULT_IDS] [--ask-vault-password | --vault-password-file VAULT_PASSWORD_FILES] [-f FORKS] [-M MODULE_PATH] [--playbook-dir BASEDIR] [--task-timeout TASK_TIMEOUT] [-a MODULE_ARGS] [-m MODULE_NAME] pattern
is an extra-simple tool/framework/API for doing 'remote things'.  this command allows you to define and run a single task 'playbook' against a set of hosts
host pattern
--become-method 'BECOME_METHOD' privilege escalation method to use (default=sudo), use ansible-doc -t become -l to list valid choices.
--become-password-file 'BECOME_PASSWORD_FILE', --become-pass-file 'BECOME_PASSWORD_FILE' Become password file
--become-user 'BECOME_USER' run operations as this user (default=root)
--connection-password-file 'CONNECTION_PASSWORD_FILE', --conn-pass-file 'CONNECTION_PASSWORD_FILE' Connection password file
--list-hosts outputs a list of matching hosts; does not execute anything else
--private-key 'PRIVATE_KEY_FILE', --key-file 'PRIVATE_KEY_FILE' use this file to authenticate the connection
--scp-extra-args 'SCP_EXTRA_ARGS' specify extra arguments to pass to scp only (e.g. -l)
--sftp-extra-args 'SFTP_EXTRA_ARGS' specify extra arguments to pass to sftp only (e.g. -f, -l)
--ssh-common-args 'SSH_COMMON_ARGS' specify common arguments to pass to sftp/scp/ssh (e.g. ProxyCommand)
--ssh-extra-args 'SSH_EXTRA_ARGS' specify extra arguments to pass to ssh only (e.g. -R)
--syntax-check perform a syntax check on the playbook, but do not execute it
--task-timeout 'TASK_TIMEOUT' set task timeout limit in seconds, must be positive integer.
-B 'SECONDS', --background 'SECONDS' run asynchronously, failing after X seconds (default=N/A)
-C, --check don't make any changes; instead, try to predict some of the changes that may occur
-D, --diff when changing (small) files and templates, show the differences in those files; works great with --check
-K, --ask-become-pass ask for privilege escalation password
-M, --module-path prepend colon-separated path(s) to module library (default=~/.ansible/plugins/modules:/usr/share/ansible/plugins/modules)
-P 'POLL_INTERVAL', --poll 'POLL_INTERVAL' set the poll interval if using -B (default=15)
-T 'TIMEOUT', --timeout 'TIMEOUT' override the connection timeout in seconds (default=10)
-a 'MODULE_ARGS', --args 'MODULE_ARGS' The action's options in space separated k=v format: -a 'opt1=val1 opt2=val2'
-b, --become run operations with become (does not imply password prompting)
-c 'CONNECTION', --connection 'CONNECTION' connection type to use (default=smart)
-f 'FORKS', --forks 'FORKS' specify number of parallel processes to use (default=5)
-k, --ask-pass ask for connection password
-l 'SUBSET', --limit 'SUBSET' further limit selected hosts to an additional pattern
-m 'MODULE_NAME', --module-name 'MODULE_NAME' Name of the action to execute (default=command)
-o, --one-line condense output
-t 'TREE', --tree 'TREE' log output to this directory
-u 'REMOTE_USER', --user 'REMOTE_USER' connect as this user (default=None)
ansible-config (1), ansible-console (1), ansible-doc (1), ansible-galaxy (1), ansible-inventory (1), ansible-playbook (1), ansible-pull (1), ansible-vault (1)
LIGHT(1)                     User's Reference Manual                    LIGHT(1)
light — a program to control backlight controllers
light [OPTIONS] [VALUE]
light is a program to control backlight display and keyboard controllers under GNU/Linux.
•   Operates independently of X (X-Window) •   Can automatically figure out the best controller to use, making full use of the underlying hardware •   Supports a minimum cap on the brightness value, as some controllers set the display to be pitch black at a vaĺue of 0 (or higher)
The following unique commands are supported:
-H, -h  Show help text and exit
-V      Show program version and exit
-L      List available devices
-A      Increase brightness by value
-U      Decrease brightness by value
-S      Set brightness to value
-G      Get brightness, default
-N      Set minimum brightness to value
-P      Get minimum brightness
-O      Save current brightness
-I      Restore previously saved brightness
The behavior of the above commands can be modified using these options:
-r      Interpret input and output values in raw mode
-s PATH Specify device target path.  Use -L to list available devices
-v LEVEL Set verbosity level, by default light only outputs read values:
0:  Read values 1:  Read values, Errors 2:  Read values, Errors, Warnings 3:  Read values, Errors, Warnings, Notices
When run in its classic SUID root mode light caches settings and current brightness in /etc/light.  In its non-privileged mode of operation the ~/.cache/light directory is used instead.
Copyright © 2012-2018 Fredrik Haikarainen
This is free software, see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE
FLS(1)                       General Commands Manual                      FLS(1)
fls - List file and directory names in a disk image.
fls [-adDFlpruvV] [-m mnt ] [-z zone ] [-f fstype ] [-s seconds ] [-i imgtype ] [-o imgoffset ] [-b dev_sector_size] image [images] [ inode ]
fls lists the files and directory names in the image and can display file names of recently deleted files for the directory using the given inode. If the inode argument is not given, the inode value for the root directory is used. For example, on an NTFS file system it would be 5 and on a Ext3 file system it would be 2.
-a     Display the "." and ".." directory entries (by default it does not)
-d     Display deleted entries only
-D     Display directory entries only
-f fstype The type of file system.  Use '-f list' to list the supported file system types.  If not given, autodetection methods are used.
-F     Display file (all non-directory) entries only.
-l     Display file details in long format.  The following contents are displayed:
file_type inode file_name mod_time acc_time chg_time cre_time size uid gid
-m mnt Display files in time machine format so that a timeline can be created with mactime(1).  The string given as mnt will be prepended to the file names as the mounting point (for example /usr).
-p     Display the full path for each entry.  By default it denotes the directory depth on recursive runs with a '+' sign.
-r     Recursively display directories.  This will not follow deleted directories, because it can't.
-s seconds The time skew of the original system in seconds.  For example, if the original system was 100 seconds slow, this value would be -100.  This is only used if -l or -m are given.
-o imgoffset The sector offset where the file system starts in the image.
-u     Display undeleted entries only
-v     Verbose output to stderr.
-V     Display version.
-z zone The ASCII string of the time zone of the original system.  For example, EST or GMT.  These strings must be defined by your operating system and may vary.
Once the inode has been determined, the file can be recovered using icat(1) from The Coroners Toolkit.  The amount of information recovered from deleted file entries varies depending on the system.  For example, on Linux, a recently deleted file can be easily recovered, while in Solaris not even the inode can be determined.  If you just want to find what file name belongs to an inode, it is easier to use ffind(1).
To get a list of all files and directories in an image use:
# fls -r image 2
or just (if no inode is specified, the root directory inode is used):
# fls -r image
To get the full path of deleted files in a given directory:
# fls -d -p image 29
To get the mactime output do:
# fls -m /usr/local image 2
If you have a disk image and the file system starts in sector 63, use:
# fls -o 63 disk-img.dd
If you have a disk image that is split use:
# fls -i "split" -o 63 disk-1.dd disk-2.dd disk-3.dd
ffind(1), icat(1)
Send documentation updates to <doc-updates at sleuthkit dot org>
PROSODYCTL(1)                                                      PROSODYCTL(1)
prosodyctl - Manage a Prosody XMPP server
prosodyctl command [--help]
prosodyctl is the control tool for the Prosody XMPP server.  It may be used to control the server daemon and manage users.
prosodyctl needs to be executed with sufficient privileges to perform its commands.  This typically means executing prosodyctl as the root user. If a user named "prosody" is found then prosodyctl will change to that user before executing its commands.
User Management In the following commands users are identified by a Jabber ID, jid, of the usual form: user@domain.
adduser jid Adds a user with Jabber ID, jid, to the server.  You will be prompted to enter the user's password.
passwd jid Changes the password of an existing user with Jabber ID, jid.  You will be prompted to enter the user's new password.
deluser jid Deletes an existing user with Jabber ID, jid, from the server.
Daemon Management Although prosodyctl has commands to manage the prosody daemon it is recommended that you utilize your distributions daemon management features if you attained Prosody through a package.
To perform daemon control commands prosodyctl needs a pidfile value specified in /etc/prosody/prosody.cfg.lua.  Failure to do so will cause prosodyctl to complain.
start  Starts the prosody server daemon.  If run as root prosodyctl will attempt to change to a user named "prosody" before executing. This operation will block for up to five seconds to wait for the server to execute.
stop   Stops the prosody server daemon.  This operation will block for up to five seconds to wait for the server to stop executing.
restart Restarts the prosody server daemon.  Equivalent to running prosodyctl stop followed by prosodyctl start.
reload Signals the prosody server daemon to reload configuration and reopen log files.
status Prints the current execution status of the prosody server daemon.
Certificates prosodyctl can create self-signed certificates, certificate requests and private keys for use with Prosody.  Commands are of the form prosodyctl cert subcommand.  Commands take a list of hosts to be included in the certificate.
request hosts Create a certificate request (CSR) file for submission to a certificate authority.  Multiple hosts can be given, sub-domains are automatically included.
generate hosts Generate a self-signed certificate.
key host [size] Generate a private key of 'size' bits (defaults to 2048).  Invoked automatically by 'request' and 'generate' if needed.
config hosts Produce a config file for the list of hosts.  Invoked automatically by 'request' and 'generate' if needed.
import hosts paths Copy certificates for hosts into the certificate path and reload prosody.
Debugging prosodyctl can also show some information about the environment, dependencies and such to aid in debugging.
about  Shows environment, various paths used by Prosody and installed dependencies.
check [what] Performs various sanity checks on the configuration, DNS setup and configured TLS certificates.  what can be one of config, dns and certs to run only that check.
Ejabberd Compatibility ejabberd is another XMPP server which provides a comparable control tool, ejabberdctl, to control its server's operations.  prosodyctl implements some commands which are compatible with ejabberdctl.  For details of how these commands work you should see ejabberdctl(8).
register user server password
unregister user server
--config filename Use the specified config file instead of the default.
--root Don't drop root privileges.
--help Display help text for the specified command.
/etc/prosody/prosody.cfg.lua The main prosody configuration file.  prosodyctl reads this to determine the process ID file of the prosody server daemon and to determine if a host has been configured.
More information may be found online at: <https://prosody.im/>
Dwayne Bent <dbb.1@liqd.org>; Kim Alvefur.
THUNAR(1)                        [FIXME: manual]                       THUNAR(1)
Thunar - File Manager for the Xfce Desktop Environment
Thunar [options] [[URI]...]
Thunar [options] --bulk-rename [[URI]...]
Thunar [options] --quit
Thunar is a fast and easy to use file manager for the Xfce Desktop Environment. It has been designed from the ground up to be lighweight with special focus on usability. Its user interface is clean and intuitive, and does not include any confusing or useless options.
Thunar takes a list of URIs for folders that should be opened in new file manager windows or files that should be run using the default application for their types. The URIs may be specified as either file: or trash: URIs, absolute paths or paths relative to the current directory from which Thunar is being invoked. If no URIs are specified, the current folder will be opened in a new file manager window.
When the --bulk-rename option is specified no file managers windows will be opened, but instead the URIs will be passed to the bulk renamer. The bulk renamer allows one to rename several files or folders at once using different renamer modules.
Options -?, --help Print brief help and exit.
-B, --bulk-rename Open the URIs in a standalone window of the bulk renamer.
--daemon Do not terminate the Thunar instance when the last window is closed, but keep it running to speed up opening new windows later on. This is the default when spawning Thunar as part of the default Xfce session or when using D-Bus activation.
--display=DISPLAY Use the specified X DISPLAY for the user interface.
-q, --quit Terminate any Thunar instance running in the background (spawned using the --daemon option). This command should be used whenever Thunar is upgraded to a new version to ensure that no old instance is reused.
Thunar was written by Benedikt Meurer <benny@xfce.org>.
This manual page was written by Benedikt Meurer <benny@xfce.org>.
CSVCLEAN(1)                          csvkit                          CSVCLEAN(1)
csvclean - csvclean Documentation
Cleans a CSV file of common syntax errors:
• reports rows that have a different number of columns than the header row
• attempts to correct the CSV by joining short rows into a single row
Note that every csvkit tool does the following:
• removes optional quote characters, unless the –quoting (-u) option is set to change this behavior
• changes the field delimiter to a comma, if the input delimiter is set with the –delimiter (-d) or –tabs (-t) options
• changes the record delimiter to a line feed (LF or \n)
• changes the quote character to a double-quotation mark, if the character is set with the –quotechar (-q) option
• changes the character encoding to UTF-8, if the input encoding is set with the –encoding (-e) option
Outputs [basename]_out.csv and [basename]_err.csv, the former containing all valid rows and the latter containing all error rows along with line numbers and descriptions:
usage: csvclean [-h] [-d DELIMITER] [-t] [-q QUOTECHAR] [-u {0,1,2,3}] [-b] [-p ESCAPECHAR] [-z FIELD_SIZE_LIMIT] [-e ENCODING] [-S] [-H] [-K SKIP_LINES] [-v] [-l] [--zero] [-V] [-n] [FILE]
Fix common errors in a CSV file.
positional arguments: FILE                  The CSV file to operate on. If omitted, will accept input on STDIN.
optional arguments: -h, --help            show this help message and exit -n, --dry-run         Do not create output files. Information about what would have been done will be printed to STDERR.
See also: ../common_arguments.
Test a file with known bad rows:
csvclean -n examples/bad.csv
Line 1: Expected 3 columns, found 4 columns Line 2: Expected 3 columns, found 2 columns
To change the line ending from line feed (LF or \n) to carriage return and line feed (CRLF or \r\n) use:
csvformat -M $'\r\n' examples/dummy.csv
Christopher Groskopf
2021, Christopher Groskopf
ROLLDICE(6)                       Games Manual                       ROLLDICE(6)
rolldice - rolls virtual dice
rolldice [ options ] [dice_string [dice_string ...]]
rolldice rolls virtual dice.  The dice strings passed on the command line contain information on the dice to roll in a format comparable to the format used in most role playing games.
If no dice strings are provided as command line arguments, rolldice uses stdin as input.
-h,--help returns the usage of diceroll
-v,--version returns the version of diceroll
-r,--random uses /dev/random for random number generating
-u,--urandom uses /dev/urandom for random number generating (default)
-s,--separate prints out the result of each individual die separately, as well as the operations and totals
-i,--interactive prompts the user to input dice strings. Differs from normal stdin input in that errors do not cause the program to immediately exit, but rather return to the prompt.
The dice string uses the following format:
{#x}{#}d[#|%]{*#}{+/-#}{s#}
The dice string doesn't have to be in the exact format outlined above, but this is the order I use.  It will try to parse any different string containing the same sections in the best way it can, and will throw out anything that isn't one of the sections below.
{#}d[#|%] The first number is the number of dice to roll, and the second number is the number of sides the dice have.  The numbers rolled on each die are then added up and given as the result.  Hence 3d6 means "roll three six-sided dice, add them together and return the result".  If the first number is left out, then the number of dice defaults to 1. If the second number is not a number, but a percentage sign (%), then the number of sides becomes 100 (for a percentage roll).  If this is not included in the dice string, then the default is 1d6.
{#x}   This number describes how many times to roll.  For example, if you want to roll 3 6-sided dice 6 times, you use the dice string 6x3d6.  This returns six numbers, corresponding to the six different rolls.
{*#}   This number describes how many times to multiply the result of each roll.  3d6*100 returns a number in the range of 300-1800, because 3-18 is the range for 3d6 and the result is then multipled by 100.
{+/-#} This number is the modifier to be added or subtracted, depending on the sign, from each roll.  1d4+1 results in a range from 2-5 (1-4 for the die, plus 1).  This step is handled *after* the multiplication modifier.
{s#}   This number describes how many lowest dice rolls to drop. This step is handled *before* the multiplication modifier.
in the order show above.  For an extreme example, "3x4d6*5+1s2" would roll four six-sided dice, drop the lowest two, multiply the result by 5, add 1 to that, and repeat the process two more times, for a total of three results.
The following error messages may appear on STDERR:
Requested * is too large Memory could not be allocated while parsing the string passed to the rolldice program Problems with the malformed dice string The dice string contains a syntax error (see upper section DICE STRING FORMAT) Unknown option An unknown command-line option was provided
The exit values returned by rolldice follow the BSD convention.
Stevie Strickland <sstrickl@ccs.neu.edu>
1.16 - 18 Dec 2012
LLC(1)                                LLVM                                LLC(1)
llc - LLVM static compiler
llc [options] [filename]
The llc command compiles LLVM source inputs into assembly language for a specified architecture.  The assembly language output can then be passed through a native assembler and linker to generate a native executable.
The choice of architecture for the output assembly code is automatically determined from the input file, unless the -march option is used to override the default.
If filename is "-" or omitted, llc reads from standard input.  Otherwise, it will from filename.  Inputs can be in either the LLVM assembly language format (.ll) or the LLVM bitcode format (.bc).
If the -o option is omitted, then llc will send its output to standard output if the input is from standard input.  If the -o option specifies "-", then the output will also be sent to standard output.
If no -o option is specified and an input file other than "-" is specified, then llc creates the output filename by taking the input filename, removing any existing .bc extension, and adding a .s suffix.
Other llc options are described below.
End-user Options -help  Print a summary of command line options.
-o <filename> Use <filename> as the output filename. See the summary above for more details.
-O=uint Generate code at different optimization levels.  These correspond to the -O0, -O1, -O2, and -O3 optimization levels used by clang.
-mtriple=<target triple> Override the target triple specified in the input file with the specified string.
-march=<arch> Specify the architecture for which to generate assembly, overriding the target encoded in the input file.  See the output of llc -help for a list of valid architectures.  By default this is inferred from the target triple or autodetected to the current architecture.
-mcpu=<cpuname> Specify a specific chip in the current architecture to generate code for.  By default this is inferred from the target triple and autodetected to the current architecture.  For a list of available CPUs, use:
llvm-as < /dev/null | llc -march=xyz -mcpu=help
-filetype=<output file type> Specify what kind of output llc should generated.  Options are: asm for textual assembly ( '.s'), obj for native object files ('.o') and null for not emitting anything (for performance testing).
Note that not all targets support all options.
-mattr=a1,+a2,-a3,... Override or control specific attributes of the target, such as whether SIMD operations are enabled or not.  The default set of attributes is set by the current CPU.  For a list of available attributes, use:
llvm-as < /dev/null | llc -march=xyz -mattr=help
--frame-pointer Specify effect of frame pointer elimination optimization (all,non-leaf,none).
--disable-excess-fp-precision Disable optimizations that may produce excess precision for floating point.  Note that this option can dramatically slow down code on some systems (e.g. X86).
--enable-no-infs-fp-math Enable optimizations that assume no Inf values.
--enable-no-nans-fp-math Enable optimizations that assume no NAN values.
--enable-no-signed-zeros-fp-math Enable FP math optimizations that assume the sign of 0 is insignificant.
--enable-no-trapping-fp-math Enable setting the FP exceptions build attribute not to use exceptions.
--enable-unsafe-fp-math Enable optimizations that make unsafe assumptions about IEEE math (e.g. that addition is associative) or may not work for all input ranges.  These optimizations allow the code generator to make use of some instructions which would otherwise not be usable (such as fsin on X86).
--stats Print statistics recorded by code-generation passes.
--time-passes Record the amount of time needed for each pass and print a report to standard error.
--load=<dso_path> Dynamically load dso_path (a path to a dynamically shared object) that implements an LLVM target.  This will permit the target name to be used with the -march option so that code can be generated for that target.
-meabi=[default|gnu|4|5] Specify which EABI version should conform to.  Valid EABI versions are gnu, 4 and 5.  Default value (default) depends on the triple.
-stack-size-section Emit the .stack_sizes section which contains stack size metadata. The section contains an array of pairs of function symbol values (pointer size) and stack sizes (unsigned LEB128). The stack size values only include the space allocated in the function prologue. Functions with dynamic stack allocations are not included.
-remarks-section Emit the __remarks (MachO) section which contains metadata about remark diagnostics.
Tuning/Configuration Options --print-after-isel Print generated machine code after instruction selection (useful for debugging).
--regalloc=<allocator> Specify the register allocator to use.  Valid register allocators are:
basic Basic register allocator.
fast Fast register allocator. It is the default for unoptimized code.
greedy Greedy register allocator. It is the default for optimized code.
pbqp Register allocator based on 'Partitioned Boolean Quadratic Programming'.
--spiller=<spiller> Specify the spiller to use for register allocators that support it.  Currently this option is used only by the linear scan register allocator.  The default spiller is local.  Valid spillers are:
simple Simple spiller
local Local spiller
Intel IA-32-specific Options --x86-asm-syntax=[att|intel] Specify whether to emit assembly code in AT&T syntax (the default) or Intel syntax.
If llc succeeds, it will exit with 0.  Otherwise, if an error occurs, it will exit with a non-zero value.
lli(1)
RACKET(1)                    General Commands Manual                   RACKET(1)
racket - core Racket implementation
racket [ option ...  ] [ argument ...  ]
racket --help
for a list of command-line options and other start-up information.
Supplying no arguments to racket is the same as supplying the -i option for interactive evaluation.
Supplying non-switch, non-configuration arguments to racket is the same as putting -u before the arguments to run the first one as a module-based script.
For further information, run
raco docs
to open installed documentation in your web browser.
Alternately, consult the on-line documentation and other information available at
Racket was implemented by Matthew Flatt and PLT.  It was originally based on libscheme, written by Brent Benson.
raco(1), drracket(1), gracket(1)
pacman(6)                      XScreenSaver manual                     pacman(6)
pacman - simulates a game of Pac-Man on a randomly-created level.
pacman [-display host:display.screen] [-window] [-root] [-mono] [-install] [-visual visual] [-ncolors integer] [-delay microseconds] [-size pixels] [-fps]
Simulates a game of Pac-Man on a randomly-created level.
pacman accepts the following options:
-ncolors integer How many colors should be used (if possible).  Default 6.
-size integer How big to make Pac-Man and the ghosts.  0 means "default."
-fps    Display the current frame rate and CPU load.
X(1), xscreensaver(1).
Copyright Â© 2000 Edwin de Jong.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.
Edwin de Jong <mauddib@gmx.net>.
CALCURSE(1)                                                          CALCURSE(1)
calcurse - terminal-based organizer for interactive and command line use
calcurse [-D datadir] [-C confdir] [-c calendar-file]
calcurse -Q [--from date] [--to date | --days number]
calcurse -a | -d date | -d number | -n | -r[number] | -s[date] | -t[number]
calcurse -G [filter options] [format options] | -P [filter options] [format options]
calcurse -h | --status | -g | -i file | -x[file] | --daemon
The first form shows how to invoke calcurse interactively; the remainder is command line forms.
The second form shows queries (as opposed to interactive use). For convenience, common queries have abbreviated forms shown in the third line. All queries may be combined with filter options as well as format options.
The fourth form shows operations on the calcurse data files, one for display of entries, the other for removal of them.
The fifth form is miscellaneous help and support functions.
All details are in OPTIONS.
calcurse is a calendar and scheduling application for use in a terminal session (terminal emulator). When invoked without options, calcurse enters interactive mode; in most other cases, calcurse produces output on the terminal and exits. It helps keeping track of events, appointments and everyday tasks. Interactive mode is used when data are entered or when already existing entries are inspected or edited. All data are saved to disk as text files. Command line mode is used for queries and administrative tasks and for automating tasks in scripts.
The interactive interface is based on ncurses and can be customized to suit user preferences. Customization includes program behaviour as well as visual appearance and key bindings, and is performed interactively; the result is automatically saved to disk and loaded on every invocation. Available actions are documented in an online help system. A configurable notification system issues reminders of upcoming deadlines.
When leaving the interactive program, a background daemon may continue running and issue reminders; it stops automatically when the interactive mode is reentered.
This man page mainly describes the command-line mode. The following two subsections contain some general descriptions of command line options and usage.
Input and Output Date Format Many options require a date argument, and query results per day are set apart by a leading date line.
The input format of date options and the output format of date lines are taken from the configuration file (see FILES). The formats are set in the "General Options" submenu in interactive mode. Particularly in scripts it may be desirable that formats are independent of the local user configuration. For this purpose use the options --input-datefmt and --output-datefmt.
An input date consists of date, month and year. Here day must be in the range 1-31 and month in 1-12. Depending on the operating system year must be in the range 1902-2037 or 1902-?. Additionally, some short forms are allowed with the obvious meaning: today, tomorrow, yesterday, now and weekdays mon, ..., sun.
Optionally, a date argument for a filter option (see Filter Options) may be followed by a time-of-day specification in hours and minutes (24-hour clock). The specification has the fixed format hh:mm (example: "2018-12-1 20:30" when the input date format is the ISO standard format). Note that the entire date specification must be quoted to create one argument.
Filter, format and day range options These options do not accomplish anything in and of themselves. They influence other options and are in a way opposites: filter options affect the input to, format and day range options the output from calcurse. Specifically, filter options limit what is loaded from the data files into calcurse, day range options limit what is output (see -Q), and format options describe how it is presented.
Filter options have effect on queries (-Q and query short-forms), grep (-G), purge (-P) and export (-x). Format options have effect on queries, grep and --dump-imported. Day range options have effect on queries only.
Most options imply command line mode. Options compatible with interactive mode are marked "(also interactively)".
-a, --appointment Print the appointments and events for the current day. Equivalent to -Q --filter-type cal.
-c file, --calendar file (also interactively) Specify the calendar file to use. The default calendar is located at <datadir>/apts (see FILES). If file is not an absolute path name, it is interpreted relative to the current working directory. The option has precedence over -D.
-C dir, --confdir dir (also interactively) Specify the configuration directory to use. See section FILES for the default directory and the interaction with -D.
-D dir, --datadir dir (also interactively) Specify the (data) directory to use. See section FILES for the default directory and the interaction with -C.
-d date|num, --day date|num Print appointments and events for the given date or given range of days, depending on the argument format:
•   a date
•   a number num
In the first case, appointments and events for date are returned, while in the second case those for num days are returned. Positive values of num means the future, negative the past; the range either starts or ends with the current day. As an example calcurse -d 3 displays appointments and events for today, tomorrow and the day after tomorrow, while calcurse -d -2 displays those for yesterday and today. The first form is equivalent to -Q --filter-type cal --from date, the second to -Q --filter-type cal --days num.
--daemon Start calcurse in background mode; restart, if the daemon was already running. Usually done automatically by setting the configuration option daemon.enable in the Notify submenu in interactive mode.
--days num Specify the range of days when used with -Q. Can be combined with --from, but not with --to. Without --from, the first day of the range defaults to the current day. The number may be negative, see -Q --query.
--dump-imported When importing items, print each newly created object to stdout. Format options can be used to specify which details are printed. See also Format Options.
--export-uid When exporting items, add the hash of each item to the exported object as a UID property.
--from date Specify the start date of the day range when used with -Q. When used without -to or --days the range is one day (the specified day), see -Q --query.
-F, --filter Deprecated, see -P. Note that this option is for backward compatibility and not the same as -P (it does not use the invert filter option).
-g, --gc Run the garbage collector for note files. The garbage collector removes files from the notes directory (see FILES) that are no longer linked to an item. Usually done automatically by setting the configuration option general.autogc in the General Options submenu in interactive mode.
-G, --grep Print appointments, events and TODO items in calcurse data file format.
-h, --help Print a short help text describing the supported command-line options.
-i file, --import file Import the icalendar data contained in file.
--input-datefmt format For command line and script use only: override the configuration file setting of the option format.inputdate (General Options submenu in interactive mode). A valid format is any of 1, 2, 3, or 4, with 1 = mm/dd/yyyy, 2 = dd/mm/yyyy, 3 = yyyy/mm/dd, 4 = yyyy-mm-dd.
-l num, --limit num Limit the number of results printed to num.
-n, --next Print the first appointment within the next 24 hours. The printed time is the number of hours and minutes left before this appointment.
--output-datefmt format For command line and script use only: override the configuration file setting of the option format.outputdate (General Options submenu in interactive mode). A valid format is any strftime(3) format string.
-P, --purge Load items from the data files and save them back; the items are described by suitable filter options (see Filter Options). It may be used to drop specific items from the data files, see EXAMPLES.
The matching items are (silently) removed from the data files. Any combination of filter options, except --filter-invert, may be used in describing the items to be removed. The invert filter is used internally by the purge option, and its simultaneous use on the command line may result in unpredictable behaviour.
Warning: Be careful with this option, specifying the wrong filter options may result in data loss. It is highly recommended to test with -G first and fine-tune the filters to show the items to be removed. Then run the same command with -P instead of -G. In any case, make a backup of the data files in advance.
-q, --quiet (also interactively) Be quiet. Do not show system dialogs.
-Q, --query Print all appointments and events in a given range of days followed by all TODO items. The calendar part is displayed per day with a leading line containing the date and a trailing empty line (much like the calendar panel in interactive mode).
The day range defaults to the current day and is changed with the options --from and --to/--days. The range --from a --to z includes both a and z. The range --from a --days n, includes a as the first day, if n is positive, or last day, if n is negative.
Day range has an effect on queries only.
-r[num], --range[=num] Print appointments and events for num number of days starting with the current day. If num is left out, a range of 1 day is used. The number may be negative in which case the range is in the past, ending with the current day. Equivalent to -Q --filter-type cal --days num.
--read-only (also interactively) Do not save configuration nor appointments and todos.
Warning: If you run calcurse interactively in read-only mode, all changes from that session will be lost without warning!
-s[date], --startday[=date] Print events and appointments from the optional date; default is the current day. Equivalent to -Q --filter-type cal --from date.
-S regex, --search regex When used with any of -a, -d, -r, -s, or -t print only the items having a description that matches the given regular expression. Equivalent to -Q --filter-pattern regex.
--status Display the status of running instances of calcurse, interactive or background mode. The process pid is also printed.
-t[num], --todo[=num] Print the todo list. If the optional number num is given, then only uncompleted (open) todos having a priority equal to num will be returned. The priority number must be between 1 (highest) and 9 (lowest). It is also possible to specify 0 for the priority, in which case only completed (closed) tasks will be shown. Equivalent to -Q --filter-type todo, combined with --filter-priority and --filter-completed or --filter-uncompleted.
--to date Specify the end date of the day range when used with -Q. When used without --from the start day is the current day. Cannot be combined with --days, see -Q --query.
-v, --version Display calcurse version.
-x[format], --export[=format] Export user data in the specified format. Events, appointments and todos are converted and echoed to stdout. Two formats are available: ical and pcal. The default format is ical.
Filter options have effect on queries (-Q and query short-forms), grep (-G), purge (-P) and export (-x), see also options in the DESCRIPTION section.
Several filter options may be given. For an item to be loaded into calcurse it must match all filters. In other words, filters are logically "and"-ed. The --filter-type option has a default value which matches any item. All other filter options have no default value and only apply when explicitly set.
The filter options fall into three groups: general, calendar, todo. The general filters apply to all items, the calendar filters concern start and end times and apply to appointments and events only, and the todo filters concern priority and completeness and apply to TODOs only.
Outside the three groups is the invert filter.
--filter-invert Invert the combined effect of any other filters, i.e. load the items that do not match them.
General filters --filter-type type Include items that match type. The type value is a comma-separated list of type descriptions selected from event, apt, recur-event, recur-apt and todo. You can also use recur as a shorthand for recur-event,recur-apt and cal as a shorthand for event,apt,recur.
--filter-pattern pattern Include items with a description that matches the pattern. The pattern is interpreted as an extended regular expression.
--filter-hash string Include items with a hash starting with string. The filter can be negated by prepending an exclamation mark (!): include items with a hash string not starting with string. For the (SHA1) hash of an item refer to Extended format specifiers.
Calendar filters For filter options ending in -from, -to, -after, -before and -range, start or end time is the filter criterion.
An event is an all-day appointment for which no times are displayed. The start time of an event is the beginning of the event day (midnight), the end time is the end of the event day (one second before next midnight).
The -start- options ending in -from, -after and -range refer to the same filter criterion and cannot be used together. The same is the case for options ending in -to, -before and -range. Similar restrictions apply to -end- options.
Start and end times of a recurrent item refer to the very first occurrence, not to those of any of the repetitions. If a recurrent item meets the criterion, all of the repetitions are displayed in queries, even though they may not meet the criterion. If they are unwanted, they may be removed from the output with the day range options, although this will also remove other items in that range.
--filter-start-from date Include items that start at or after a given date.
--filter-start-to date Include items that start at or before a given date.
--filter-start-after date Include items that start after a given date.
--filter-start-before date Include items that start before a given date.
--filter-start-range range Include items with a start date that belongs to a given range. A range consists of a start date and an end date, separated by a comma.
--filter-end-from date Include items that end at or after a given date.
--filter-end-to date Include items that end at or before a given date.
--filter-end-after date Include items that end after a given date.
--filter-end-before date Include items that end before a given date.
--filter-end-range range Include items with an end date that belongs to a given range. A range consists of a start date and an end date, separated by a comma.
Todo filters --filter-priority priority Include TODO items with a given priority.
--filter-completed Include completed TODO items.
--filter-uncompleted Include uncompleted TODO items.
Format options have effect on queries, grep and --dump-imported.
The options specify a format for appointments, recurring appointments, events, recurring events or todo items, respectively.
--format-apt format, --format-recur-apt format, --format-event format, --format-recur-event format, --format-todo format The format argument is a string composed of printf-style format specifiers, which are replaced as explained below, and ordinary characters, which are copied to stdout without modification. Each option has a default format string which is used when the option is not given. Default strings are described in Default Format Strings.
Note: Use of a format option requires explicit formatting of field separation and line spacing.
Default format strings Each specifier is introduced by a % followed by a character which tells what to print. The available specifiers depend on the item type. Times are printed as hours and minutes (hh:mm) unless otherwise noted; time formats can be changed with extended specifiers.
For each format option there is a default format string which is used when the option is not given. In query results the default format options are:
--format-apt " - %S -> %E\n\t%m\n" --format-recur-apt " - %S -> %E\n\t%m\n" --format-event " * %m\n" --format-recur-event " * %m\n" --format-todo "%p. %m\n"
In all other cases (grep and dump-imported) the default format string is "%(raw)".
Appointments %d Print the duration of the appointment in seconds
%e Print the end time of the appointment as the Unix time in seconds
%E Print the end time of the appointment or the marker ..:..  if it ends after midnight
%m Print the description of the item
%n Print the name of the note file belonging to the item
%N Print the note belonging to the item
%r Print the remaining time before the appointment
%s Print the start time of the appointment as the Unix time in seconds