neulab/tldr huggingface dataset:
/proc/stat contains system statistics. /proc/uptime contains system uptime. /proc/diskstats contains disks statistics. /sys contains statistics for block devices. /proc/self/mountstats contains statistics for network filesystems. /dev/disk contains persistent device names.
sar(1), pidstat(1), mpstat(1), vmstat(8), tapestat(1), nfsiostat(1), cifsiostat(1)
ARDUINO(1)                                                            ARDUINO(1)
arduino - Integrated development environment for Arduino boards
arduino [FILE.ino...]
arduino [--verify|--upload] [--board package:arch:board[:parameters]] [--port portname] [--pref name=value] [-v|--verbose] [--preserve-temp-files] [FILE.ino]
arduino [--get-pref [preference]]
arduino [--install-boards package name:platform architecture[:version]]
arduino [--install-library library name[:version][,library name[:version],library name[:version]]
arduino [--version]
The arduino integrated development environment allows editing, compiling and uploading sketches (programs) for Arduino (and compatible) microcontroller boards.
Normally, running the arduino command starts the IDE, optionally loading any .ino files specified on the commandline.
Alternatively, if any of the following command line options is given, no graphical interface will be shown and instead a one-off verify (compile) or upload will be done. A single .ino file should be given. If the sketch contains multiple .ino files, any one can be specified on the commandline, but the entire sketch will be compiled.
When running in a one-off mode, it might be useful to set the build.path preference to allow keeping intermediate build results between multiple runs and only recompile the files that changed.
Note that on MacOS X, the main executable is Arduino.app/Contents/MacOS/Arduino instead of arduino.
Note that on Windows, due to the diffence between GUI and console apps, that the arduino_debug.exe is the appropriate executable to use if you want to use the majority of these command line options. The arduino.exe GUI version of the launcher may perform some of the functions described below, but will not output any messages to the console, meaning it is pretty useless if you want any feedback or to be able to keep log files for automated testing, etc.
--verify Build the sketch.
--upload Build and upload the sketch.
--get-pref [preference] Prints the value of the given preference to the standard output stream. When the value does not exist, nothing is printed and the exit status is set (see EXIT STATUS below). If no preference is given as parameter, it prints all preferences.
--install-boards package name:platform architecture[:version] Fetches available board support (platform) list and install the specified one, along with its related tools. If version is omitted, the latest is installed. If a platform with the same version is already installed, nothing is installed and program exits with exit code 1. If a platform with a different version is already installed, it’s replaced.
--install-library library name[:version] Fetches available libraries list and install the specified one. If version is omitted, the latest is installed. If a library with the same version is already installed, nothing is installed and program exits with exit code 1. If a library with a different version is already installed, it’s replaced. Multiple libraries can be specified, separated by a comma.
--version Print the version information and exit.
--board package:arch:board[:parameters] Select the board to compile for.
•   package is the identifier of the vendor (the first level folders inside the hardware directory). Default arduino boards use arduino.
•   architecture is the architecture of the board (second level folders inside the hardware directory). Default arduino boards use either arduino:avr for all AVR-based boards (like Uno, Mega or Leonardo) or arduino:sam for 32bit SAM-based boards (like Arduino Due).
•   board is the actual board to use, as defined in boards.txt contained in the architecture folder selected. For example, arduino:avr:uno for the Arduino Uno, arduino:avr:diecimila for the Arduino Duemilanove or Diecimila, or arduino:avr:mega for the Arduino Mega.
•   parameters is a comma-separated list of boards specific parameters that are normally shown under submenus of the "Tools" menu. For example arduino:avr:nano:cpu=atmega168 to Select the mega168 variant of the Arduino Nano board.
If this option is not passed, the value from the current preferences is used (e.g., the last board selected in the IDE).
--port portname Select the serial port to perform upload of the sketch. On linux and MacOS X, this should be the path to a device file (e.g., /dev/ttyACM0). On Windows, this should be the name of the serial port (e.g., COM3).
If this option is not passed, the value from the current preferences is used (e.g., the last port selected in the IDE).
--verbose-build Enable verbose mode during build. If this option is not given, verbose mode during build is disabled regardless of the current preferences.
--preserve-temp-files Keep temporary files (preprocessed sketch, object files...) after termination. If omitted, temporary files are deleted.
This option is only valid together with --verify or --upload.
--useprogrammer Upload using a programmer. Set if you’re using an external programmer, or using the Arduino as ISP.
--verbose-upload Enable verbose mode during upload. If this option is not given, verbose mode during upload is disabled regardless of the current preferences.
-v, --verbose Enable verbose mode during build and upload. This option has the same effect of using both --verbose-build and --verbose-upload.
--preferences-file filename Read and store preferences from the specified filename instead of the default one.
--pref name=value Sets the preference name to the given value.
Note that the preferences you set with this option are not validated: Invalid names will be set but never used, invalid values might lead to an error later on.
--save-prefs Save any (changed) preferences to preferences.txt. In particular --board, --port, --pref, --verbose, --verbose-build and --verbose-upload may alter the current preferences.
Arduino keeps a list of preferences, as simple name and value pairs. Below, a few of them are documented but a lot more are available.
sketchbook.path The path where sketches are (usually) stored. This path can also contain some special subdirectories (see FILES below).
update.check When set to true, the IDE checks for a new version on startup.
editor.external When set to true, use an external editor (the IDE does not allow editing and reloads each file before verifying).
build.path The path to use for building. This is where things like the preprocessed .cpp file, compiled .o files and the final .hex file go.
If set, this directory should already exist before running the arduino command.
If this preference is not set (which is normally the case), a new temporary build folder is created on every run and deleted again when the application is closed.
1 Build failed or upload failed
2 Sketch not found
3 Invalid (argument for) commandline option
4 Preference passed to --get-pref does not exist
%LOCALAPPDATA%/Arduino15/preferences.txt (Windows), ~/Library/Arduino15/preferences.txt (Max OS X), ~/.arduino15/preferences.txt (Linux) This file stores the preferences used for the IDE, building and uploading sketches.
My Documents/Arduino/ (Windows), ~/Documents/Arduino/ (Mac OS X), ~/Arduino/ (Linux) This directory is referred to as the "Sketchbook" and contains the user’s sketches. The path can be changed through the sketchbook.path preference.
Apart from sketches, three special directories can be inside the sketchbook:
libraries Libraries can be put inside this directory, one library per subdirectory.
hardware Support for third-party hardware can be added through this directory.
tools External code-processing tools (that can be run through the Tools menu of the IDE) can be added here.
Start the Arduino IDE, with two files open:
arduino /path/to/sketch/sketch.ino /path/to/sketch/extra.ino
Compile and upload a sketch using the last selected board and serial port
arduino --upload /path/to/sketch/sketch.ino
Compile and upload a sketch to an Arduino Nano, with an Atmega168 CPU, connected on port /dev/ttyACM0:
arduino --board arduino:avr:nano:cpu=atmega168 --port /dev/ttyACM0 --upload /path/to/sketch/sketch.ino
Compile a sketch, put the build results in the build directory an re-use any previous build results in that directory.
arduino --pref build.path=/path/to/sketch/build --verify /path/to/sketch/sketch.ino
Change the selected board and build path and do nothing else.
arduino --pref build.path=/path/to/sketch/build --board arduino:avr:uno --save-prefs
Install latest SAM board support
arduino --install-boards "arduino:sam"
Install AVR board support, 1.6.2
arduino --install-boards "arduino:avr:1.6.2"
Install Bridge library version 1.0.0
arduino --install-library "Bridge:1.0.0"
Install Bridge and Servo libraries
arduino --install-library "Bridge:1.0.0,Servo:1.2.0"
1.5.2 Added initial commandline support. This introduced --verify, --upload, --board, --port, --verbose and -v.
1.5.5 Added support for board-specific parameters to --board.
Sketch filenames are now interpreted relative to the current directory instead of the location of the arduino command itself.
1.5.6 Introduced --pref, --preferences-file, --verbose-build and --verbose-upload.
Preferences set through --pref are remembered, preferences set through --board, --port or the --verbose options are not.
When running with --verify or --upload, the full GUI is no longer shown. Error messages still use a graphical popup and on Windows, the splash screen is still shown.
1.5.8 Introduced --save-prefs.
1.6.2 Main executable in MacOS X changed from Arduino.app/Contents/MacOS/JavaApplicationStub to Arduino.app/Contents/MacOS/Arduino.
1.6.4 Introduced --install-boards and --install-library.
--pref options are now not saved to the preferences file, just like --board and --port, unless --save-prefs is specified.
A path passed to --preferences-file, or set in the build.path, preferences.path or settings.path is now interpreted relative to the current directory instead of the location of the arduino command itself.
Web site: http://www.arduino.cc/
Help on projects and programming: http://forum.arduino.cc/
Report bugs: http://github.com/arduino/Arduino/issues
IDE and framework development mailing list: https://groups.google.com/a/arduino.cc/forum/#!forum/developers
FCRACKZIP(1)                 General Commands Manual                FCRACKZIP(1)
fcrackzip - a Free/Fast Zip Password Cracker
fcrackzip [-bDBchVvplum2] [--brute-force] [--dictionary] [--benchmark] [--charset characterset] [--help] [--validate] [--verbose] [--init- password string/path] [--length min-max] [--use-unzip] [--method name] [--modulo r/m] file...
fcrackzip searches each zipfile given for encrypted files and tries to guess the password. All files must be encrypted with the same password, the more files you provide, the better.
OPTIONS -h, --help Prints the version number and (hopefully) some helpful insights.
-v, --verbose Each -v makes the program more verbose.
-b, --brute-force Select brute force mode. This tries all possible combinations of the letters you specify.
-D, --dictionary Select dictionary mode. In this mode, fcrackzip will read passwords from a file, which must contain one password per line and should be alphabetically sorted (e.g. using sort(1)).
-c, --charset characterset-specification Select the characters to use in brute-force cracking. Must be one of
a   include all lowercase characters [a-z] A   include all uppercase characters [A-Z] 1   include the digits [0-9] !   include [!:$%&/()=?{[]}+*~#] :   the following characters upto the end of the spe- cification string are included in the character set. This way you can include any character except binary null (at least under unix).
For example, a1:$% selects lowercase characters, digits and the dollar and percent signs.
-p, --init-password string Set initial (starting) password for brute-force searching to string, or use the file with the name string to supply passwords for dictionary searching.
-l, --length min[-max] Use an initial password of length min, and check all passwords upto passwords of length max (including). You can omit the max parameter.
-u, --use-unzip Try to decompress the first file by calling unzip with the guessed password. This weeds out false positives when not enough files have been given.
-m, --method name Use method number "name" instead of the default cracking method. The switch --help will print a list of available methods. Use --benchmark to see which method does perform best on your machine. The name can also be the number of the method to use.
-2, --modulo r/m Calculate only r/m of the password. Not yet supported.
-B, --benchmark Make a small benchmark, the output is nearly meaningless.
-V, --validate Make some basic checks wether the cracker works.
Have you ever mis-typed a password for unzip? Unzip reacted pretty fast with ´incorrect password´, without decrypting the whole file. While the encryption algorithm used by zip is relatively secure, PK made cracking easy by providing hooks for very fast password-checking, directly in the zip file. Understanding these is crucial to zip password cracking:
For each password that is tried, the first twelve bytes of the file are decrypted. Depending on the version of zip used to encrypt the file (more on that later), the first ten or eleven bytes are random, followed by one or two bytes whose values are stored elsewhere in the zip file, i.e. are known beforehand. If these last bytes don't have the correct (known) value, the password is definitely wrong. If the bytes are correct, the password might be correct, but the only method to find out is to unzip the file and compare the uncompressed length and crc´s.
Earlier versions of pkzip (1.xx) (and, incidentally, many zip clones for other operating systems!) stored two known bytes. Thus the error rate was roughly 1/2^16 = 0.01%. PKWARE ´improved´ (interesting what industry calls improved) the security of their format by only including one byte, so the possibility of false passwords is now raised to 0.4%. Unfortunately, there is no real way to distinguish one byte from two byte formats, so we have to be conservative.
By default, brute force starts at the given starting password, and successively tries all combinations until they are exhausted, printing all passwords that it detects, together with a rough correctness indicator.
The starting password given by the -p switch determines the length. fcrackzip will not currently increase the password length automatically, unless the -l switch is used.
This mode is similar to brute force mode, but instead of generating passwords using a given set of characters and a length, the passwords will be read from a file that you have to specify using the -p switch.
A CP mask is a method to obscure images or parts of images using a password.  These obscured images can be restored even when saved as JPEG files. In most of these files the password is actually hidden and can be decoded easily (using one of the many available viewer and masking programs, e.g. xv). If you convert the image the password, however, is lost. The cpmask crack method can be used to brute-force these images. Instead of a zip file you supply the obscured part (and nothing else) of the image in the PPM-Image Format (xv and other viewers can easily do this).
The cpmask method can only cope with password composed of uppercase letters, so be sure to supply the --charset A or equivalent option, together with a suitable initialization password.
fcrackzip -c a -p aaaaaa sample.zip checks the encrypted files in sample.zip for all lowercase 6 character passwords (aaaaaa ... abaaba ... ghfgrg ... zzzzzz).
fcrackzip --method cpmask --charset A --init AAAA test.ppm checks the obscured image test.ppm for all four character passwords.  -TP fcrackzip -D -p passwords.txt sample.zip check for every password listed in the file passwords.txt.
fzc, which seems to be widely used as a fast password cracker, claims to make 204570 checks per second on my machine (measured under plain dos w/o memory manager).
fcrackzip, being written in C and not in assembler, naturally is slower. Measured on a slightly loaded unix (same machine), it´s 12 percent slower (the compiler used was pgcc, from http://www.gcc.ml.org/).
To remedy this a bit, I converted small parts of the encryption core to x86 assembler (it will still compile on non x86 machines), and now it´s about 4-12 percent faster than fzc (again, the fcrackzip performance was measured under a multitasking os, so there are inevitably some meaurement errors), so there shouldn't be a tempting reason to switch to other programs.
Further improvements are definitely possible: fzc took 4 years to get into shape, while fcrackzip was hacked together in under 10 hours. And not to forget you have the source, while other programs (like fzc), even come as an encrypted .exe file (maybe because their programmers are afraid of other people could having a look at their lack of programming skills?  nobody knows...)
The reason I wrote fcrackzip was NOT to have the fastest zip cracker available, but to provide a portable, free (thus extensible), but still fast zip password cracker. I was really pissed of with that dumb, nonextendable zipcrackers that were either slow, were too limited, or wouldn't run in the background (say, under unix). (And you can't run them on your superfast 600Mhz Alpha).
No automatic unzip checking.
Stop/resume facility is missing.
Should be able to distinguish between files with 16 bit stored CRC´s and 8 bit stored CRC´s.
The benchmark does not work on all systems.
It's still early alpha.
Method "cpmask" only accepts ppms.
Could be faster.
fcrackzip was written by Marc Lehmann <pcg@goof.com>. The main fcrackzip page is at http://www.goof.com/pcg/marc/fcrackzip.html)
urxvt(1)                          RXVT-UNICODE                          urxvt(1)
rxvt-unicode (ouR XVT, unicode) - (a VT102 emulator for the X window system)
urxvt [options] [-e command [ args ]]
rxvt-unicode, version 9.26, is a colour vt102 terminal emulator intended as an xterm(1) replacement for users who do not require features such as Tektronix 4014 emulation and toolkit-style configurability. As a result, rxvt-unicode uses much less swap space -- a significant advantage on a machine serving many X sessions.
This document is also available on the World-Wide-Web at <http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.1.pod>.
See urxvt(7) (try "man 7 urxvt") for a list of frequently asked questions and answer to them and some common problems. That document is also accessible on the World-Wide-Web at <http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.pod>.
RXVT-UNICODE VS. RXVT Unlike the original rxvt, rxvt-unicode stores all text in Unicode internally. That means it can store and display most scripts in the world. Being a terminal emulator, however, some things are very difficult, especially cursive scripts such as arabic, vertically written scripts like mongolian or scripts requiring extremely complex combining rules, like tibetan or devanagari. Don't expect pretty output when using these scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work fine, though. A somewhat difficult case are right-to-left scripts, such as hebrew: rxvt-unicode adopts the view that bidirectional algorithms belong in the application, not the terminal emulator (too many things -- such as cursor-movement while editing -- break otherwise), but that might change.
If you are looking for a terminal that supports more exotic scripts, let me recommend "mlterm", which is a very user friendly, lean and clean terminal emulator. In fact, the reason rxvt-unicode was born was solely because the author couldn't get "mlterm" to use one font for latin1 and another for japanese.
Therefore another design rationale was the use of multiple fonts to display characters: The idea of a single unicode font which many other programs force onto its users never made sense to me: You should be able to choose any font for any script freely.
Apart from that, rxvt-unicode is also much better internationalised than its predecessor, supports things such as XFT and ISO 14755 that are handy in i18n-environments, is faster, and has a lot bugs less than the original rxvt. This all in addition to dozens of other small improvements.
It is still faithfully following the original rxvt idea of being lean and nice on resources: for example, you can still configure rxvt-unicode without most of its features to get a lean binary. It also comes with a client/daemon pair that lets you open any number of terminal windows from within a single process, which makes startup time very fast and drastically reduces memory usage. See urxvtd(1) (daemon) and urxvtc(1) (client).
It also makes technical information about escape sequences (which have been extended) more accessible: see urxvt(7) for technical reference documentation (escape sequences etc.).
The urxvt options (mostly a subset of xterm's) are listed below. In keeping with the smaller-is-better philosophy, options may be eliminated or default values chosen at compile-time, so options and defaults listed may not accurately reflect the version installed on your system. `urxvt -h' gives a list of major compile-time options on the Options line. Option descriptions may be prefixed with which compile option each is dependent upon. e.g. `Compile XIM:' requires XIM on the Options line. Note: `urxvt -help' gives a list of all command-line options compiled into your version.
Note that urxvt permits the resource name to be used as a long-option (--/++ option) so the potential command-line options are far greater than those listed. For example: `urxvt --loginShell --color1 Orange'.
-help, --help Print out a message describing available options.
-display displayname Attempt to open a window on the named X display (the older form -d is still respected. but deprecated). In the absence of this option, the display specified by the DISPLAY environment variable is used.
-depth bitdepth Compile frills: Attempt to find a visual with the given bit depth; resource depth.
[Please note that many X servers (and libXft) are buggy with respect to "-depth 32" and/or alpha channels, and will cause all sorts of graphical corruption. This is harmless, but we can't do anything about this, so watch out]
-visual visualID Compile frills: Use the given visual (see e.g. "xdpyinfo" for possible visual ids) instead of the default, and also allocate a private colormap. All visual types except for DirectColor are supported.
-geometry geom Window geometry (-g still respected); resource geometry.
-rv|+rv Turn on/off simulated reverse video; resource reverseVideo.
-j|+j Turn on/off jump scrolling (allow multiple lines per refresh); resource jumpScroll.
-ss|+ss Turn on/off skip scrolling (allow multiple screens per refresh); resource skipScroll.
-fade number Fade the text by the given percentage when focus is lost. Small values fade a little only, 100 completely replaces all colours by the fade colour; resource fading.
-fadecolor colour Fade to this colour when fading is used (see -fade). The default colour is opaque black. resource fadeColor.
-icon file Compile pixbuf: Use the specified image as application icon. This is used by many window managers, taskbars and pagers to represent the application window; resource iconFile.
-bg colour Window background colour; resource background.
-fg colour Window foreground colour; resource foreground.
-cr colour The cursor colour; resource cursorColor.
-pr colour The mouse pointer foreground colour; resource pointerColor.
-pr2 colour The mouse pointer background colour; resource pointerColor2.
-bd colour The colour of the border around the text area and between the scrollbar and the text; resource borderColor.
-fn fontlist Select the fonts to be used. This is a comma separated list of font names that are checked in order when trying to find glyphs for characters. The first font defines the cell size for characters; other fonts might be smaller, but not (in general) larger. A (hopefully) reasonable default font list is always appended to it. See resource font for more details.
In short, to specify an X11 core font, just specify its name or prefix it with "x:". To specify an XFT-font, you need to prefix it with "xft:", e.g.:
urxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15" urxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
See also the question "How does rxvt-unicode choose fonts?" in the FAQ section of urxvt(7).
-fb fontlist Compile font-styles: The bold font list to use when bold characters are to be printed. See resource boldFont for details.
-fi fontlist Compile font-styles: The italic font list to use when italic characters are to be printed. See resource italicFont for details.
-fbi fontlist Compile font-styles: The bold italic font list to use when bold italic characters are to be printed. See resource boldItalicFont for details.
-is|+is Compile font-styles: Bold/Blink font styles imply high intensity foreground/background (default). See resource intensityStyles for details.
-name name Specify the application name under which resources are to be obtained, rather than the default executable file name. Name should not contain `.' or `*' characters. Also sets the icon and title name.
-ls|+ls Start as a login-shell/sub-shell; resource loginShell.
-mc milliseconds Specify the maximum time between multi-click selections.
-ut|+ut Compile utmp: Inhibit/enable writing a utmp entry; resource utmpInhibit.
-vb|+vb Turn on/off visual bell on receipt of a bell character; resource visualBell.
-sb|+sb Turn on/off scrollbar; resource scrollBar.
-sr|+sr Put scrollbar on right/left; resource scrollBar_right.
-st|+st Display rxvt (non XTerm/NeXT) scrollbar without/with a trough; resource scrollBar_floating.
-si|+si Turn on/off scroll-to-bottom on TTY output inhibit; resource scrollTtyOutput has opposite effect.
-sk|+sk Turn on/off scroll-to-bottom on keypress; resource scrollTtyKeypress.
-sw|+sw Turn on/off scrolling with the scrollback buffer as new lines appear. This only takes effect if -si is also given; resource scrollWithBuffer.
-ptab|+ptab If enabled (default), "Horizontal Tab" characters are being stored as actual wide characters in the screen buffer, which makes it possible to select and paste them. Since a horizontal tab is a cursor movement and not an actual glyph, this can sometimes be visually annoying as the cursor on a tab character is displayed as a wide cursor; resource pastableTabs.
-bc|+bc Blink the cursor; resource cursorBlink.
-uc|+uc Make the cursor underlined; resource cursorUnderline.
-iconic Start iconified, if the window manager supports that option. Alternative form is -ic.
-sl number Save number lines in the scrollback buffer. See resource entry for limits; resource saveLines.
-b number Compile frills: Internal border of number pixels. See resource entry for limits; resource internalBorder.
-w number Compile frills: External border of number pixels. Also, -bw and -borderwidth. See resource entry for limits; resource externalBorder.
-bl Compile frills: Set MWM hints to request a borderless window, i.e. if honoured by the WM, the rxvt-unicode window will not have window decorations; resource borderLess. If the window manager does not support MWM hints (e.g. kwin), enables override-redirect mode.
-override-redirect Compile frills: Sets override-redirect on the window; resource override-redirect.
-dockapp Sets the initial state of the window to WithdrawnState, which makes window managers that support this extension treat it as a dockapp.
-sbg Compile frills: Disable the usage of the built-in block graphics/line drawing characters and just rely on what the specified fonts provide. Use this if you have a good font and want to use its block graphic glyphs; resource skipBuiltinGlyphs.
-lsp number Compile frills: Lines (pixel height) to insert between each row of the display. Useful to work around font rendering problems; resource lineSpace.
-letsp number Compile frills: Amount to adjust the computed character width by to control overall letter spacing. Negative values will tighten up the letter spacing, positive values will space letters out more. Useful to work around odd font metrics; resource letterSpace.
-tn termname This option specifies the name of the terminal type to be set in the TERM environment variable. This terminal type must exist in the termcap(5) database and should have li# and co# entries; resource termName.
-e command [arguments] Run the command with its command-line arguments in the urxvt window; also sets the window title and icon name to be the basename of the program being executed if neither -title (-T) nor -n are given on the command line. If this option is used, it must be the last on the command-line. If there is no -e option then the default is to run the program specified by the SHELL environment variable or, failing that, sh(1).
Please note that you must specify a program with arguments. If you want to run shell commands, you have to specify the shell, like this:
urxvt -e sh -c "shell commands"
-title text Window title (-T still respected); the default title is the basename of the program specified after the -e option, if any, otherwise the application name; resource title.
-n text Icon name; the default name is the basename of the program specified after the -e option, if any, otherwise the application name; resource iconName.
-C  Capture system console messages.
-pt style Compile XIM: input style for input method; OverTheSpot, OffTheSpot, Root; resource preeditType.
If the perl extension "xim-onthespot" is used (which is the default), then additionally the "OnTheSpot" preedit type is available.
-im text Compile XIM: input method name. resource inputMethod.
-imlocale string The locale to use for opening the IM. You can use an "LC_CTYPE" of e.g.  "de_DE.UTF-8" for normal text processing but "ja_JP.EUC-JP" for the input extension to be able to input japanese characters while staying in another locale. resource imLocale.
-imfont fontset Set the font set to use for the X Input Method, see resource imFont for more info.
-tcw Change the meaning of triple-click selection with the left mouse button. Only effective when the original (non-perl) selection code is in-use. Instead of selecting a full line it will extend the selection to the end of the logical line only. resource tripleclickwords.
-insecure Enable "insecure" mode, which currently enables most of the escape sequences that echo strings. See the resource insecure for more info.
-mod modifier Override detection of Meta modifier with specified key: alt, meta, hyper, super, mod1, mod2, mod3, mod4, mod5; resource modifier.
-ssc|+ssc Turn on/off secondary screen (default enabled); resource secondaryScreen.
-ssr|+ssr Turn on/off secondary screen scroll (default enabled); resource secondaryScroll.
-hold|+hold Turn on/off hold window after exit support. If enabled, urxvt will not immediately destroy its window when the program executed within it exits. Instead, it will wait till it is being killed or closed by the user; resource hold.
-cd path Sets the working directory for the shell (or the command specified via -e). The path must be an absolute path and it must exist for urxvt to start; resource chdir.
-xrm string Works like the X Toolkit option of the same name, by adding the string as if it were specified in a resource file. Resource values specified this way take precedence over all other resource specifications.
Note that you need to use the same syntax as in the .Xdefaults file, e.g. "*.background: black". Also note that all urxvt-specific options can be specified as long-options on the commandline, so use of -xrm is mostly limited to cases where you want to specify other resources (e.g. for input methods) or for compatibility with other programs.
-keysym.sym string Remap a key symbol. See resource keysym.
-embed windowid Tells urxvt to embed its windows into an already-existing window, which enables applications to easily embed a terminal.
Right now, urxvt will first unmap/map the specified window, so it shouldn't be a top-level window. urxvt will also reconfigure it quite a bit, so don't expect it to keep some specific state. It's best to create an extra subwindow for urxvt and leave it alone.
The window will not be destroyed when urxvt exits.
It might be useful to know that urxvt will not close file descriptors passed to it (except for stdin/out/err, of course), so you can use file descriptors to communicate with the programs within the terminal. This works regardless of whether the "-embed" option was used or not.
Here is a short Gtk2-perl snippet that illustrates how this option can be used (a longer example is in doc/embed):
my $rxvt = new Gtk2::Socket; $rxvt->signal_connect_after (realize => sub { my $xid = $_[0]->window->get_xid; system "urxvt -embed $xid &"; });
-pty-fd file descriptor Tells urxvt NOT to execute any commands or create a new pty/tty pair but instead use the given file descriptor as the tty master. This is useful if you want to drive urxvt as a generic terminal emulator without having to run a program within it.
If this switch is given, urxvt will not create any utmp/wtmp entries and will not tinker with pty/tty permissions - you have to do that yourself if you want that.
As an extremely special case, specifying "-1" will completely suppress pty/tty operations, which is probably only useful in conjunction with some perl extension that manages the terminal.
Here is a example in perl that illustrates how this option can be used (a longer example is in doc/pty-fd):
use IO::Pty; use Fcntl;
my $pty = new IO::Pty; fcntl $pty, F_SETFD, 0; # clear close-on-exec system "urxvt -pty-fd " . (fileno $pty) . "&"; close $pty;
# now communicate with rxvt my $slave = $pty->slave; while (<$slave>) { print $slave "got <$_>\n" }
-pe string Comma-separated list of perl extension scripts to use (or not to use) in this terminal instance. See resource perl-ext for details.
Note: `urxvt --help' gives a list of all resources (long options) compiled into your version. All resources are also available as long- options.
You can set and change the resources using X11 tools like xrdb. Many distribution do also load settings from the ~/.Xresources file when X starts. urxvt will consult the following files/resources in order, with later settings overwriting earlier ones:
1. app-defaults file in $XAPPLRESDIR 2. $HOME/.Xdefaults 3. RESOURCE_MANAGER property on root-window of screen 0 4. SCREEN_RESOURCES property on root-window of the current screen 5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename> 6. resources specified via -xrm on the commandline
Note that when reading X resources, urxvt recognizes two class names: Rxvt and URxvt. The class name Rxvt allows resources common to both urxvt and the original rxvt to be easily configured, while the class name URxvt allows resources unique to urxvt, to be shared between different urxvt configurations. If no resources are specified, suitable defaults will be used. Command-line arguments can be used to override resource settings. The following resources are supported (you might want to check the urxvtperl(3) manpage for additional settings by perl extensions not documented here):
depth: bitdepth Compile xft: Attempt to find a visual with the given bit depth; option -depth.
buffered: boolean Compile xft: Turn on/off double-buffering for xft (default enabled). On some card/driver combination enabling it slightly decreases performance, on most it greatly helps it. The slowdown is small, so it should normally be enabled.
geometry: geom Create the window with the specified X window geometry [default 80x24]; option -geometry.
background: colour Use the specified colour as the window's background colour [default White]; option -bg.
foreground: colour Use the specified colour as the window's foreground colour [default Black]; option -fg.
colorn: colour Use the specified colour for the colour value n, where 0-7 corresponds to low-intensity (normal) colours and 8-15 corresponds to high-intensity (bold = bright foreground, blink = bright background) colours. The canonical names are as follows: 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour names used are listed in the COLOURS AND GRAPHICS section.
Colours higher than 15 cannot be set using resources (yet), but can be changed using an escape command (see urxvt(7)).
Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with 88 colour support). Colours 80-87 are evenly spaces grey steps.
colorBD: colour colorIT: colour Use the specified colour to display bold or italic characters when the foreground colour is the default. If font styles are not available (Compile styles) and this option is unset, reverse video is used instead.
colorUL: colour Use the specified colour to display underlined characters when the foreground colour is the default.
underlineColor: colour If set, use the specified colour as the colour for the underline itself. If unset, use the foreground colour.
highlightColor: colour If set, use the specified colour as the background for highlighted characters. If unset, use reverse video.
highlightTextColor: colour If set and highlightColor is set, use the specified colour as the foreground for highlighted characters.
cursorColor: colour Use the specified colour for the cursor. The default is to use the foreground colour; option -cr.
cursorColor2: colour Use the specified colour for the colour of the cursor text. For this to take effect, cursorColor must also be specified. The default is to use the background colour.
reverseVideo: boolean True: simulate reverse video by foreground and background colours; option -rv. False: regular screen colours [default]; option +rv. See note in COLOURS AND GRAPHICS section.
jumpScroll: boolean True: specify that jump scrolling should be used. When receiving lots of lines, urxvt will only scroll once a whole screen height of lines has been read, resulting in fewer updates while still displaying every received line; option -j.
False: specify that smooth scrolling should be used. urxvt will force a screen refresh on each new line it received; option +j.
skipScroll: boolean True: (the default) specify that skip scrolling should be used. When receiving lots of lines, urxvt will only scroll once in a while (around 60 times per second), resulting in far fewer updates. This can result in urxvt not ever displaying some of the lines it receives; option -ss.
False: specify that everything is to be displayed, even if the refresh is too fast for the human eye to read anything (or the monitor to display anything); option +ss.
fading: number Fade the text by the given percentage when focus is lost; option -fade.
fadeColor: colour Fade to this colour, when fading is used (see fading:). The default colour is black; option -fadecolor.
iconFile: file Set the application icon pixmap; option -icon.
scrollColor: colour Use the specified colour for the scrollbar [default #B2B2B2].
troughColor: colour Use the specified colour for the scrollbar's trough area [default #969696]. Only relevant for rxvt (non XTerm/NeXT) scrollbar.
borderColor: colour The colour of the border around the text area and between the scrollbar and the text.
font: fontlist Select the fonts to be used. This is a comma separated list of font names that are checked in order when trying to find glyphs for characters. The first font defines the cell size for characters; other fonts might be smaller, but not (in general) larger. A (hopefully) reasonable default font list is always appended to it; option -fn.
Each font can either be a standard X11 core font (XLFD) name, with optional prefix "x:" or a Xft font (Compile xft), prefixed with "xft:".
In addition, each font can be prefixed with additional hints and specifications enclosed in square brackets ("[]"). The only available hint currently is "codeset=codeset-name", and this is only used for Xft fonts.
For example, this font resource
URxvt.font: 9x15bold,\ -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ [codeset=JISX0208]xft:Kochi Gothic:antialias=false, \ xft:Code2000:antialias=false
specifies five fonts to be used. The first one is "9x15bold" (actually the iso8859-1 version of the second font), which is the base font (because it is named first) and thus defines the character cell grid to be 9 pixels wide and 15 pixels high.
The second font is just used to add additional unicode characters not in the base font, likewise the third, which is unfortunately non- bold, but the bold version of the font does contain fewer characters, so this is a useful supplement.
The third font is an Xft font with aliasing turned off, and the characters are limited to the JIS 0208 codeset (i.e. japanese kanji). The font contains other characters, but we are not interested in them.
The last font is a useful catch-all font that supplies most of the remaining unicode characters.
boldFont: fontlist italicFont: fontlist boldItalicFont: fontlist The font list to use for displaying bold, italic or bold italic characters, respectively.
If specified and non-empty, then the syntax is the same as for the font-resource, and the given font list will be used as is, which makes it possible to substitute completely different font styles for bold and italic.
If unset (the default), a suitable font list will be synthesized by "morphing" the normal text font list into the desired shape. If that is not possible, replacement fonts of the desired shape will be tried.
If set, but empty, then this specific style is disabled and the normal text font will being used for the given style.
intensityStyles: boolean When font styles are not enabled, or this option is enabled (True, option -is, the default), bold/blink font styles imply high intensity foreground/background colours. Disabling this option (False, option +is) disables this behaviour, the high intensity colours are not reachable.
title: string Set window title string, the default title is the command-line specified after the -e option, if any, otherwise the application name; option -title.
iconName: string Set the name used to label the window's icon or displayed in an icon manager window, it also sets the window's title unless it is explicitly set; option -n.
mapAlert: boolean True: de-iconify (map) on receipt of a bell character. False: no de- iconify (map) on receipt of a bell character [default].
urgentOnBell: boolean True: set the urgency hint for the wm on receipt of a bell character. False: do not set the urgency hint [default].
urxvt resets the urgency hint on every focus change.
visualBell: boolean True: use visual bell on receipt of a bell character; option -vb. False: no visual bell [default]; option +vb.
loginShell: boolean True: start as a login shell by prepending a `-' to argv[0] of the shell; option -ls. False: start as a normal sub-shell [default]; option +ls.
multiClickTime: number Specify the maximum time in milliseconds between multi-click select events. The default is 500 milliseconds; option -mc.
utmpInhibit: boolean True: inhibit writing record into the system log file utmp; option -ut. False: write record into the system log file utmp [default]; option +ut.
print-pipe: string Specify a command pipe for vt100 printer [default lpr(1)]. Use Print to initiate a screen dump to the printer and Ctrl-Print or Shift- Print to include the scrollback as well.
The string will be interpreted as if typed into the shell as-is.
URxvt.print-pipe: cat > $(TMPDIR=$HOME mktemp urxvt.XXXXXX)
This creates a new file in your home directory with the screen contents every time you hit "Print".
scrollstyle: mode Set scrollbar style to rxvt, plain, next or xterm. plain is the author's favourite.
thickness: number Set the scrollbar width in pixels.
scrollBar: boolean True: enable the scrollbar [default]; option -sb. False: disable the scrollbar; option +sb.
scrollBar_right: boolean True: place the scrollbar on the right of the window; option -sr. False: place the scrollbar on the left of the window; option +sr.
scrollBar_floating: boolean True: display an rxvt scrollbar without a trough; option -st.  False: display an rxvt scrollbar with a trough; option +st.
scrollBar_align: mode Align the top, bottom or centre [default] of the scrollbar thumb with the pointer on middle button press/drag.
scrollTtyOutput: boolean True: scroll to bottom when tty receives output; option -si.  False: do not scroll to bottom when tty receives output; option +si.
scrollWithBuffer: boolean True: scroll with scrollback buffer when tty receives new lines (i.e. try to show the same lines) and scrollTtyOutput is False; option -sw. False: do not scroll with scrollback buffer when tty receives new lines; option +sw.
scrollTtyKeypress: boolean True: scroll to bottom when a non-special key is pressed. Special keys are those which are intercepted by rxvt-unicode for special handling and are not passed onto the shell; option -sk. False: do not scroll to bottom when a non-special key is pressed; option +sk.
saveLines: number Save number lines in the scrollback buffer [default 1000]; option -sl.
internalBorder: number Internal border of number pixels. This resource is limited to 100; option -b.
externalBorder: number External border of number pixels. This resource is limited to 100; option -w, -bw, -borderwidth.
borderLess: boolean Set MWM hints to request a borderless window, i.e. if honoured by the WM, the rxvt-unicode window will not have window decorations; option -bl.
skipBuiltinGlyphs: boolean Compile frills: Disable the usage of the built-in block graphics/line drawing characters and just rely on what the specified fonts provide. Use this if you have a good font and want to use its block graphic glyphs; option -sbg.
termName: termname Specifies the terminal type name to be set in the TERM environment variable; option -tn.
lineSpace: number Specifies number of lines (pixel height) to insert between each row of the display [default 0]; option -lsp.
meta8: boolean True: handle Meta (Alt) + keypress to set the 8th bit. False: handle Meta (Alt) + keypress as an escape prefix [default].
mouseWheelScrollPage: boolean True: the mouse wheel scrolls a page full. False: the mouse wheel scrolls five lines [default].
pastableTabs: boolean True: store tabs as wide characters. False: interpret tabs as cursor movement only; option "-ptab".
cursorBlink: boolean True: blink the cursor. False: do not blink the cursor [default]; option -bc.
cursorUnderline: boolean True: Make the cursor underlined. False: Make the cursor a box [default]; option -uc.
pointerBlank: boolean True: blank the pointer when a key is pressed or after a set number of seconds of inactivity. False: the pointer is always visible [default].
pointerColor: colour Mouse pointer foreground colour.
pointerColor2: colour Mouse pointer background colour.
pointerShape: string Compile frills: Specifies the name of the mouse pointer shape [default xterm]. See the macros in the X11/cursorfont.h include file for possible values (omit the "XC_" prefix).
pointerBlankDelay: number Specifies number of seconds before blanking the pointer [default 2]. Use a large number (e.g. 987654321) to effectively disable the timeout.
backspacekey: string The string to send when the backspace key is pressed. If set to DEC or unset it will send Delete (code 127) or, with control, Backspace (code 8) - which can be reversed with the appropriate DEC private mode escape sequence.
deletekey: string The string to send when the delete key (not the keypad delete key) is pressed. If unset it will send the sequence traditionally associated with the Execute key.
cutchars: string The characters used as delimiters for double-click word selection (whitespace delimiting is added automatically if resource is given).
When the perl selection extension is in use (the default if compiled in, see the urxvtperl(3) manpage), a suitable regex using these characters will be created (if the resource exists, otherwise, no regex will be created). In this mode, characters outside ISO-8859-1 can be used.
When the selection extension is not used, only ISO-8859-1 characters can be used. If not specified, the built-in default is used:
BACKSLASH `"'&()*,;<=>?@[]^{|}
preeditType: style OnTheSpot, OverTheSpot, OffTheSpot, Root; option -pt.
inputMethod: name name of inputMethod to use; option -im.