neulab/tldr huggingface dataset:
• check if the application data path passed in does not exist or is read-only, and fallback to a temporary directory,
• temporary directory application data is automatically cleaned up at the end of execution,
• symlink-app-data is always False when the application data is temporary
by @gaborbernat. (#1640)
• Fix PyPy 2 builtin modules are imported from standard library, rather than from builtin  - by @gaborbernat. (#1652)
• Fix creation of entry points when path contains spaces - by @nsoranzo. (#1660)
• Fix relative paths for the zipapp (for python 3.7+) - by @gaborbernat. (#1666)
v20.0.5 (2020-02-21) Features - 20.0.5 • Also create pythonX.X executables when creating pypy virtualenvs - by @asottile (#1612)
• Fail with better error message if trying to install source with unsupported setuptools, allow setuptools-scm >= 2 and move to legacy setuptools-scm format to support better older platforms (CentOS 7 and such) - by @gaborbernat. (#1621)
• Report of the created virtual environment is now split across four short lines rather than one long - by @gaborbernat (#1641)
Bugfixes - 20.0.5 • Add macOs Python 2 Framework support (now we test it with the CI via brew) - by @gaborbernat (#1561)
• Fix losing of libpypy-c.so when the pypy executable is a symlink - by @asottile (#1614)
• Discover python interpreter in a case insensitive manner - by @PrajwalM2212 (#1624)
• Fix cross interpreter support when the host python sets sys.base_executable based on __PYVENV_LAUNCHER__ - by @cjolowicz (‐ #1643)
v20.0.4 (2020-02-14) Features - 20.0.4 • When aliasing interpreters, use relative symlinks - by @asottile. (‐ #1596)
Bugfixes - 20.0.4 • Allow the use of / as pathname component separator on Windows - by vphilippon (#1582)
• Lower minimal version of six required to 1.9 - by ssbarnea (#1606)
v20.0.3 (2020-02-12) Bugfixes - 20.0.3 • On Python 2 with Apple Framework builds the global site package is no longer added when the system-site-packages is not specified - by @gaborbernat. (#1561)
• Fix system python discovery mechanism when prefixes contain relative parts (e.g. ..) by resolving paths within the python information query - by @gaborbernat. (#1583)
• Expose a programmatic API as from virtualenv import cli_run - by @gaborbernat. (#1585)
• Fix app-data seeder injects a extra .dist-info.virtualenv path that breaks importlib.metadata, now we inject an extra .virtualenv - by @gaborbernat. (#1589)
Improved Documentation - 20.0.3 • Document a programmatic API as from virtualenv import cli_run under programmatic_api - by @gaborbernat. (#1585)
v20.0.2 (2020-02-11) Features - 20.0.2 • Print out a one line message about the created virtual environment when no verbose is set, this can now be silenced to get back the original behaviour via the quiet flag - by @pradyunsg. (#1557)
• Allow virtualenv's app data cache to be overridden by VIRTUALENV_OVERRIDE_APP_DATA - by @asottile. (#1559)
• Passing in the virtual environment name/path is now required (no longer defaults to venv) - by @gaborbernat. (#1568)
• Add a CLI flag with-traceback that allows displaying the stacktrace of the virtualenv when a failure occurs - by @gaborbernat. (#1572)
Bugfixes - 20.0.2 • Support long path names for generated virtual environment console entry points (such as pip) when using the app-data seeder - by @gaborbernat. (#997)
• Improve python discovery mechanism:
• do not fail if there are executables that fail to query (e.g. for not having execute access to it) on the PATH,
• beside the prefix folder also try with the platform dependent binary folder within that,
by @gaborbernat. (#1545)
• When copying (either files or trees) do not copy the permission bits, last access time, last modification time, and flags as access to these might be forbidden (for example in case of the macOs Framework Python) and these are not needed for the user to use the virtual environment - by @gaborbernat. (#1561)
• While discovering a python executables interpreters that cannot be queried are now displayed with info level rather than warning, so now they're no longer shown by default (these can be just executables to which we don't have access or that are broken, don't warn if it's not the target Python we want) - by @gaborbernat. (#1574)
• The app-data seeder no longer symlinks the packages on UNIX and copies on Windows. Instead by default always copies, however now has the symlink-app-data flag allowing users to request this less robust but faster method - by @gaborbernat. (#1575)
Improved Documentation - 20.0.2 • Add link to the legacy documentation for the changelog by @jezdez. (‐ #1547)
• Fine tune the documentation layout: default width of theme, allow tables to wrap around, soft corners for code snippets - by @pradyunsg. (#1548)
v20.0.1 (2020-02-10) Features - 20.0.1 • upgrade embedded setuptools to 45.2.0 from 45.1.0 for Python 3.4+ - by @gaborbernat. (#1554)
Bugfixes - 20.0.1 • Virtual environments created via relative path on Windows creates bad console executables - by @gaborbernat. (#1552)
• Seems sometimes venvs created set their base executable to themselves; we accept these without question, so we handle virtual environments as system pythons causing issues - by @gaborbernat. (#1553)
v20.0.0. (2020-02-10) Improved Documentation - 20.0.0. • Fixes typos, repeated words and inconsistent heading spacing. Rephrase parts of the development documentation and CLI documentation. Expands shorthands like env var and config to their full forms. Uses descriptions from respective documentation, for projects listed in related links - by @pradyunsg. (#1540)
v20.0.0b2 (2020-02-04) Features - 20.0.0b2 • Improve base executable discovery mechanism:
• print at debug level why we refuse some candidates,
• when no candidates match exactly, instead of hard failing fallback to the closest match where the priority of matching attributes is: python implementation, major version, minor version, architecture, patch version, release level and serial (this is to facilitate things to still work when the OS upgrade replace/upgrades the system python with a never version, than what the virtualenv host python was created with),
• always resolve system_executable information during the interpreter discovery, and the discovered environment is the system interpreter instead of the venv/virtualenv (this happened before lazily the first time we accessed, and caused reporting that the created virtual environment is of type of the virtualenv host python version, instead of the system pythons version - these two can differ if the OS upgraded the system python underneath and the virtualenv host was created via copy),
by @gaborbernat. (#1515)
• Generate bash and fish activators on Windows too (as these can be available with git bash, cygwin or mysys2) - by @gaborbernat. (#1527)
• Upgrade the bundled wheel package from 0.34.0 to 0.34.2 - by @gaborbernat. (#1531)
Bugfixes - 20.0.0b2 • Bash activation script should have no extensions instead of .sh (this fixes the virtualenvwrapper integration) - by @gaborbernat. (#1508)
• Show less information when we run with a single verbosity (-v):
• no longer shows accepted interpreters information (as the last proposed one is always the accepted one),
• do not display the str_spec attribute for PythonSpec as these can be deduced from the other attributes,
• for the app-data seeder do not show the type of lock, only the path to the app data directory,
By @gaborbernat. (#1510)
• Fixed cannot discover a python interpreter that has already been discovered under a different path (such is the case when we have multiple symlinks to the same interpreter) - by @gaborbernat. (#1512)
• Support relative paths for -p - by @gaborbernat. (#1514)
• Creating virtual environments in parallel fail with cannot acquire lock within app data - by @gaborbernat. (#1516)
• pth files were not processed under Debian CPython2 interpreters - by @gaborbernat. (#1517)
• Fix prompt not displayed correctly with upcoming fish 3.10 due to us not preserving $pipestatus - by @krobelus. (#1530)
• Stable order within pyenv.cfg and add include-system-site-packages only for creators that reference a global Python - by user:gaborbernat. (‐ #1535)
Improved Documentation - 20.0.0b2 • Create the first iteration of the new documentation - by @gaborbernat. (#1465)
• Project readme is now of type MarkDown instead of reStructuredText - by @gaborbernat. (#1531)
v20.0.0b1 (2020-01-28) • First public release of the rewrite. Everything is brand new and just added.
• --download defaults to False
WARNING: The current virtualenv is the second iteration of implementation. From version 0.8 all the way to 16.7.9 we numbered the first iteration. Version 20.0.0b1 is a complete rewrite of the package, and as such this release history starts from there. The old changelog is still available in the legacy branch documentation.
2007-2021, PyPA, PyPA
IPCRM(1)                          User Commands                         IPCRM(1)
ipcrm - remove certain IPC resources
ipcrm [options]
ipcrm [shm|msg|sem] ID ...
ipcrm removes System V inter-process communication (IPC) objects and associated data structures from the system. In order to delete such objects, you must be superuser, or the creator or owner of the object.
System V IPC objects are of three types: shared memory, message queues, and semaphores. Deletion of a message queue or semaphore object is immediate (regardless of whether any process still holds an IPC identifier for the object). A shared memory object is only removed after all currently attached processes have detached (shmdt(2)) the object from their virtual address space.
Two syntax styles are supported. The old Linux historical syntax specifies a three-letter keyword indicating which class of object is to be deleted, followed by one or more IPC identifiers for objects of this type.
The SUS-compliant syntax allows the specification of zero or more objects of all three types in a single command line, with objects specified either by key or by identifier (see below). Both keys and identifiers may be specified in decimal, hexadecimal (specified with an initial '0x' or '0X'), or octal (specified with an initial '0').
The details of the removes are described in shmctl(2), msgctl(2), and semctl(2). The identifiers and keys can be found by using ipcs(1).
-a, --all [shm] [msg] [sem] Remove all resources. When an option argument is provided, the removal is performed only for the specified resource types.
Warning! Do not use -a if you are unsure how the software using the resources might react to missing objects. Some programs create these resources at startup and may not have any code to deal with an unexpected disappearance.
-M, --shmem-key shmkey Remove the shared memory segment created with shmkey after the last detach is performed.
-m, --shmem-id shmid Remove the shared memory segment identified by shmid after the last detach is performed.
-Q, --queue-key msgkey Remove the message queue created with msgkey.
-q, --queue-id msgid Remove the message queue identified by msgid.
-S, --semaphore-key semkey Remove the semaphore created with semkey.
-s, --semaphore-id semid Remove the semaphore identified by semid.
In its first Linux implementation, ipcrm used the deprecated syntax shown in the second line of the SYNOPSIS. Functionality present in other *nix implementations of ipcrm has since been added, namely the ability to delete resources by key (not just identifier), and to respect the same command-line syntax. For backward compatibility the previous syntax is still supported.
ipcmk(1), ipcs(1), msgctl(2), msgget(2), semctl(2), semget(2), shmctl(2), shmdt(2), shmget(2), ftok(3), sysvipc(7)
The ipcrm command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
add-apt-repository(1)        General Commands Manual       add-apt-repository(1)
add-apt-repository - Adds a repository into the /etc/apt/sources.list or /etc/apt/sources.list.d or removes an existing one
add-apt-repository [OPTIONS] REPOSITORY
add-apt-repository is a script which adds an external APT repository to either /etc/apt/sources.list or a file in /etc/apt/sources.list.d/ or removes an already existing repository.
The options supported by add-apt-repository are:
-h, --help Show help message and exit
-m, --massive-debug Print a lot of debug information to the command line
-r, --remove Remove the specified repository
-y, --yes Assume yes to all queries
-k, --keyserver Use a custom keyserver URL instead of the default
-s, --enable-source Allow downloading of the source packages from the repository
REPOSITORY can be either a line that can be added directly to sources.list(5), in the form ppa:<user>/<ppa-name> for adding Personal Package Archives, or a distribution component to enable.
In the first form, REPOSITORY will just be appended to /etc/apt/sources.list.
In the second form, ppa:<user>/<ppa-name> will be expanded to the full deb line of the PPA and added into a new file in the /etc/apt/sources.list.d/ directory.  The GPG public key of the newly added PPA will also be downloaded and added to apt's keyring.
In the third form, the given distribution component will be enabled for all sources.
sources.list(5)
This manual page was written by Chow Loong Jin <hyperair@gmail.com> for the Debian system (but 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 2 or 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.
KWRITE(1)                    General Commands Manual                   KWRITE(1)
kwrite - KDE text editor
kwrite [options][file]
This manual page documents briefly the kwrite command.  This manual page was written for the Debian distribution because the original program does not have a manual page.
kwrite is a text editor for KDE, that is a light version of kate.  It allows syntax coloration for many langages.
It is able to expand or collapse parts of code (C functions, ...).
--help-qt Show QT specific help (common for all QT apps).
--help-kde Show KDE specific help (common for all KDE apps).
--help-all Show the complete help.
--author Show program author(s).
--license Show program license.
-v, --version Show version of program.
file is the file to open
kate(1)
For more details, you should have a look at the KDE Help center, available from the K menu.
This manual page was written by Clement Stenac <zorglub@via.ecp.fr>, for the Debian GNU/Linux project (but may be used by others).
kwrite was written by the KDE project
INTERDIFF(1)                        Man pages                       INTERDIFF(1)
interdiff - show differences between two diff files
interdiff [[-p n] | [--strip-match=n]] [[-U n] | [--unified=n]] [[-d PAT] | [--drop-context=PAT]] [[-q] | [--quiet]] [[-z] | [--decompress]] [[-b] | [--ignore-space-change]] [[-B] | [--ignore-blank-lines]] [[-i] | [--ignore-case]] [[-w] | [--ignore-all-space]] [[--interpolate] | [--combine] | [--flip]] [--no-revert-omitted] diff1 diff2
interdiff {[--help] | [--version]}
interdiff creates a unified format diff that expresses the difference between two diffs. The diffs must both be relative to the same files. For best results, the diffs must have at least three lines of context.
To reverse a patch, use /dev/null for diff2.
To reduce the amount of context in a patch, use:
interdiff -U1 /dev/null patchfile
Since interdiff doesn't have the advantage of being able to look at the files that are to be modified, it has stricter requirements on the input format than patch(1) does. The output of GNU diff will be okay, even with extensions, but if you intend to use a hand-edited patch it might be wise to clean up the offsets and counts using recountdiff(1) first.
Note, however, that the two patches must both be relative to the versions of the same original set of files.
The diffs may be in context format. The output, however, will be in unified format.
-h Ignored, for compatibility with older versions of interdiff. This option will go away soon.
-p n, --strip-match=n When comparing filenames, ignore the first n pathname components from both patches. (This is similar to the -p option to GNU patch(1).)
-q, --quiet Quieter output. Don't emit rationale lines at the beginning of each patch.
-U n, --unified=n Attempt to display n lines of context (requires at least n lines of context in both input files). (This is similar to the -U option to GNU diff(1).)
-d PATTERN, --drop-context=PATTERN Don't display any context on files that match the shell wildcard PATTERN. This option can be given multiple times.
Note that the interpretation of the shell wildcard pattern does not count slash characters or periods as special (in other words, no flags are given to fnmatch). This is so that “*/basename”-type patterns can be given without limiting the number of pathname components.
-i, --ignore-case Consider upper- and lower-case to be the same.
-w, --ignore-all-space Ignore whitespace changes in patches.
-b, --ignore-space-change Ignore changes in the amount of whitespace.
-B, --ignore-blank-lines Ignore changes whose lines are all blank.
-z, --decompress Decompress files with extensions .gz and .bz2.
--interpolate Run as “interdiff”. This is the default.
--combine Run as “combinediff”. See combinediff(1) for more information about how the behaviour is altered in this mode.
--no-revert-omitted (For interpolation mode only) When a file is changed by the first patch but not by the second, don't revert that change.
--help Display a short usage message.
--version Display the version number of interdiff.
Basic usage:
interdiff -z 3.2pre1.patch.gz 3.2pre2.patch.gz
Reversing a patch:
interdiff patch /dev/null
Reversing part of a patch (and ignoring the rest):
filterdiff -i file.c patchfile | \ interdiff /dev/stdin /dev/null
There are currently no known bugs in interdiff; but there are some caveats. If you find a bug, please report it (along with a minimal test case) to Tim Waugh <twaugh@redhat.com>.
There are some sets of patches in which there is just not enough information to produce a proper interdiff. In this case, the strategy employed is to revert the original patch and apply the new patch. This, unfortunately, means that interdiffs are not guaranteed to be reversible.
combinediff(1)
Tim Waugh <twaugh@redhat.com> Package maintainer
Michael K. Johnson <johnsonm@redhat.com> Original man page contributor
highlight(1)                   user documentation                   highlight(1)
Highlight - a universal sourcecode to formatted text converter
highlight [OPTIONS]... [FILES]...
Highlight converts sourcecode to HTML, XHTML, RTF, ODT, LaTeX, TeX, BBCode, Pango markup, SVG, XTERM or ANSI escape sequences.  There are several colour themes available.  Highlight recognizes keywords, numbers, strings, comments, symbols and preprocessor directives.  It supports about 180 programming languages, which are defined in Lua scripts.
It's easily possible to enhance highlight's database of programming languages and colour themes.  See the README file for details.
-B, --batch-recursive=<wildcard> convert all files matching the wildcard (uses recursive search)
-D, --data-dir=<path> set path to highlight data directory
--config-file=<file> set path to a lang or theme file
-h, --help[=topic] print this help or a topic description <topic> = [syntax, theme, plugin, config]
-i, --input=<file> name of input file
-o, --output=<file> name of output file
-d, --outdir=<output directory> name of output directory
-P, --progress print progress bar in batch mode
-S, --syntax=<type|path> set type of source code, necessary if input file suffix is missing. The syntax may also be defined as path of the language file.
--syntax-by-name=<name> specify type of source code by given name.  Will not read a file of this name, useful for stdin and to determine the syntax of the file before piping its content to highlight. This option overrides --syntax.
--syntax-supported test if the given syntax can be loaded and print the result (assumes -S or --syntax-by-name)
-v, --verbose print debug info to stderr; repeat to show more information
-q, --quiet suppress progress info in batch mode
--force[=syntax] generate output if input syntax is unknown. The fallback syntax may be set here, Plain Text is default.
--list-scripts=<type> list installed scripts <type> = [langs, themes, plugins]
--list-cat=<categories> filter the scripts by the given categories (example: --list- cat='source;script')
--max-size=<size> set maximum input file size (examples: 512M, 1G; default: 256M)
--plug-in=<script> execute Lua plug-in script; repeat option to apply multiple plug- ins
--plug-in-param set plug-in input parameter. This might be an input file name (ie. 'tags').
--print-config print path configuration
--print-style print stylesheet only (see --style-outfile)
--skip=<list> ignore listed unknown file types (example: --skip='bak;c~;h~')
--stdout output to stdout (batch mode, --print-style)
--validate-input test if input is a valid text file
--version print version and copyright info
-O, --out-format=<format> output file in given format <format>=[html, xhtml, latex, tex, rtf, odt, ansi, xterm256, truecolor, bbcode, pango, svg]
-c, --style-outfile=<file> name of style definition file
-T, --doc-title document title
-e, --style-infile=<file> name of file to be included in style-outfile
-f, --fragment omit header and footer of the output document (see --keep- injections)
-F, --reformat=<style> reformat output in given style.  <style>=[allman, gnu, google, horstmann, java, kr, linux, lisp, mozilla, otbs, pico, vtk, ratliff, stroustrup, webkit, whitesmith]
-I, --include-style include style definition in output
-J, --line-length=<num> line length before wrapping (see -V, -W)
-j, --line-number-length=<num> line number length incl. left padding. Default length: 5
-k, --font=<font> set font (specific to output format)
-K, --font-size=<num?> set font size (specific to output format)
-l, --line-numbers print line numbers in output file
-m, --line-number-start=<cnt> start line numbering with cnt (assumes -l)
--line-range=<start-end> output only lines from number <start> to <end>
-s, --style=<style name|path> set highlighting style (theme). Add 'base16/' prefix to use a Base16 theme. The theme may also be defined as path of the theme file.
-t  --replace-tabs=<num> replace tabs by num spaces
-u, --encoding=<enc> set output encoding which matches input file encoding; omit encoding information if set to "NONE"
-V, --wrap-simple wrap lines after 80 (default) characters without indenting function parameters and statements.
-W, --wrap wrap lines after 80 (default) characters (use with caution).
-z, --zeroes fill leading space of line numbers with zeroes
--isolate output each syntax token in separate tags (verbose output)
--keep-injections output plug-in header and footer injections in spite of -f
--kw-case=<upper|lower|capitalize> output all keywords in given case if language is not case sensitive
--no-trailing-nl[=mode] omit trailing newline. If mode is "empty-file", omit only for empty input
--no-version-info omit version info comment
--wrap-no-numbers omit line numbers of wrapped lines (assumes -l)
(X)HTML OPTIONS -a, --anchors attach anchors to line numbers (HTML only)
-y, --anchor-prefix=<str> set anchor name prefix
-N, --anchor-filename use input file name as anchor name
-C, --print-index print index file with links to all output files
-n, --ordered-list print lines as ordered list items
--class-name=<str> set CSS class name prefix; omit class name if set to "NONE"
--inline-css output CSS within each tag (verbose output)
--enclose-pre enclose fragmented output with pre tag (assumes -f)
-b, --babel disable Babel package shorthands
-r, --replace-quotes replace double quotes by \dq
--beamer adapt output for the Beamer package
--pretty-symbols improve appearance of brackets and other symbols
--page-color include page color attributes
-x, --page-size=<size> set page size, <size>=[a3, a4, a5, b4, b5, b6, letter]
--char-styles include character stylesheets
--height=<h> set image height (units allowed)
--width=<w> set image size (see --height)
TERMINAL ESCAPE OUTPUT OPTIONS (XTERM256 OR TRUECOLOR) --canvas[=width] set background colour padding (default: 80)
--ls-profile=<server> load LSP configuration from lsp.conf
--ls-delay=<ms> set server initialization delay in milliseconds
--ls-exec=<bin> set server executable name
--ls-option=<option> set server CLI option (can be repeated)
--ls-hover execute hover requests (HTML output only)
--ls-semantic query server for semantic token types (requires LSP 3.16)
--ls-syntax=<lang> set syntax which is understood by the server
--ls-syntax-error retrieve syntax error information (assumes --ls-hover or --ls- semantic)
--ls-workspace=<dir> set workspace directory to initialize the server
Highlight recognizes these variables:
HIGHLIGHT_DATADIR sets the path to highlight's configuration scripts
HIGHLIGHT_OPTIONS may contain command line options, but no input file paths.
If no in- or output files are specified, stdin and stdout will be used for in- or output.  Reading from stdin can also be triggered by the '-' option.
Default output format: xterm256 or truecolor if appropriate, HTML otherwise.
Style definitions are stored in highlight.css (HTML, XHTML, SVG) or highlight.sty (LaTeX, TeX) if neither -c nor -I is given. For CSS, definitions are stored in the output document header with -I, if -f is also given there will be no style definitions.
Reformatting code (-F) will only work with C, C++, C# and Java input files.
LSP features require absolute input paths and disable reformatting (-F).
Wrapping lines with -V or -W will cause faulty highlighting of long single line comments and directives.  Using line-range might interfere with multi line syntax elements. Use with caution.
The configuration files are stored in /usr/share/highlight/.  Language definitions, themes and plugins are located in subdirectories.
Documentation files are stored in /usr/share/doc/highlight/ , configuration files in /etc/highlight/.
See README how to install own scripts in the home directory.
Single file conversion:
highlight -o hello.html -i hello.c
highlight -o hello.html hello.c
highlight -o hello.html -S c < hello.c
highlight -S c < hello.c > hello.html
Note that a file highlight.css is created in the current directory.
Batch file processing:
highlight --out-format=xhtml  -B '*.cpp' -d /home/you/html_code/
converts all *.cpp files in the current directory and its subdirectories to xhtml files, and stores the output in /home/you/html_code.
highlight --out-format=latex  * -d /home/you/latex_code/
converts all files to LaTeX, stored in /home/you/latex_code/.
Use --quiet to improve performance of batch file processing (recommended for usage in shell scripts).
Use highlight --out-format=xterm256 <yourfile> | less -R to display a source file in a terminal.
Run highlight --list-scripts=langs to see all supported syntax types.
Andre Simon <as@andre-simon.de>
README files and http://www.andre-simon.de/.
XFCE4-TERMINAL(1)                     Xfce                     XFCE4-TERMINAL(1)
xfce4-terminal - A Terminal emulator for X
xfce4-terminal [OPTION...]
xfce4-terminal is what is known as an X terminal emulator, often referred to as terminal or shell. It provides an equivalent to the old-fashioned text screen on your desktop, but one which can easily share the screen with other graphical applications. Windows users may already be familiar with the MS-DOS Prompt utility, which has the analogous function of offering a DOS command-line under Windows, though one should note that the UNIX CLI offer far more power and ease of use than does DOS.
xfce4-terminal emulates the xterm application developed by the X Consortium. In turn, the xterm application emulates the DEC VT102 terminal and also supports the DEC VT220 escape sequences. An escape sequence is a series of characters that start with the Esc character. xfce4-terminal accepts all of the escape sequences that the VT102 and VT220 terminals use for functions such as to position the cursor and to clear the screen.
Option Summary Here is a summary of all the options, grouped by type. Explanations are in the following sections.
General Options -h, --help; -V, --version; --disable-server; --color-table; --default-display=display; --default-working-directory=directory
Window or Tab Separators --tab; --window
Tab Options -x, --execute; -e, --command=command; -T, --title=title; --dynamic-title-mode=mode; --initial-title=title; --working-directory=directory; -H, --hold; --active-tab; --color-text=color; --color-bg=color
Window Options --display=display; --drop-down; --geometry=geometry; --role=role; --startup-id=string; -I, --icon=icon; --fullscreen; --maximize; --minimize; --show-menubar, --hide-menubar; --show-borders, --hide-borders; --show-toolbar, --hide-toolbar; --show-scrollbar, --hide-scrollbar; --font=font; --zoom=zoom
General Options -h, --help List the various command line options supported by xfce4-terminal and exit
-V, --version Display version information and exit
--disable-server Do not register with the D-BUS session message bus
--color-table Echo the color codes
--default-display=display Default X display to use.
--default-working-directory=directory Set directory as the default working directory for the terminal
Window or Tab Separators --tab Open a new tab in the last-specified window; more than one of these options can be provided.
If you use this as the first option, without --window separators, the last window will be re-used.
--window Open a new window containing one tab; more than one of these options can be provided.
Tab Options -x, --execute Execute the remainder of the command line inside the terminal
-e, --command=command Execute command inside the terminal
-T, --title=title Set title as the window title for the terminal (ignores dynamically-set title)
--dynamic-title-mode=mode Set mode as the dynamically-set title mode for the terminal, one of: 'replace', 'before', 'after', 'none'
--initial-title=title Set title as the initial window title for the terminal (respects dynamically-set title)
--working-directory=directory Set directory as the working directory for the terminal
-H, --hold Causes the terminal to be kept around after the child command has terminated
--active-tab Makes the terminal active: useful when a terminal window contains multiple tabs
--color-text=color Set color as the text color for the terminal per the following specification: https://developer.gnome.org/gdk3/stable/gdk3-RGBA-Colors.html#gdk-rgba-parse
--color-bg=color Set color as the background color for the terminal per the following specification: https://developer.gnome.org/gdk3/stable/gdk3-RGBA-Colors.html#gdk-rgba-parse
Window Options --display=display X display to use for the last- specified window.
--drop-down Will start the window in drop-down mode (also called a Quake-style terminal). This will only apply to the first window started with this option. It is advised to bind this to a shortcut in the keyboard preferences.
--geometry=geometry Sets the geometry of the last-specified window to geometry. Read X(7) for more information on how to specify window geometries.
--role=role Sets the window role of the last-specified window to role. Applies to only one window and can be specified once for each window you create from the command line. The role is a unique identifier for the window to be used when restoring a session.
--startup-id=string Specifies the startup notification id for the last-specified window. Used internally to forward the startup notification id when using the D-BUS service.
-I, --icon=icon Set the terminal's icon as an icon name or filename.
--fullscreen Set the last-specified window into fullscreen mode; applies to only one window; can be specified once for each window you create from the command line.
--maximize Set the last-specified window into maximized mode; applies to only one window; can be specified once for each window you create from the command line.
--minimize Set the last-specified window into minimized mode; applies to only one window; can be specified once for each window you create from the command line.
--show-menubar Turn on the menubar for the last-specified window. Can be specified once for each window you create from the command line.
--hide-menubar Turn off the menubar for the last-specified window. Can be specified once for each window you create from the command line.
--show-borders Turn on the window decorations for the last-specified window. Applies to only one window. Can be specified once for each window you create from the command line.
--hide-borders Turn off the window decorations for the last-specified window. Applies to only one window. Can be specified once for each window you create from the command line.
--show-toolbar Turn on the toolbar for the last-specified window. Applies to only one window. Can be specified once for each window you create from the command line.
--hide-toolbar Turn off the toolbar for the last-specified window. Applies to only one window. Can be specified once for each window you create from the command line.
--show-scrollbar Turn on the scrollbar for the last-specified window. Scrollbar position is taken from the settings; if position is None, the default position is Right side. Applies to only one window. Can be specified once for each window you create from the command line.
--hide-scrollbar Turn off the scrollbar for the last-specified window. Applies to only one window. Can be specified once for each window you create from the command line.
--font=font Set the terminal font.
--zoom=zoom Set the zoom level: the font size will be multiplied by this level. The range is from -7 to 7, default is 0. Each step multiplies the size by 1.2, i.e. level 7 is 3.5831808 (1.2^7) times larger than the default size.
xfce4-terminal --geometry 80x40 --command mutt --tab --command mc Opens a new terminal window with a geometry of 80 columns and 40 rows and two tabs in it, where the first tab runs mutt and the second tab runs mc.
xfce4-terminal uses the Basedir Specification as defined on Freedesktop.org[1] to locate its data and configuration files. This means that file locations will be specified as a path relative to the directories described in the specification.
${XDG_CONFIG_HOME} The first base directory to look for configuration files. By default this is set to ~/.config/.
${XDG_CONFIG_DIRS} A colon separated list of base directories that contain configuration data. By default the application will look in ${sysconfdir}/xdg/. The value of ${sysconfdir} depends on how the program was build and will often be /etc/ for binary packages.
${XDG_DATA_HOME} The root for all user-specific data files. By default this is set to ~/.local/share/.
${XDG_DATA_DIRS} A set of preference ordered base directories relative to which data files should be searched in addition to the ${XDG_DATA_HOME} base directory. The directories should be separated with a colon.
${XDG_CONFIG_DIRS}/xfce4/terminal/terminalrc This is the location of the configuration file that includes the preferences which control the look and feel of xfce4-terminal. Note: any update made to the configuration file via an external editor will be picked up by xfce4-terminal instances running.
${XDG_CONFIG_DIRS}/xfce4/terminal/accels.scm This is the location of the keyboard shortcuts configuration file for xfce4-terminal. Editing this file allows one to modify or disable shortcuts for the supported actions.
bash(1), X(7)
Igor Zakharov <f2404@yandex.ru> Developer
Nick Schermer <nick@xfce.org> Developer
Benedikt Meurer <benny@xfce.org> Software developer, os-cillation, System development, Developer
1. Freedesktop.org http://freedesktop.org/
IFTOP(8)                     System Manager's Manual                    IFTOP(8)
iftop - display bandwidth usage on an interface by host
iftop -h | [-nNpblBP] [-i interface] [-f filter code] [-F net/mask] [-G net6/mask6]
iftop listens to network traffic on a named interface, or on the first interface it can find which looks like an external interface if none is specified, and displays a table of current bandwidth usage by pairs of hosts.  iftop must be run with sufficient permissions to monitor all network traffic on the interface; see pcap(3) for more information, but on most systems this means that it must be run as root.
By default, iftop will look up the hostnames associated with addresses it finds in packets. This can cause substantial traffic of itself, and may result in a confusing display. You may wish to suppress display of DNS traffic by using filter code such as not port domain, or switch it off entirely, by using the -n option or by pressing r when the program is running.
By default, iftop counts all IP packets that pass through the filter, and the direction of the packet is determined according to the direction the packet is moving across the interface.  Using the -F option it is possible to get iftop to show packets entering and leaving a given network.  For example, iftop -F 10.0.0.0/255.0.0.0 will analyse packets flowing in and out of the 10.* network.
Some other filter ideas:
not ether host ff:ff:ff:ff:ff:ff Ignore ethernet broadcast packets.
port http and not host webcache.example.com Count web traffic only, unless it is being directed through a local web cache.
icmp   How much bandwidth are users wasting trying to figure out why the network is slow?
-h     Print a summary of usage.
-n     Don't do hostname lookups.
-N     Do not resolve port number to service names
-p     Run in promiscuous mode, so that traffic which does not pass directly through the specified interface is also counted.
-P     Turn on port display.
-l     Display and count datagrams addressed to or from link-local IPv6 addresses.  The default is not to display that address category.
-b     Don't display bar graphs of traffic.
-m limit Set the upper limit for the bandwidth scale.  Specified as a number with a 'K', 'M' or 'G' suffix.
-B     Display bandwidth rates in bytes/sec rather than bits/sec.
-i interface Listen to packets on interface.
-f filter code Use filter code to select the packets to count. Only IP packets are ever counted, so the specified code is evaluated as (filter code) and ip.
-F net/mask Specifies an IPv4 network for traffic analysis.  If specified, iftop will only include packets flowing in to or out of the given network, and packet direction is determined relative to the network boundary, rather than to the interface.  You may specify mask as a dotted quad, such as /255.255.255.0, or as a single number specifying the number of bits set in the netmask, such as /24.
-G net6/mask6 Specifies an IPv6 network for traffic analysis. The value of mask6 can be given as a prefix length or as a numerical address string for more compound bitmasking.
-c config file Specifies an alternate config file.  If not specified, iftop will use ~/.iftoprc if it exists.  See below for a description of config files
-t text output mode Use text interface without ncurses and print the output to STDOUT.
When running, iftop uses the whole screen to display network usage. At the top of the display is a logarithmic scale for the bar graph which gives a visual indication of traffic.
The main part of the display lists, for each pair of hosts, the rate at which data has been sent and received over the preceding 2, 10 and 40 second intervals. The direction of data flow is indicated by arrows, <= and =>. For instance,
foo.example.com  =>  bar.example.com      1Kb  500b   100b <=                       2Mb    2Mb    2Mb
shows, on the first line, traffic from foo.example.com to bar.example.com; in the preceding 2 seconds, this averaged 1Kbit/s, around half that amount over the preceding 10s, and a fifth of that over the whole of the last 40s. During each of those intervals, the data sent in the other direction was about 2Mbit/s. On the actual display, part of each line is inverted to give a visual indication of the 10s average of traffic.  You might expect to see something like this where host foo is making repeated HTTP requests to bar, which is sending data back which saturates a 2Mbit/s link.
By default, the pairs of hosts responsible for the most traffic (10 second average) are displayed at the top of the list.
At the bottom of the display, various totals are shown, including peak traffic over the last 40s, total traffic transferred (after filtering), and total transfer rates averaged over 2s, 10s and 40s.
SOURCE / DEST AGGREGATION By pressing s or d while iftop is running, all traffic for each source or destination will be aggregated together.  This is most useful when iftop is run in promiscuous mode, or is run on a gateway machine.
S or D toggle the display of source and destination ports respectively. p will toggle port display on/off.
t cycles through the four line display modes; the default 2-line display, with sent and received traffic on separate lines, and 3 1-line displays, with sent, received, or total traffic shown.
By default, the display is ordered according to the 10s average (2nd column).  By pressing 1, 2 or 3 it is possible to sort by the 1st, 2nd or 3rd column.   By pressing < or > the display will be sorted by source or destination hostname respectively.
l allows you to enter a POSIX extended regular expression that will be used to filter hostnames shown in the display.  This is a good way to quickly limit what is shown on the display.  Note that this happens at a much later stage than filter code, and does not affect what is actually captured.  Display filters DO NOT affect the totals at the bottom of the screen.
PAUSE DISPLAY / FREEZE ORDER P will pause the current display.
o will freeze the current screen order.  This has the side effect that traffic between hosts not shown on the screen at the time will not be shown at all, although it will be included in the totals at the bottom of the screen.
j and k will scroll the display of hosts.  This feature is most useful when the display order is frozen (see above).
f allows you to edit the filter code whilst iftop running.  This can lead to some unexpected behaviour.
iftop can read its configuration from a config file.  If the -c option is not specified, iftop will attempt to read its configuration from ~/.iftoprc, if it exists.  Any command line options specified will override settings in the config file.
The config file consists of one configuration directive per line.  Each directive is a name value pair, for example:
interface: eth0
sets the network interface.  The following config directives are supported:
interface: if Sets the network interface to if.
dns-resolution: (yes|no) Controls reverse lookup of IP addresses.
port-resolution: (yes|no) Controls conversion of port numbers to service names.
filter-code: bpf Sets the filter code to bpf.
show-bars: (yes|no) Controls display of bar graphs.
promiscuous: (yes|no) Puts the interface into promiscuous mode.
port-display: (off|source-only|destination-only|on) Controls display of port numbers.
link-local: (yes|no) Determines displaying of link-local IPv6 addresses.
hide-source: (yes|no) Hides source host names.
hide-destination: (yes|no) Hides destination host names.
use-bytes: (yes|no) Use bytes for bandwidth display, rather than bits.
sort: (2s|10s|40s|source|destination) Sets which column is used to sort the display.
line-display: (two-line|one-line-both|one-line-sent|one-line-received) Controls the appearance of each item in the display.
show-totals: (yes|no) Shows cumulative total for each item.
log-scale: (yes|no) Use a logarithmic scale for bar graphs.
max-bandwidth: bw Fixes the maximum for the bar graph scale to bw, e.g. "10M". Note that the value has to always be in bits, regardless if the option to display in bytes has been chosen.
net-filter: net/mask Defines an IP network boundary for determining packet direction.
net-filter6: net6/mask6 Defines an IPv6 network boundary for determining packet direction.
screen-filter: regexp Sets a regular expression to filter screen output.
QUIRKS (aka they're features, not bugs) There are some circumstances in which iftop may not do what you expect. In most cases what it is doing is logical, and we believe it is correct behaviour, although I'm happy to hear reasoned arguments for alternative behaviour.
Totals don't add up
There are several reasons why the totals may not appear to add up.  The most obvious is having a screen filter in effect, or screen ordering frozen.  In this case some captured information is not being shown to you, but is included in the totals.
A more subtle explanation comes about when running in promiscuous mode without specifying a -F option.  In this case there is no easy way to assign the direction of traffic between two third parties.  For the purposes of the main display this is done in an arbitrary fashion (by ordering of IP addresses), but for the sake of totals all traffic between other hosts is accounted as incoming, because that's what it is from the point of view of your interface.  The -F option allows you to specify an arbitrary network boundary, and to show traffic flowing across it.
Peak totals don't add up
Again, this is a feature.  The peak sent and peak received didn't necessarily happen at the same time.  The peak total is the maximum of sent plus received in each captured time division.
Changing the filter code doesn't seem to work
Give it time.  Changing the filter code affects what is captured from the time that you entered it, but most of what is on the display is based on some fraction of the last 40s window of capturing.  After changing the filter there may be entries on the display that are disallowed by the current filter for up to 40s.  DISPLAY FILTERING has immediate effect and does not affect what is captured.
~/.iftoprc Configuration file for iftop.
tcpdump(8), pcap(3), driftnet(1).
Paul Warren <pdw@ex-parrot.com>
$Id: iftop.8,v 1.31 2014/01/05 17:22:39 pdw Exp $
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
PV(1)                             User Manuals                             PV(1)
pv - monitor the progress of data through a pipe
pv [OPTION] [FILE]... pv [-h|-V]
pv shows the progress of data through a pipeline by giving information such as time elapsed, percentage completed (with progress bar), current throughput rate, total data transferred, and ETA.
To use it, insert it in a pipeline between two processes, with the appropriate options.  Its standard input will be passed through to its standard output and progress will be shown on standard error.
pv will copy each supplied FILE in turn to standard output (- means standard input), or if no FILEs are specified just standard input is copied. This is the same behaviour as cat(1).
A simple example to watch how quickly a file is transferred using nc(1):
pv file | nc -w 1 somewhere.com 3000
A similar example, transferring a file from another process and passing the expected size to pv:
cat file | pv -s 12345 | nc -w 1 somewhere.com 3000
A more complicated example using numeric output to feed into the dialog(1) program for a full-screen progress display:
(tar cf - . \ | pv -n -s $(du -sb . | awk '{print $1}') \ | gzip -9 > out.tgz) 2>&1 \ | dialog --gauge 'Progress' 7 70
Taking an image of a disk, skipping errors:
pv -EE /dev/your/disk/device > disk-image.img
Writing an image back to a disk:
pv disk-image.img > /dev/your/disk/device
Zeroing a disk:
pv < /dev/zero > /dev/your/disk/device
Note that if the input size cannot be calculated, and the output is a block device, then the size of the block device will be used and pv will automatically stop at that size as if -S had been given.
(Linux only): Watching file descriptor 3 opened by another process 1234:
pv -d 1234:3
(Linux only): Watching all file descriptors used by process 1234:
pv -d 1234
pv takes many options, which are divided into display switches, output modifiers, and general options.
If no display switches are specified, pv behaves as if -p, -t, -e, -r, and -b had been given (i.e. everything except average rate is switched on).  Otherwise, only those display types that are explicitly switched on will be shown.
-p, --progress Turn the progress bar on.  If standard input is not a file and no size was given (with the -s modifier), the progress bar cannot indicate how close to completion the transfer is, so it will just move left and right to indicate that data is moving.
-t, --timer Turn the timer on.  This will display the total elapsed time that pv has been running for.