neulab/tldr huggingface dataset:
pioneer= /dev/hdd   -1   -1
This tells wodim that a drive named plex760 is at scsibus 0, target 5, lun 0 and should be used with speed 12 and a FIFO size of 50 MB. It also uses some device specific parameter.  A second drive may is accessible via the device file /dev/hdd and uses the default speed and the default FIFO size.
icedax(1), readom(1), genisoimage(1), ssh(1).
On Solaris you need to stop the volume management if you like to use the USCSI fallback SCSI transport code. Even things like wodim -scanbus will not work if the volume management is running.
Disks made in Track At Once mode are not suitable as a master for direct mass production by CD manufacturers.  You will need the disk at once option to record such disks.  Nevertheless the disks made in Track At Once will normally be read in all CD players. Some old audio CD players however may produce a two second click between two audio tracks.
The minimal size of a track is 4 seconds or 300 sectors. If you write smaller tracks, the CD-Recorder will add dummy blocks. This is not an error, even though the SCSI-error message looks this way.
The Yamaha CDR-400 and all new SCSI-3/mmc conforming drives are supported in single and multi-session.
You should run several tests in all supported speeds of your drive with the -dummy option turned on if you are using wodim on an unknown system. Writing a CD is a real-time process.  NFS, CIFS and other network file systems won't always deliver constantly the needed data rates.  If you want to use wodim with CD-images that are located on a NFS mounted filesystem, be sure that the FIFO size is big enough.  If you want to make sure that buffer underruns are not caused by your source disk, you may use the command
wodim -dummy dev=2,0 padsize=600m /dev/null
to create a disk that is entirely made of dummy data.
There are also cases where you either need to be root or install wodim executable with suid-root permissions. First, if you are using a device manufactured before 1999 which requires a non-MMC driver, you should run wodim in dummy mode before writing data. If you find a problem doing this, please report it to the cdrkit maintainers (see below).
Second, certain functionality may be unusable because of Linux's SCSI command filtering. When using wodim for anything except of pure data writing, you should also test the process in dummy mode and report trouble to the contact address below.
If you still want to run wodim with root permissions, you can set the permissions of the executable to suid-root. See the additional notes of your system/program distribution or README.suidroot which is part of the cdrkit source.
You should not connect old drives that do not support disconnect/reconnect to either the SCSI bus that is connected to the CD- Recorder or the source disk.
A Compact Disc can have no more than 99 tracks.
When creating a disc with both audio and data tracks, the data should be on track 1 otherwise you should create a CDplus disk which is a multi session disk with the first session containing the audio tracks and the following session containing the data track.
Many operating systems are not able to read more than a single data track, or need special software to do so.
If you have more information or SCSI command manuals for currently unsupported CD/DVD/BR/HD-DVD-Recorders, please contact the cdrkit maintainers (see below).
Many CD recorders have bugs and often require a firmware update to work correctly. If you experience problems which cannot be solved or explained by the notes above, please look for instructions on the homepage of the particular manufacturer.
Some bugs will force you to power cycle the device or to reboot the machine.
The FIFO percent output is computed just after a block of data has been written to the CD/DVD-Recorder. For this reason, there will never be 100% FIFO fill ratio while the FIFO is in streaming mode.
You have 4 seconds to abort wodim start after you see the message:
Starting to write CD at speed %d in %s mode for %s session.  In most shells you can do that by pressing Ctrl-C.
A typical error message for a SCSI command looks like:
wodim: I/O error. test unit ready: scsi sendcmd: no error CDB:  00 20 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.002s timeout 40s
The first line gives information about the transport of the command.  The text after the first colon gives the error text for the system call from the view of the kernel. It usually is: I/O error unless other problems happen. The next words contain a short description for the SCSI command that fails. The rest of the line tells you if there were any problems for the transport of the command over the SCSI bus.  fatal error means that it was not possible to transport the command (i.e. no device present at the requested SCSI address).
The second line prints the SCSI command descriptor block for the failed command.
The third line gives information on the SCSI status code returned by the command, if the transport of the command succeeds.  This is error information from the SCSI device.
The fourth line is a hex dump of the auto request sense information for the command.
The fifth line is the error text for the sense key if available, followed by the segment number that is only valid if the command was a copy command. If the error message is not directly related to the current command, the text deferred error is appended.
The sixth line is the error text for the sense code and the sense qualifier if available.  If the type of the device is known, the sense data is decoded from tables in scsierrs.c .  The text is followed by the error value for a field replaceable unit.
The seventh line prints the block number that is related to the failed command and text for several error flags. The block number may not be valid.
The eight line reports the timeout set up for this command and the time that the command really needed to complete.
The following message is not an error:
Track 01: Total bytes read/written: 2048/2048 (1 sectors). wodim: I/O error. flush cache: scsi sendcmd: no error CDB:  35 00 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F0 00 05 80 00 00 27 0A 00 00 00 00 B5 00 00 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0xB5 Qual 0x00 (dummy data blocks added) Fru 0x0 Sense flags: Blk -2147483609 (valid) cmd finished after 0.002s timeout 40s
It simply notifies, that a track that is smaller than the minimum size has been expanded to 300 sectors.
netscsid does not work properly and is generally unmaintained. It is probably not compatible with rscsi from cdrtools either. Good bugfixes are welcome, talk to Cdrkit maintainers.
cuefile support is very limited, only one file is allowed. For volunteers, see TODO file in the source.
Specifying an audio file multiple times causes corruption of the second track (effectively no data plus minimum padding).
Some of the bugs may be fixed in Joerg Schilling's cdrtools. See there for details, URL attached below.
Joerg Schilling (schilling@fokus.fhg.de) For writing cdrecord and libscg which represent the most parts of wodim's code.
Bill Swartz    (Bill_Swartz@twolf.com) For helping me with the TEAC driver support
Aaron Newsome  (aaron.d.newsome@wdc.com) For letting me develop Sony support on his drive
Eric Youngdale (eric@andante.jic.com) For supplying mkisofs
Gadi Oxman     (gadio@netvision.net.il) For tips on the ATAPI standard
Finn Arne Gangstad  (finnag@guardian.no) For the first FIFO implementation.
Dave Platt     (dplatt@feghoot.ml.org) For creating the experimental packet writing support, the first implementation of CD-RW blanking support, the first .wav file decoder and many nice discussions on cdrecord.
Chris P. Ross (cross@eng.us.uu.net) For the first implementation of a BSDI SCSI transport.
Grant R. Guenther   (grant@torque.net) For creating the first parallel port transport implementation for Linux.
Kenneth D. Merry (ken@kdm.org) for providing the CAM port for FreeBSD together with Michael Smith (msmith@freebsd.org)
Heiko Eiszfeldt (heiko@hexco.de) for making libedc_ecc available (needed to write RAW data sectors).
If you want to actively take part on the development of wodim, you may join the developer mailing list via this URL:
https://alioth.debian.org/mail/?group_id=31006
The mail address of the list is: debburn-devel@lists.alioth.debian.org
wodim is currently maintained as part of the cdrkit project by its developers. Most of the code and this manual page was originally written by:
Joerg Schilling Seestr. 110 D-13353 Berlin Germany
This application is derived from "cdrecord" as included in the cdrtools package [1] created by Joerg Schilling, who deserves most of the credit for its success. However, he is not involved into the development of this spinoff and therefore he shall not be held responsible for any problems caused by it. Do not refer to this application as "cdrecord", do not try to get support for wodim by contacting the original authors.
Additional information can be found on: https://alioth.debian.org/projects/debburn/
If you have support questions, send them to
debburn-devel@lists.alioth.debian.org
If you have definitely found a bug, send a mail to this list or to
submit@bugs.debian.org
writing at least a short description into the Subject and "Package: cdrkit" in the first line of the mail body.
[1] Cdrtools 2.01.01a08 from May 2006, http://cdrecord.berlios.de
MONGOIMPORT(1)               General Commands Manual              MONGOIMPORT(1)
mongoimport - import CSV, TSV or JSON data into MongoDB.
mongoimport [options] [file]
The mongoimport program allows loading data in CSV, TSV or JSON form into a running MongoDB instance.
See mongoimport --help for a list supported options and their descriptions.
mongoexport(1)
The full documentation of mongoimport can be found at https://docs.mongodb.com/manual/reference/program/mongoimport/.
mongoimport was written by MongoDB, Inc. and is licensed under the Apache License, Version 2.0.
LUA(1)                       General Commands Manual                      LUA(1)
lua - Lua interpreter
lua [ options ] [ script [ args ] ]
lua is the standalone Lua interpreter.  It loads and executes Lua programs, either in textual source form or in precompiled binary form. (Precompiled binaries are output by luac, the Lua compiler.)  lua can be used as a batch interpreter and also interactively.
After handling the options, the Lua program in file script is loaded and executed.  The args are available to script as strings in a global table named arg and also as arguments to its main function.  When called without arguments, lua behaves as lua -v -i if the standard input is a terminal, and as lua - otherwise.
In interactive mode, lua prompts the user, reads lines from the standard input, and executes them as they are read.  If the line contains an expression, then the line is evaluated and the result is printed.  If a line does not contain a complete statement, then a secondary prompt is displayed and lines are read until a complete statement is formed or a syntax error is found.
Before handling command line options and scripts, lua checks the contents of the environment variables LUA_INIT_5_4 and LUA_INIT, in that order. If the contents are of the form '@filename', then filename is executed. Otherwise, the contents are assumed to be a Lua statement and is executed.  When LUA_INIT_5_4 is defined, LUA_INIT is ignored.
-e stat execute statement stat.
-i     enter interactive mode after executing script.
-l name require library name into global name.
-E     ignore environment variables.
-W     turn warnings on.
-      stop handling options and execute the standard input as a file.
The following environment variables affect the execution of lua.  When defined, the version-specific variants take priority and the version- neutral variants are ignored.
LUA_INIT, LUA_INIT_5_4 Code to be executed before command line options and scripts.
LUA_PATH, LUA_PATH_5_4 Initial value of package.cpath, the path used by require to search for Lua loaders.
LUA_CPATH, LUA_CPATH_5_4 Initial value of package.cpath, the path used by require to search for C loaders.
If a script calls os.exit, then lua exits with the given exit status. Otherwise, lua exits with EXIT_SUCCESS (0 on POSIX systems) if there were no errors and with EXIT_FAILURE (1 on POSIX systems) if there were errors.  Errors raised in interactive mode do not cause exits.
luac(1) The documentation at lua.org, especially section 7 of the reference manual.
DOCKER-COMPOSE(1)                 User Commands                DOCKER-COMPOSE(1)
docker-compose - Define and run multi-container applications with Docker.
docker-compose [OPTIONS] [COMMAND] [ARGS]...
docker-compose allows you to define a multi-container application with all of its dependencies in a single file, then spin the application up in a single command. The applicationâ€™s structure and configuration are held in a single place, which makes spinning up applications simple and repeatable everywhere.
-f, --file FILE Specify an alternate compose file (default: docker-compose.yml)
-p, --project-name NAME Specify an alternate project name (default: directory name)
--verbose Show more output
-v, --version Print version and exit
build Build or rebuild services
--no-cache Do not use cache when building the image.
help Displays help and usage information on a command.
kill Forces running containers to stop by sending a SIGKILL signal.
-s SIGNAL SIGNAL to send to the container. Default signal is SIGKILL.
logs View output from containers.
--no-color Produce a monochrome output.
port Print the public port for a port binding
--protocol=proto Choose the 4th layer protocol, tcp or udp. Default is tcp.
--index=index Index of the container if there are multiple instances of a service. Default is 1.
ps List containers.
-q     Only display IDs.
pull Pulls service images from Docker registry.
--allow-insecure-ssl Allow insecure connections to the Docker registry.
restart Restart running containers.
-t, --timeout TIMEOUT Specify a shutdown timeout in seconds. Default is 10.
rm Remove stopped service containers
-f, --force Do not ask to confirm removal.
-v     Remove volumes associated with containers.
run Run a one-off command on a service. By default linked services will be started, unless they are already running.
-d     Detached mode. Run container in the background, print new container name.
--entrypoint CMD Override the entrypoint of the image with CMD.
-e KEY=VAL Set an environment variable. Can be used multiple times.
-u, --user=USER Run as a specific USER, a username or uid.
--no-deps Do not start linked services.
--rm   Remove container after run. This option is ignored in the detached mode.
--service-ports Run command with the service's ports enabled and mapped to the host.
-T     Disable pseudo tty allocation. By default a tty is allocated.
scale Set number of containers to run for a service. Numbers are specified in the form service=num as arguments.
# docker-compose scale web=2 worker=3
start Start existing containers.
stop Stop running containers without removing them.
up Build, (re)create, start and attach to containers.  If there are existing containers for a service, `docker-compose up` will stop and recreate them (preserving mounted volumes with volumes-from), so that changes in `docker-compose.yml` are picked up. If you do not want existing containers to be recreated, `docker-compose up --no-recreate` will re-use existing containers.
--x-smart-recreate Only recreate containers whose configuration or image needs to be updated. This feature is experimental.
--no-recreate If containers already exist, do not recreate them.
--no-build Do not build an image even if it is missing.
migrate-to-labels Recreate containers to add labels. If docker-compose detects containers that were created without labels, it will refuse to run so that you don't end up with two sets of them.
Several environmental variables are available to configure docker-compose behavior.
Variables starting with DOCKER_ are the same as those used to configure the Docker command-line client. If you're using boot2docker, eval "$(boot2docker shellinit)" will set them to their correct values.
COMPOSE_PROJECT_NAME Sets the project name, which is prepended to the name of every container started by docker-compose.  Defaults to the basename of the current working directory.
COMPOSE_FILE Specify what file to read configuration from. If not provided, docker-compose will look for docker-compose.yml in the current working directory, and then each parent directory successively, until found.
DOCKER_HOST Sets the URL of the docker daemon. As with the Docker client, defaults to unix:///var/run/docker.sock.
DOCKER_TLS_VERIFY When set to anything other than an empty string, enables TLS communication with the daemon.
DOCKER_CERT_PATH Configures the path to the ca.pem, cert.pem, and key.pem files used for TLS verification.  Defaults to ~/.docker.
Full documentation for docker-compose at: <http://docs.docker.com/compose/>
This manual page was written by Dariusz Dwornikowski <dariusz.dwornikowski@cs.put.poznan.pl> based on the official docker compose documentation.
OKULAR(1)                     Okular User's Manual                     OKULAR(1)
okular - a universal document viewer
okular [Okular options] [URL]
okular is aimed to show documents in different formats.
-p, --page number
Open a given page in the document.
--presentation
Start the document in presentation mode.
Start with print dialog.
--print-and-exit
Start with print dialog and exit after printing.
--unique
Unique instance control.
--noraise
Allows to prevent Okular window raising after the start.
--find string
Find a string on the text.
An address of the document to be opened. For PDF, can be given as document_name#named_destination where named_destination is a particular named destination embedded in the document.
On IRC, irc.libera.chat #okular or via email, okular-devel@kde.org or on the web, <https://okular.kde.org/>.
More detailed user documentation is available from help:/okular (either enter this URL into Konqueror, or run khelpcenter help:/okular). kf5options(7) qt5options(7) There is also further information available at https://okular.kde.org/
Copyright (c) 2002 Wilco Greven, Christophe Devriese
Copyright (c) 2004-2005 Enrico Ros
Copyright (c) 2005 Piotr Szymanski
Copyright (c) 2004-2012 Albert Astals Cid
Copyright (c) 2006-2009 Pino Toscano
License: GNU General Public Version 2 <https://www.gnu.org/licenses/gpl-2.0.html>
Yuri Chornoivan <yurchor@ukr.net> Okular man page.
CLEMENTINE(1)                General Commands Manual               CLEMENTINE(1)
clementine - A modern music player and library organizer
clementine [options] [URL(s)]
Clementine is a multiplatform music player focusing on a fast and easy- to-use interface for searching and playing your music.
Features : - Search and play your local music library. - Listen to internet radio from ROCKRADIO.com, RadioTunes.com, IntergalacticFM, SomaFM, Magnatune, Jamendo, Digitally Imported, ClassicalRadio.com, JAZZRADIO.com, Icecast and Subsonic servers. - Search and play songs you've uploaded to SeaFile, Box, Dropbox, Google Drive, and OneDrive. - Create smart playlists and dynamic playlists. - Tabbed playlists, import and export M3U, XSPF, PLS and ASX. - CUE sheet support. - Play audio CDs. - Visualisations from projectM. - Lyrics and artist biographies and photos. - Transcode music into MP3, Ogg Vorbis, Ogg Speex, FLAC or AAC. - Edit tags on MP3 and OGG files, organise your music. - Fetch missing tags from MusicBrainz. - Discover and download Podcasts. - Download missing album cover art from Last.fm. - Native desktop notifications using libnotify. - Remote control using an Android device, a Wii Remote, MPRIS or the command-line. - Copy music to your iPod, iPhone, MTP or mass-storage USB player. - Queue manager.
These programs follow the usual GNU command line syntax, with long options starting with two dashes (`-').  A summary of options is included below.  For a complete description, see the Info files.
Player options :
-p           --play Start the playlist currently playing.
-t           --play-pause Play if stopped, pause if playing.
-u           --pause Pause playback
-s           --stop Stop playback
-q           --stop-after-current Stop playback after current track
-r           --previous Skip backwards in playlist.
-f           --next Skip forwards in playlist.
-v           --volume <value> Set the volume to <value> percent.
--volume-up Increase the volume by 4%.
--volume-down Decrease the volume by 4%..
--seek-to <seconds> Seek the currently playing track to an absolute position.
--seek-by <seconds> Seek the currently playing track by a relative amount.
Playlist options:
-c           --create <name> Create a new playlist with files/URLs.
-a           --append Append files/URLs to the playlist.
-l           --load Loads files/URLs, replacing current playlist.
-k           --play-track <n> Play the <n>th track in the playlist
-o           --show-osd Display the on-screen-display.
-y           --toggle-pretty-osd Toggle visibility for the pretty on-screen-display
-g           --language <lang> Change the language
--quiet   Equivalent to --log-levels *:1
--verbose Equivalent to --log-levels *:3
--log-levels <levels> Comma separated list of class:level, level is 0-3
--version Print out version information
Clementine main authors are David Sansome me@davidsansome.com and John Maguire john.maguire@gmail.com.
This manual page was written by Thomas PIERSON contact@thomaspierson.fr for the Debian system (and may be used by others).  Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 any later version published by the Free Software Foundation.
On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-3.
UFRAW(1)                                                                UFRAW(1)
UFRaw - Convert camera RAW images to standard image files.
ufraw [OPTIONS] <rawfile(s)> ufraw-batch [OPTIONS] <rawfile(s)>
The Unidentified Flying Raw (UFRaw) is a utility to read and manipulate raw images from digital cameras. It reads raw images using Dave Coffin's raw conversion utility - DCRaw. UFRaw supports basic color management using Little CMS, allowing the user to apply color profiles. For Nikon users UFRaw has the advantage that it can read the camera's tone curves. Even if you don't own a Nikon, you can still apply a Nikon curve to your images.
By default 'ufraw' displays a preview window for each raw image allowing the user to tweak the image parameters before saving. If no raw images are given at the command line, UFRaw will display a file chooser dialog. To process the images with no questions asked (and no preview) use the command 'ufraw-batch'.
The input files can be either raw images or UFRaw ID-files.  ID-files contain a raw image filename and the parameters for handling the image.
UFRaw can also work as a GIMP plug-in. To activate it simply open a raw image or a UFRaw ID-file in the GIMP.
The options supplied on the command-line decide the starting-values for the GUI. The GUI will then allow you to tweak these values before saving the final image.
General Options --version Display the version of UFRaw and exit.
--help Display a brief description of how to use UFRaw and exit.
--maximize-window Force window to be maximized.
--silent Do not display any messages during conversion. This option is only valid with 'ufraw-batch'.
--conf=<ID-filename> Load all parameters from an ID-file. This feature can be used to tweak the parameters for one file using the GUI and using those parameters as the starting point for other images as well.
Image Manipulation Options These command-line options override settings from the default configuration of UFRaw and from any loaded ID-file. The best way to learn about how these parameters work is to experiment with the GUI. All parameters correspond exactly to a setting available in the GUI. Not all parameters in the GUI have corresponding command-line options.
--wb=camera|auto White balance setting. "camera" means that UFRaw tries to read the color-temperature and green color component that the camera recorded in the meta-information in the raw-file. This does not work for all cameras. If UFRaw fails to read the white-balance information from the meta-information, it falls back to "auto".
"auto" means that UFRaw calculates the color-temperature and green color component automatically from the image data.
The white-balance can also be set manually with the --temperature and --green options.
--temperature=TEMP Manually set the color temperature in Kelvin.
--green=GREEN Green color component. Range 0.20 to 2.50.
--gamma=GAMMA Gamma adjustment of the base curve. Range 0.10 to 1.00. Default 0.45.
--linearity=LINEARITY Linearity of the base curve. Range 0.00 to 1.00. Default 0.10.
--exposure=auto|EXPOSURE Auto exposure or exposure correction in EV. Range -3.00 to 3.00. Default 0.
--restore=clip|lch|hsv Control how highlights are restored when applying negative EV. 'clip' restores nothing and is therefore safe from any artifacts. 'lch' restores in LCH space, resulting in restored highlights with soft details (good for clouds).  'hsv' restores in HSV space, resulting in restored highlights with sharp details.  The default is 'lch'.
--clip=digital|film Control how highlights are clipped when applying positive EV. 'digital' corresponds to using a linear response, emulating the harsh behaviour of the digital sensor.  'film' emulate the soft film response.  The default is 'digital'.
--saturation=SAT Adjust the color saturation. Range 0.00 to 8.00. Default 1.0, use 0 for black & white output.
--wavelet-denoising-threshold=THRESHOLD Wavelet denoising threshold (default 0.0).
--hotpixel-sensitivity=VALUE Sensitivity for detecting and shaving hot pixels (default 0.0).
--base-curve=manual|linear|custom|camera|CURVE Type of tone curve to use. The base curve is a combination of the gamma curve corrected by the curve specified here.  The base curve is applied to each channel of the raw data after the white balance and color matrix, but before the ICC transformation.
"manual" means that a manual tone curve is used.  This is probably not very useful as a command-line option, since there is no way to specify what the curve should look like.
"linear" means that no tone curve corrections is performed.
"custom" means that UFRaw shall use the curve supplied by the camera in the meta-information in the raw-file.
"camera" means that UFRaw shall use the "custom" curve only if the camera was set to use it (according to the meta-information). Otherwise the "linear" curve is used.
CURVE can be the filename (without path) of any curve that was previously loaded in the GUI.
The default is "camera" if such a curve exists, linear otherwise.
--base-curve-file=<curve-file> Load the base curve from a file.  The curve file format can be either UFRaw's XML format or Nikon's NTC/NCV format.
--curve=manual|linear|CURVE Type of luminosity curve to use. This curve is applied in HSV space and therefore hue and saturation should not be effected by it.
"manual" means that a manual luminosity curve is used.  This is probably not very useful as a command-line option, since there is no way to specify what the curve should look like.
"linear" means that no luminosity correction is performed.
The default is "linear".
--curve-file=<curve-file> Load the luminosity curve from a file.  The curve file format can be either UFRaw's XML format or Nikon's NTC/NCV format.
--black-point=auto|BLACK Black-point value. Range 0.0 to 1.0, default 0.0.
--interpolation=ahd|vng|four-color|ppg|bilinear Interpolation algorithm to use when converting from the color filter array to normal RGB values. AHD (Adaptive Homogeneity Directed) interpolation is the best, but also the slowest. VNG (Variable Number Gradients) is second best and a bit faster. Bilinear is the simplest yet fastest interpolation.
"four-color" is a variation of the VNG interpolation that should only be used if you see strange square patterns in the VNG interpolation, See <http://www.cybercom.net/~dcoffin/dcraw/>.
AHD is the default interpolation.  AHD interpolation is not supported for cameras with four color filters, such as the Sony-828 RGBE filter. In such cases, VNG interpolation will be used instead.
--color-smoothing Apply color smoothing.
--grayscale=none|lightness|luminance|value|mixer Grayscale conversion algorithm to use (default none).
--grayscale-mixer=RED,GREEN,BLUE Grayscale mixer values to use (default 1,1,1).
--darkframe=FILE Use FILE for raw darkframe subtraction.
Output Options The options which are related to the final output are:
--shrink=FACTOR Shrink the image by FACTOR (default 1).
--size=SIZE Downsize max(height,width) to SIZE.
--rotate=camera|ANGLE|no Rotate image to camera's setting, by ANGLE degrees clockwise, or do not rotate the image (default camera)
--crop-(left|right|top|bottom)=PIXELS Crop the output to the given pixel range, relative to the raw image after rotation but before any scaling.
--auto-crop Crop the output automatically.
--aspect-ratio X:Y Set crop area aspect ratio.
--lensfun=none|auto Do not apply lens correction or try to apply correction by auto- detecting the lens (default auto).
--out-type=ppm|tiff|tif|png|jpeg|jpg|fits Output file-format to use.  The default output file-format is ppm.
--out-depth=8|16 Output bit depth per channel.  ppm, tiff, png and fits output formats can uses either 8 bits or 16 bits to encode each of the  Red, Green and Blue components of each pixel.  The jpeg format only allows for 8 bits for each color component.
The raw-files contain more than eight bits of information for each color component. This means that by using an eight bit format, you are actually discarding some of the information supplied by the camera. This is not a problem if you only plan to view the image on screen. For prints you should consider a 16 bits workflow.
--compression=VALUE JPEG quality factor. Range 0-100 with a higher number giving a higher quality at the cost of a larger file. Default 85. The --compression parameter is only relevant if the output file-format is jpeg.
--[no]exif Embed exif in output. Default embed exif. Exif is currently embedded in JPEG, PNG and TIFF output.
--[no]zip Enable [disable] TIFF zip compression. The zip-compression is loss- less.  Default nozip. The --zip parameter is only relevant if the output file-format if tiff8 or tiff16.
--out-path=PATH PATH for output file. In batch mode by default, output-files are placed in the same directory as the input-files. In interactive mode UFRaw tries to ''guess'' if you have a favorite output directory.
--output=FILE Output file name to use. This is only relevant if a single raw-file is supplied on the command-line. . Use '-' to output to stdout. The default is to name the output-file the same as the input-file but with the extension given by the output file-format.
--overwrite Overwrite existing files without asking. Default is to ask before deleting an existing file.
--create-id=no|also|only Control whether UFRaw ID files are created for the output image. (Default is no).
--embedded-image Extract the preview image embedded in the raw file instead of converting the raw image. This option is only valid with 'ufraw-batch'.
Conversion Setting Priority Conversion settings are applied in the following priority order:
1. Command-line options 2. Settings from the configuration file specified with --conf=<ID-file> (ignoring any filenames in the ID-file). 3. Settings from an ID-file supplied as an input-file. 4. Settings from $HOME/.ufrawrc 5. UFRaw's default settings.
This means that an option supplied on the command-line always takes precedence over all other options.
The conversion settings can be changed in the GUI before the resulting image is saved.
$HOME/.ufrawrc or $HOME/.config/ufrawrc (depending on the system) - UFRaw resource file containing the user default settings. This is an XML file that can be modified with any text editor. Still, it is recommended not to edit this file. This file is updated from the GUI when you save an image, or when you explicitly ask to save this file in the 'Options' menu.
$HOME/.ufraw-gtkrc - An optional file for setting up a specific GTK theme for UFRaw.
UFRaw homepage: <http://ufraw.sourceforge.net> DCRaw homepage: <http://www.cybercom.net/~dcoffin/dcraw>
The GIMP homepage: <http://www.gimp.org>
GIT-COMMITS-SINCE(1)               Git Extras               GIT-COMMITS-SINCE(1)
git-commits-since - Show commit logs since some date
git-commits-since [<date>]
List of commits since the given date.
<date>
Show commits more recent than date. By default, the command shows the commit logs since "last week".
It is really flexible and these are only 3 of the options, go ahead give it a try:
$ git commits-since yesterday `... commits since yesterday` nickl- - Merge branch upstream master. nickl- - Rebase bolshakov with master TJ Holowaychuk - Merge pull request #128 from nickl-/git-extras-html-hyperlinks TJ Holowaychuk - Merge pull request #129 from nickl-/develop nickl- - Fix #127 git-ignore wonÂ´t add duplicates.
$ git commits-since 3 o clock pm `... commits since 3 o clock pm` nickl- - Merge branch upstream master.
$ git commits-since 2 hour ago `... commits since 2 hour ago` nickl- - Merge branch upstream master. TJ Holowaychuk - Merge pull request #128 from nickl-/git-extras-html-hyperlinks TJ Holowaychuk - Merge pull request #129 from nickl-/develop
cowsay(6)                         Games Manual                         cowsay(6)
cowsay/cowthink - configurable speaking/thinking cow (and a bit more)
cowsay [-e eye_string] [-f cowfile] [-h] [-l] [-n] [-T tongue_string] [-W column] [-bdgpstwy]
Cowsay generates an ASCII picture of a cow saying something provided by the user.  If run with no arguments, it accepts standard input, word- wraps the message given at about 40 columns, and prints the cow saying the given message on standard output.
To aid in the use of arbitrary messages with arbitrary whitespace, use the -n option.  If it is specified, the given message will not be word- wrapped.  This is possibly useful if you want to make the cow think or speak in figlet(6).  If -n is specified, there must not be any command- line arguments left after all the switches have been processed.
The -W specifies roughly where the message should be wrapped.  The default is equivalent to -W 40 i.e. wrap words at or before the 40th column.
If any command-line arguments are left over after all switches have been processed, they become the cow's message.  The program will not accept standard input for a message in this case.
There are several provided modes which change the appearance of the cow depending on its particular emotional/physical state.  The -b option initiates Borg mode; -d causes the cow to appear dead; -g invokes greedy mode; -p causes a state of paranoia to come over the cow; -s makes the cow appear thoroughly stoned; -t yields a tired cow; -w is somewhat the opposite of -t, and initiates wired mode; -y brings on the cow's youthful appearance.
The user may specify the -e option to select the appearance of the cow's eyes, in which case the first two characters of the argument string eye_string will be used.  The default eyes are 'oo'.  The tongue is similarly configurable through -T and tongue_string; it must be two characters and does not appear by default.  However, it does appear in the 'dead' and 'stoned' modes.  Any configuration done by -e and -T will be lost if one of the provided modes is used.
The -f option specifies a particular cow picture file (``cowfile'') to use.  If the cowfile spec contains '/' then it will be interpreted as a path relative to the current directory.  Otherwise, cowsay will search the path specified in the COWPATH environment variable.  To list all cowfiles on the current COWPATH, invoke cowsay with the -l switch.
If the program is invoked as cowthink then the cow will think its message instead of saying it.
A cowfile is made up of a simple block of perl(1) code, which assigns a picture of a cow to the variable $the_cow.  Should you wish to customize the eyes or the tongue of the cow, then the variables $eyes and $tongue may be used.  The trail leading up to the cow's message balloon is composed of the character(s) in the $thoughts variable.  Any backslashes must be reduplicated to prevent interpolation.  The name of a cowfile should end with .cow, otherwise it is assumed not to be a cowfile.  Also, at-signs (``@'') must be backslashed because that is what Perl 5 expects.
What older versions? :-)
Version 3.x is fully backward-compatible with 2.x versions.  If you're still using a 1.x version, consider upgrading.  And tell me where you got the older versions, since I didn't exactly put them up for world-wide access.
Oh, just so you know, this manual page documents version 3.03 of cowsay.
The COWPATH environment variable, if present, will be used to search for cowfiles.  It contains a colon-separated list of directories, much like PATH or MANPATH.  It should always contain the /usr/share/cowsay/cows directory, or at least a directory with a file called default.cow in it.
/usr/share/cowsay/cows holds a sample set of cowfiles.  If your COWPATH is not explicitly set, it automatically contains this directory.
If there are any, please notify the author at the address below.
Tony Monroe (tony@nog.net), with suggestions from Shannon Appel (appel@CSUA.Berkeley.EDU) and contributions from Anthony Polito (aspolito@CSUA.Berkeley.EDU).
perl(1), wall(1), nwrite(1), figlet(6)
watson(1)                     Monitoring your time                     watson(1)
watson - helps you monitoring your time
watson [OPTIONS] COMMAND [ARGS]...
Watson is a tool aimed at helping you monitoring your time.
You just have to tell Watson when you start working on your project with the `start` command, and you can stop the timer when you're done with the `stop` command.
‐‐version Show the version and exit.
‐‐help Show this manpage and exit.
cancel Cancel the last call to the start command. The time will not be recorded.
config Get and set configuration options.
edit   Edit a frame.
frames Display the list of all frame IDs.
help   Display help information.
log    Display each recorded session during the given timespan
merge  Perform a merge of the existing frames with a conflicting frames file.
projects Display the list of all the existing projects.
remove Remove a frame.
rename Rename a project or tag.
report Display a report of the time spent on each project.
restart Restart monitoring time for a previously stopped project.
start  Start monitoring time for the given project.
status Display when the current project was started and the time spent since.
stop   Stop monitoring time for the current project.
sync   Get the frames from the server and push the new ones.
tags   Display the list of all the tags.
This manual page was generate by genallman shellscript that uses txt2man. The script was created by Joao Eriberto Mota Filho <eriberto@debian.org>. The manpage was made for the watson package of the Debian project (but may be used by others)
If more information is necessary, please read the online documentation at https://tailordev.github.io/Watson/user-guide/commands/
Pandoc User’s Guide()                                      Pandoc User’s Guide()
pandoc - general markup converter
pandoc [options] [input-file]...
Pandoc is a Haskell library for converting from one markup format to another, and a command-line tool that uses this library.
Pandoc can convert between numerous markup and word processing formats, including, but not limited to, various flavors of Markdown, HTML, LaTeX and Word docx.  For the full lists of input and output formats, see the --from and --to options below.  Pandoc can also produce PDF output: see creating a PDF, below.
Pandoc’s enhanced version of Markdown includes syntax for tables, definition lists, metadata blocks, footnotes, citations, math, and much more.  See below under Pandoc’s Markdown.
Pandoc has a modular design: it consists of a set of readers, which parse text in a given format and produce a native representation of the document (an abstract syntax tree or AST), and a set of writers, which convert this native representation into a target format.  Thus, adding an input or output format requires only adding a reader or writer.  Users can also run custom pandoc filters to modify the intermediate AST.
Because pandoc’s intermediate representation of a document is less expressive than many of the formats it converts between, one should not expect perfect conversions between every format and every other.  Pandoc attempts to preserve the structural elements of a document, but not formatting details such as margin size.  And some document elements, such as complex tables, may not fit into pandoc’s simple document model. While conversions from pandoc’s Markdown to all formats aspire to be perfect, conversions from formats more expressive than pandoc’s Markdown can be expected to be lossy.
Using pandoc If no input-files are specified, input is read from stdin.  Output goes to stdout by default.  For output to a file, use the -o option:
pandoc -o output.html input.txt
By default, pandoc produces a document fragment.  To produce a standalone document (e.g. a valid HTML file including <head> and <body>), use the -s or --standalone flag:
pandoc -s -o output.html input.txt
For more information on how standalone documents are produced, see Templates below.
If multiple input files are given, pandoc will concatenate them all (with blank lines between them) before parsing.  (Use --file-scope to parse files individually.)
Specifying formats The format of the input and output can be specified explicitly using command-line options.  The input format can be specified using the -f/--from option, the output format using the -t/--to option.  Thus, to convert hello.txt from Markdown to LaTeX, you could type:
pandoc -f markdown -t latex hello.txt
To convert hello.html from HTML to Markdown:
pandoc -f html -t markdown hello.html
Supported input and output formats are listed below under Options (see -f for input formats and -t for output formats).  You can also use pandoc --list-input-formats and pandoc --list-output-formats to print lists of supported formats.
If the input or output format is not specified explicitly, pandoc will attempt to guess it from the extensions of the filenames.  Thus, for example,
pandoc -o hello.tex hello.txt
will convert hello.txt from Markdown to LaTeX.  If no output file is specified (so that output goes to stdout), or if the output file’s extension is unknown, the output format will default to HTML.  If no input file is specified (so that input comes from stdin), or if the input files’ extensions are unknown, the input format will be assumed to be Markdown.
Character encoding Pandoc uses the UTF-8 character encoding for both input and output.  If your local character encoding is not UTF-8, you should pipe input and output through iconv:
iconv -t utf-8 input.txt | pandoc | iconv -f utf-8
Note that in some output formats (such as HTML, LaTeX, ConTeXt, RTF, OPML, DocBook, and Texinfo), information about the character encoding is included in the document header, which will only be included if you use the -s/--standalone option.
Creating a PDF To produce a PDF, specify an output file with a .pdf extension:
pandoc test.txt -o test.pdf
By default, pandoc will use LaTeX to create the PDF, which requires that a LaTeX engine be installed (see --pdf-engine below).  Alternatively, pandoc can use ConTeXt, roff ms, or HTML as an intermediate format.  To do this, specify an output file with a .pdf extension, as before, but add the --pdf-engine option or -t context, -t html, or -t ms to the command line.  The tool used to generate the PDF from the intermediate format may be specified using --pdf-engine.
You can control the PDF style using variables, depending on the intermediate format used: see variables for LaTeX, variables for ConTeXt, variables for wkhtmltopdf, variables for ms.  When HTML is used as an intermediate format, the output can be styled using --css.
To debug the PDF creation, it can be useful to look at the intermediate representation: instead of -o test.pdf, use for example -s -o test.tex to output the generated LaTeX.  You can then test it with pdflatex test.tex.
When using LaTeX, the following packages need to be available (they are included with all recent versions of TeX Live): amsfonts, amsmath, lm, unicode-math, iftex, listings (if the --listings option is used), fancyvrb, longtable, booktabs, graphicx (if the document contains images), hyperref, xcolor, ulem, geometry (with the geometry variable set), setspace (with linestretch), and babel (with lang).  The use of xelatex or lualatex as the PDF engine requires fontspec.  lualatex uses selnolig.  xelatex uses polyglossia (with lang), xecjk, and bidi (with the dir variable set).  If the mathspec variable is set, xelatex will use mathspec instead of unicode-math.  The upquote and microtype packages are used if available, and csquotes will be used for typography if the csquotes variable or metadata field is set to a true value.  The natbib, biblatex, bibtex, and biber packages can optionally be used for citation rendering.  The following packages will be used to improve output quality if present, but pandoc does not require them to be present: upquote (for straight quotes in verbatim environments), microtype (for better spacing adjustments), parskip (for better inter-paragraph spaces), xurl (for better line breaks in URLs), bookmark (for better PDF bookmarks), and footnotehyper or footnote (to allow footnotes in tables).
Reading from the Web Instead of an input file, an absolute URI may be given.  In this case pandoc will fetch the content using HTTP:
pandoc -f html -t markdown https://www.fsf.org
It is possible to supply a custom User-Agent string or other header when requesting a document from a URL:
pandoc -f html -t markdown --request-header User-Agent:"Mozilla/5.0" \ https://www.fsf.org
General options -f FORMAT, -r FORMAT, --from=FORMAT, --read=FORMAT Specify input format.  FORMAT can be:
• bibtex (BibTeX bibliography)
• biblatex (BibLaTeX bibliography)
• commonmark (CommonMark Markdown)
• commonmark_x (CommonMark Markdown with extensions)
• creole (Creole 1.0)
• csljson (CSL JSON bibliography)
• csv (CSV table)
• docbook (DocBook)
• docx (Word docx)
• dokuwiki (DokuWiki markup)
• epub (EPUB)
• fb2 (FictionBook2 e-book)
• gfm (GitHub-Flavored Markdown), or the deprecated and less accurate markdown_github; use markdown_github only if you need extensions not supported in gfm.
• haddock (Haddock markup)
• html (HTML)
• ipynb (Jupyter notebook)
• jats (JATS XML)
• jira (Jira/Confluence wiki markup)
• json (JSON version of native AST)
• latex (LaTeX)
• markdown (Pandoc’s Markdown)
• markdown_mmd (MultiMarkdown)
• markdown_phpextra (PHP Markdown Extra)
• markdown_strict (original unextended Markdown)
• mediawiki (MediaWiki markup)
• man (roff man)
• muse (Muse)
• native (native Haskell)
• odt (ODT)
• opml (OPML)
• org (Emacs Org mode)
• rst (reStructuredText)
• t2t (txt2tags)
• textile (Textile)
• tikiwiki (TikiWiki markup)
• twiki (TWiki markup)
• vimwiki (Vimwiki)
Extensions can be individually enabled or disabled by appending +EXTENSION or -EXTENSION to the format name.  See Extensions below, for a list of extensions and their names.  See --list- input-formats and --list-extensions, below.
-t FORMAT, -w FORMAT, --to=FORMAT, --write=FORMAT Specify output format.  FORMAT can be:
• asciidoc (AsciiDoc) or asciidoctor (AsciiDoctor)
• beamer (LaTeX beamer slide show)
• context (ConTeXt)
• docbook or docbook4 (DocBook 4)
• docbook5 (DocBook 5)
• epub or epub3 (EPUB v3 book)
• epub2 (EPUB v2)
• html or html5 (HTML, i.e. HTML5/XHTML polyglot markup)
• html4 (XHTML 1.0 Transitional)
• icml (InDesign ICML)
• jats_archiving (JATS XML, Archiving and Interchange Tag Set)
• jats_articleauthoring (JATS XML, Article Authoring Tag Set)
• jats_publishing (JATS XML, Journal Publishing Tag Set)
• jats (alias for jats_archiving)
• ms (roff ms)
• muse (Muse),
• native (native Haskell),
• odt (OpenOffice text document)
• opendocument (OpenDocument)
• pdf (PDF)
• plain (plain text),
• pptx (PowerPoint slide show)
• rtf (Rich Text Format)
• texinfo (GNU Texinfo)
• slideous (Slideous HTML and JavaScript slide show)
• slidy (Slidy HTML and JavaScript slide show)