neulab/tldr huggingface dataset:
-lss=FILENAME specify filename containing color-style information.  The default is lynx.lss.  If you give an empty filename, Lynx uses a built-in monochrome scheme which imitates the non-color-style configuration.
-mime_header prints the MIME header of a fetched document along with its source.
-minimal toggles minimal versus valid comment parsing.
-nested_tables toggles nested-tables logic (for debugging).
-newschunksize=NUMBER number of articles in chunked news listings.
-newsmaxchunk=NUMBER maximum news articles in listings before chunking.
-nobold disable bold video-attribute.
-nobrowse disable directory browsing.
-nocc  disable Cc: prompts for self copies of mailings.  Note that this does not disable any CCs which are incorporated within a mailto URL or form ACTION.
-nocolor force color mode off, overriding terminal capabilities and any -color flags, COLORTERM variable, and saved .lynxrc settings.
-noexec disable local program execution.  (DEFAULT)
-nofilereferer disable transmissions of Referer headers for file URLs.
-nolist disable the link list feature in dumps.
-nolog disable mailing of error messages to document owners.
-nomargins disable left/right margins in the default style sheet.
-nomore disable -more- string in statusline messages.
-nonrestarting_sigwinch This flag is not available on all systems, Lynx needs to be compiled with HAVE_SIGACTION defined.  If available, this flag may cause Lynx to react more immediately to window changes when run within an xterm.
-nonumbers disable link- and field-numbering.  This overrides -number_fields and -number_links.
-nopause disable forced pauses for statusline messages.
-noprint disable most print functions.
-noredir prevents automatic redirection and prints a message with a link to the new URL.
-noreferer disable transmissions of Referer headers.
-noreverse disable reverse video-attribute.
-nosocks disable SOCKS proxy usage by a SOCKSified Lynx.
-nostatus disable the retrieval status messages.
-notitle disable title and blank line from top of page.
-nounderline disable underline video-attribute.
-number_fields force numbering of links as well as form input fields
-number_links force numbering of links.
-partial toggles display partial pages while loading.
-partial_thres=NUMBER number of lines to render before repainting display with partial- display logic
-passive_ftp toggles passive ftp connections.
-pauth=ID:PASSWD set authorization ID and password for a protected proxy server at startup.  Be sure to protect any script files which use this switch.
-popup toggles handling of single-choice SELECT options via popup windows or as lists of radio buttons.
-post_data properly formatted data for a post form are read in from the standard input and passed to the form.  Input is terminated by a line that starts with “---”.
Lynx issues an HTTP POST, sending the form to the path or URL given on the command-line and prints the response of the server. If no path or URL is given, Lynx sends the form to the start-page.
-preparsed show HTML source preparsed and reformatted when used with -source or in source view.
-prettysrc show HTML source view with lexical elements and tags in color.
-print enable print functions.  (default)
-pseudo_inlines toggles pseudo-ALTs for inline images with no ALT string.
-raw   toggles default setting of 8-bit character translations or CJK mode for the startup character set.
-realm restricts access to URLs in the starting realm.
-read_timeout=N Sets the read-timeout, where N is given in seconds.
-reload flushes the cache on a proxy server (only the first document given on the command-line is affected).
-restrictions=[option][,option][,option]... allows a list of services to be disabled selectively.  Dashes and underscores in option names can be intermixed.  The following list is printed if no options are specified.
all restricts all options listed below.
bookmark disallow changing the location of the bookmark file.
bookmark_exec disallow execution links via the bookmark file.
change_exec_perms disallow changing the eXecute permission on files (but still allow it for directories) when local file management is enabled.
default same as command line option -anonymous.  Disables default services for anonymous users.  Set to all restricted, except for: inside_telnet, outside_telnet, inside_ftp, outside_ftp, inside_rlogin, outside_rlogin, inside_news, outside_news, telnet_port, jump, mail, print, exec, and goto.  The settings for these, as well as additional goto restrictions for specific URL schemes that are also applied, are derived from definitions within userdefs.h.
dired_support disallow local file management.
disk_save disallow saving to disk in the download and print menus.
dotfiles disallow access to, or creation of, hidden (dot) files.
download disallow some downloaders in the download menu (does not imply disk_save restriction).
editor disallow external editing.
exec disable execution scripts.
exec_frozen disallow the user from changing the local execution option.
externals disallow some “EXTERNAL” configuration lines if support for passing URLs to external applications (with the EXTERN command) is compiled in.
file_url disallow using G)oto, served links or bookmarks for file: URLs.
goto disable the “g” (goto) command.
inside_ftp disallow ftps for people coming from inside your domain (utmp required for selectivity).
inside_news disallow USENET news posting for people coming from inside your domain (utmp required for selectivity).
inside_rlogin disallow rlogins for people coming from inside your domain (utmp required for selectivity).
inside_telnet disallow telnets for people coming from inside your domain (utmp required for selectivity).
jump disable the “j” (jump) command.
multibook disallow multiple bookmarks.
mail disallow mail.
news_post disallow USENET News posting.
options_save disallow saving options in .lynxrc.
outside_ftp disallow ftps for people coming from outside your domain (utmp required for selectivity).
outside_news disallow USENET news reading and posting for people coming from outside your domain (utmp required for selectivity).  This restriction applies to “news”, “nntp”, “newspost”, and “newsreply” URLs, but not to “snews”, “snewspost”, or “snewsreply” in case they are supported.
outside_rlogin disallow rlogins for people coming from outside your domain (utmp required for selectivity).
outside_telnet disallow telnets for people coming from outside your domain (utmp required for selectivity).
print disallow most print options.
shell disallow shell escapes and lynxexec or lynxprog G)oto's.
suspend disallow Unix Control-Z suspends with escape to shell.
telnet_port disallow specifying a port in telnet G)oto's.
useragent disallow modifications of the User-Agent header.
-resubmit_posts toggles forced resubmissions (no-cache) of forms with method POST when the documents they returned are sought with the PREV_DOC command or from the History List.
-rlogin disable recognition of rlogin commands.
-scrollbar toggles showing scrollbar.
-scrollbar_arrow toggles showing arrows at ends of the scrollbar.
-selective require .www_browsable files to browse directories.
-session=FILENAME resumes from specified file on startup and saves session to that file on exit.
-sessionin=FILENAME resumes session from specified file.
-sessionout=FILENAME saves session to specified file.
-short_url show very long URLs in the status line with “...” to represent the portion which cannot be displayed.  The beginning and end of the URL are displayed, rather than suppressing the end.
-show_cfg Print the configuration settings, e.g., as read from “lynx.cfg”, and exit.
-show_cursor If enabled the cursor will not be hidden in the right hand corner but will instead be positioned at the start of the currently selected link.  Show cursor is the default for systems without FANCY_CURSES capabilities.  The default configuration can be changed in userdefs.h or lynx.cfg.  The command line switch toggles the default.
-show_rate If enabled the transfer rate is shown in bytes/second.  If disabled, no transfer rate is shown.  Use lynx.cfg or the options menu to select KB/second and/or ETA.
-soft_dquotes toggles emulation of the old Netscape and Mosaic bug which treated “>” as a co-terminator for double-quotes and tags.
-source works the same as dump but outputs HTML source instead of formatted text.  For example
lynx -source . >foo.html
generates HTML source listing the files in the current directory. Each file is marked by an HREF relative to the parent directory. Add a trailing slash to make the HREF's relative to the current directory:
lynx -source ./ >foo.html
-stack_dump disable SIGINT cleanup handler
-startfile_ok allow non-http startfile and homepage with -validate.
-stderr When dumping a document using -dump or -source, Lynx normally does not display alert (error) messages that you see on the screen in the status line.  Use the -stderr option to tell Lynx to write these messages to the standard error.
-stdin read the startfile from standard input (UNIX only).
-syslog=text information for syslog call.
-syslog_urls log requested URLs with syslog.
-tagsoup initialize parser, using Tag Soup DTD rather than SortaSGML.
-telnet disable recognition of telnet commands.
-term=TERM tell Lynx what terminal type to assume it is talking to.  (This may be useful for remote execution, when, for example, Lynx connects to a remote TCP/IP port that starts a script that, in turn, starts another Lynx process.)
-timeout=N For win32, sets the network read-timeout, where N is given in seconds.
-tlog  toggles between using a Lynx Trace Log and stderr for trace output from the session.
-tna   turns on “Textfields Need Activation” mode.
-trace turns on Lynx trace mode.  Destination of trace output depends on -tlog.
-trace_mask=value turn on optional traces, which may result in very large trace files.  Logically OR the values to combine options:
1  SGML character parsing states
2  color-style
4  TRST (table layout)
8  configuration (lynx.cfg, .lynxrc, .lynx-keymaps, mime.types and mailcap contents)
16 binary string copy/append, used in form data construction.
32 cookies
64 character sets
128 GridText parsing
256 timing
-traversal traverse all http links derived from startfile.  When used with -crawl, each link that begins with the same string as startfile is output to a file, intended for indexing.
See CRAWL.announce for more information.
-trim_blank_lines toggles trimming of trailing blank lines as well as the related trimming of blank lines while collapsing BR tags.
-trim_input_fields trim input text/textarea fields in forms.
-underline_links toggles use of underline/bold attribute for links.
-underscore toggles use of _underline_ format in dumps.
-unique_urls check for duplicate link numbers in each page and corresponding lists, and reuse the original link number.
-use_mouse turn on mouse support, if available.  Clicking the left mouse button on a link traverses it.  Clicking the right mouse button pops back.  Click on the top line to scroll up.  Click on the bottom line to scroll down.  The first few positions in the top and bottom line may invoke additional functions.  Lynx must be compiled with ncurses or slang to support this feature.  If ncurses is used, clicking the middle mouse button pops up a simple menu.  Mouse clicks may only work reliably while Lynx is idle waiting for input.
-useragent=Name set alternate Lynx User-Agent header.
-validate accept only http URLs (for validation).  Complete security restrictions also are implemented.
-verbose toggle [LINK], [IMAGE] and [INLINE] comments with filenames of these images.
-version print version information, and exit.
-vikeys enable vi-like key movement.
-wdebug enable Waterloo tcp/ip packet debug (print to watt debugfile). This applies only to DOS versions compiled with WATTCP or WATT-32.
-width=NUMBER number of columns for formatting of dumps, default is 80.  This is limited by the number of columns that Lynx could display, typically 1024 (the MAX_LINE symbol).
-with_backspaces emit backspaces in output if -dump'ing or -crawl'ing (like man does)
-xhtml_parsing tells Lynx that it can ignore certain tags which have no content in an XHTML 1.0 document.  For example “<p/>” will be discarded.
More than one key can be mapped to a given command.  Here are some of the most useful:
•   Use Up arrow and Down arrow to scroll through hypertext links.
•   Right arrow or Return will follow a highlighted hypertext link.
•   Left Arrow or “u” will retreat from a link.
•   Type “H”, “?”, or F1 for online help and descriptions of key-stroke commands.
•   Type “k” or “K” for a list of the current key-stroke command mappings.
If the same command is mapped to the same letter differing only by upper/lowercase only the lowercase mapping is shown.
•   Type Delete to view history list.
In addition to various “standard” environment variables such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx utilizes several Lynx-specific environment variables, if they exist.
Others may be created or modified by Lynx to pass data to an external program, or for other reasons.  These are listed separately below.
See also the sections on SIMULATED CGI SUPPORT and NATIVE LANGUAGE SUPPORT, below.
Note:  Not all environment variables apply to all types of platforms supported by Lynx, though most do.  Feedback on platform dependencies is solicited.
Environment Variables Used By Lynx:
COLORTERM           If set, color capability for the terminal is forced on at startup time.  The actual value assigned to the variable is ignored.  This variable is only meaningful if Lynx was built using the slang screen- handling library.
LYNX_CFG            This variable, if set, will override the default location and name of the global configuration file (normally, lynx.cfg) that was defined by the LYNX_CFG_FILE constant in the userdefs.h file, during installation.
See the userdefs.h file for more information.
LYNX_CFG_PATH       If set, this variable overrides the compiled-in search-list of directories used to find the configuration files, e.g., lynx.cfg and lynx.lss. The list is delimited with ":" (or ";" for Windows) like the PATH environment variable.
LYNX_HELPFILE       If set, this variable overrides the compiled-in URL and configuration file URL for the Lynx help file.
LYNX_LOCALEDIR      If set, this variable overrides the compiled-in location of the locale directory which contains native language (NLS) message text.
LYNX_LSS            This variable, if set, specifies the location of the default Lynx character style sheet file.  [Currently only meaningful if Lynx was built using curses color style support.]
LYNX_SAVE_SPACE     This variable, if set, will override the default path prefix for files saved to disk that is defined in the lynx.cfg SAVE_SPACE: statement.
See the lynx.cfg file for more information.
LYNX_TEMP_SPACE     This variable, if set, will override the default path prefix for temporary files that was defined during installation, as well as any value that may be assigned to the TMPDIR variable.
MAIL                This variable specifies the default inbox Lynx will check for new mail, if such checking is enabled in the lynx.cfg file.
NEWS_ORGANIZATION   This variable, if set, provides the string used in the Organization: header of USENET news postings.  It will override the setting of the ORGANIZATION environment variable, if it is also set (and, on UNIX, the contents of an /etc/organization file, if present).
NNTPSERVER          If set, this variable specifies the default NNTP server that will be used for USENET news reading and posting with Lynx, via news: URL's.
ORGANIZATION        This variable, if set, provides the string used in the Organization: header of USENET news postings.  On UNIX, it will override the contents of an /etc/organization file, if present.
PROTOCOL_proxy      Lynx supports the use of proxy servers that can act as firewall gateways and caching servers.  They are preferable to the older gateway servers (see WWW_access_GATEWAY, below).
Each protocol used by Lynx, (http, ftp, gopher, etc), can be mapped separately by setting environment variables of the form PROTOCOL_proxy.  Protocols are indicated in a URI by the name before “:”, e.g., “http” in “http://some.server.dom:port/” for HTML.
Depending on your system configuration and supported protocols, the environment variables recognized by lynx may include
cso_proxy finger_proxy ftp_proxy gopher_proxy https_proxy http_proxy newspost_proxy newsreply_proxy news_proxy nntp_proxy no_proxy snewspost_proxy snewsreply_proxy snews_proxy wais_proxy
See Lynx Users Guide for additional details and examples.
SSL_CERT_DIR        Set to the directory containing trusted certificates.
SSL_CERT_FILE       Set to the full path and filename for your file of trusted certificates.
WWW_access_GATEWAY  Lynx still supports use of gateway servers, with the servers specified via “WWW_access_GATEWAY” variables (where “access” is lower case and can be “http”, “ftp”, “gopher” or “wais”).  However most gateway servers have been discontinued.  Note that you do not include a terminal “/” for gateways, but do for proxies specified by PROTOCOL_proxy environment variables.
See Lynx Users Guide for details.
WWW_HOME            This variable, if set, will override the default startup URL specified in any of the Lynx configuration files.
Environment Variables Set or Modified By Lynx:
LYNX_PRINT_DATE     This variable is set by the Lynx p(rint) function, to the Date: string seen in the document's “Information about” page (= cmd), if any.  It is created for use by an external program, as defined in a lynx.cfg PRINTER: definition statement.  If the field does not exist for the document, the variable is set to a null string under UNIX, or “No Date” under VMS.
LYNX_PRINT_LASTMOD  This variable is set by the Lynx p(rint) function, to the Last Mod: string seen in the document's “Information about” page (= cmd), if any.  It is created for use by an external program, as defined in a lynx.cfg PRINTER: definition statement.  If the field does not exist for the document, the variable is set to a null string under UNIX, or “No LastMod” under VMS.
LYNX_PRINT_TITLE    This variable is set by the Lynx p(rint) function, to the Linkname: string seen in the document's “Information about” page (= cmd), if any.  It is created for use by an external program, as defined in a lynx.cfg PRINTER: definition statement.  If the field does not exist for the document, the variable is set to a null string under UNIX, or “No Title” under VMS.
LYNX_PRINT_URL      This variable is set by the Lynx p(rint) function, to the URL: string seen in the document's “Information about” page (= cmd), if any.  It is created for use by an external program, as defined in a lynx.cfg PRINTER: definition statement.  If the field does not exist for the document, the variable is set to a null string under UNIX, or “No URL” under VMS.
LYNX_TRACE          If set, causes Lynx to write a trace file as if the -trace option were supplied.
LYNX_TRACE_FILE     If set, overrides the compiled-in name of the trace file, which is either Lynx.trace or LY-TRACE.LOG (the latter on the DOS/Windows platforms).  The trace file is in either case relative to the home directory.
LYNX_VERSION        This variable is always set by Lynx, and may be used by an external program to determine if it was invoked by Lynx.
See also the comments in the distribution's sample mailcap file, for notes on usage in such a file.
TERM                Normally, this variable is used by Lynx to determine the terminal type being used to invoke Lynx.  If, however, it is unset at startup time (or has the value “unknown”), or if the -term command-line option is used (see OPTIONS section above), Lynx will set or modify its value to the user specified terminal type (for the Lynx execution environment).  Note: If set/modified by Lynx, the values of the LINES and/or COLUMNS environment variables may also be changed.
If built with the cgi-links option enabled, Lynx allows access to a cgi script directly without the need for an http daemon.
When executing such “lynxcgi scripts” (if enabled), the following variables may be set for simulating a CGI environment:
CONTENT_LENGTH
CONTENT_TYPE
DOCUMENT_ROOT
HTTP_ACCEPT_CHARSET
HTTP_ACCEPT_LANGUAGE
HTTP_USER_AGENT
PATH_INFO
PATH_TRANSLATED
QUERY_STRING
REMOTE_HOST
REQUEST_METHOD
SERVER_SOFTWARE
Other environment variables are not inherited by the script, unless they are provided via a LYNXCGI_ENVIRONMENT statement in the configuration file.  See the lynx.cfg file, and the (draft) CGI 1.1 Specification <http://Web.Golux.Com/coar/cgi/draft-coar-cgi-v11-00.txt> for the definition and usage of these variables.
The CGI Specification, and other associated documentation, should be consulted for general information on CGI script programming.
If configured and installed with Native Language Support, Lynx will display status and other messages in your local language.  See the file ABOUT_NLS in the source distribution, or at your local GNU site, for more information about internationalization.
The following environment variables may be used to alter default settings:
LANG                This variable, if set, will override the default message language.  It is an ISO 639 two-letter code identifying the language.  Language codes are NOT the same as the country codes given in ISO 3166.
LANGUAGE            This variable, if set, will override the default message language.  This is a GNU extension that has higher priority for setting the message catalog than LANG or LC_ALL.
LC_ALL              and
LC_MESSAGES         These variables, if set, specify the notion of native language formatting style.  They are POSIXly correct.
LINGUAS             This variable, if set prior to configuration, limits the installed languages to specific values.  It is a space-separated list of two-letter codes.  Currently, it is hard-coded to a wish list.
NLSPATH             This variable, if set, is used as the path prefix for message catalogs.
This is the Lynx v2.8.9 Release; development is in progress for 2.9.0.
If you wish to contribute to the further development of Lynx, subscribe to our mailing list.  Send email to <lynx-dev-request@nongnu.org> with “subscribe lynx-dev” as the only line in the body of your message.
Send bug reports, comments, suggestions to <lynx-dev@nongnu.org> after subscribing.
Unsubscribe by sending email to <lynx-dev-request@nongnu.org> with “unsubscribe lynx-dev” as the only line in the body of your message.  Do not send the unsubscribe message to the lynx-dev list, itself.
catgets(3), curses(3), environ(7), execve(2), ftp(1), gettext(GNU), localeconv(3), ncurses(3), setlocale(3), slang(?), termcap(5), terminfo(5), wget(GNU)
Note that man page availability and section numbering is somewhat platform dependent, and may vary from the above references.
A section shown as (GNU), is intended to denote that the topic may be available via an info page, instead of a man page (i.e., try “info subject”, rather than “man subject”).
A section shown as (?) denotes that documentation on the topic exists, but is not part of an established documentation retrieval system (see the distribution files associated with the topic, or contact your System Administrator for further information).
Lynx has incorporated code from a variety of sources along the way.  The earliest versions of Lynx included code from Earl Fogel of Computing Services at the University of Saskatchewan, who implemented HYPERREZ in the Unix environment.  HYPERREZ was developed by Niel Larson of Think.com and served as the model for the early versions of Lynx.  Those versions also incorporated libraries from the Unix Gopher clients developed at the University of Minnesota, and the later versions of Lynx rely on the WWW client library code developed by Tim Berners-Lee and the WWW community. Also a special thanks to Foteos Macrides who ported much of Lynx to VMS and did or organized most of its development since the departures of Lou Montulli and Garrett Blythe from the University of Kansas in the summer of 1994 through the release of v2.7.2, and to everyone on the net who has contributed to Lynx's development either directly (through patches, comments or bug reports) or indirectly (through inspiration and development of other systems).
Lou Montulli, Garrett Blythe, Craig Lavender, Michael Grobe, Charles Rezac Academic Computing Services University of Kansas Lawrence, Kansas 66047
Foteos Macrides Worcester Foundation for Biomedical Research Shrewsbury, Massachusetts 01545
Thomas E. Dickey <dickey@invisible-island.net>
CHFN(1)                      General Commands Manual                     CHFN(1)
chfn - zmienia nazwę użytkownika i informację o nim
chfn [-f pełna_nazwa] [-r nr_pokoju] [-w tel_służb] [-h tel_dom] [-o inne] [użytkownik]
chfn zmienia pełną nazwę (imię i nazwisko), telefon służbowy i domowy dla danego konta użytkownika. Informacja ta jest zwykle drukowana przez finger(1) i podobne mu programy.  Zwykły użytkownik może zmieniać wyłącznie pola opisujące własne konto.  Tylko superużytkownik może zmieniać pola dowolnego konta.  Również tylko on może posłużyć się opcją -o by zmienić niezdefiniowane części pola GECOS.
Jedynym ograniczeniem nakładanym na zawartość pól jest zakaz używania w nich znaków sterujących oraz przecinka, dwukropka i znaku równości.  Pola inne (other) nie obowiązuje to ograniczenie. Pole to służy do przechowywania informacji rozliczeniowej używanej przez inne aplikacje.
Jeśli nie wybrano żadnej z opcji, to chfn działa w trybie interaktywnym, proponując użytkownikowi wartości bieżące dla każdego z pól. Należy wprowadzić nową wartość by zmienić pole, lub pozostawić pustą by użyć wartości bieżącej.  Bieżąca wartość pola wyświetlana jest między parą znaczników [ ].  Bez podania opcji chfn pyta o konto użytkownika, które ma podlegać zmianie.
/etc/passwd - informacja o kontach użytkowników
DELUGED(1)                   General Commands Manual                  DELUGED(1)
deluged - A BitTorrent client daemon
deluged [options]
By default deluged will run as a background daemon, use the -d option to run process in foreground.
Daemon Options -p port, --port=port Port daemon will listen on, default is 58846
-i ip_address, --interface=ip_address Interface daemon will listen for bittorrent connections on, this should be an IP address
-u ip_address, --ui-interface=ip_address Interface daemon will listen for UI connections on, this should be an IP address
Process Control Options: -P file, --pidfile=file Pidfile to store the process id
-d, --do-not-daemonize Do not daemonize (fork) this process
-U, --user=user Change to this user on startup (Requires root)
-g, --group=group Change to this group on startup (Requires root)
deluge(1), deluge-web(1), deluge-console(1)
ZIPALIGN(1)                                                          ZIPALIGN(1)
zipalign - ZIP/APK alignment tool for Android application files
To align infile.zip and save it as outfile.zip:
zipalign [-f] [-p] [-v] [-z] align infile.zip outfile.zip
To confirm the alignment of existing.zip:
zipalign -c [-p] [-v] align existing.zip
The align is an integer that defines the byte-alignment boundaries.  This must always be 4 (which provides 32-bit alignment) or else it effectively does nothing.
zipalign is an archive alignment tool that provides important optimization to Android application (.apk) files.  The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file.  Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries.  This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions.  The benefit is a reduction in the amount of RAM consumed when running the application.
This tool should always be used to align your APK file before distributing it to end-users.  The Android build tools can handle this for you.  Android Studio automatically aligns your APK.
Caution: You must use zipalign at one of two specific points in the app-building process, depending on which app-signing tool you use:
• If you use apksigner, zipalign must only be performed before the APK file has been signed.  If you sign your APK using apksigner and make further changes to the APK, its signature is invalidated.
• If you use jarsigner, zipalign must only be performed after the APK file has been signed.
The adjustment is made by altering the size of the “extra” field in the zip Local File Header sections.  Existing data in the “extra” fields may be altered by this process.
For more information about how to use zipalign when building your application, please read “Signing Your Application”: https://developer.android.com/tools/publishing/app-signing.html
-c     Check alignment only (does not modify file)
-f     Overwrite existing outfile.zip
-p     Memory page alignment for stored shared object files
-z     Recompress using Zopfli
ZIPTIME(1)
https://developer.android.com/studio/command-line/zipalign.html
libreoffice(1)                    User Commands                   libreoffice(1)
Name libreoffice - LibreOffice office suite
libreoffice [--accept=accept-string] [--base] [--calc] [--convert-to output_file_extension[:output_filter_name] [--outdir output_dir] file]... [--display display] [--draw] [--global] [--headless] [--help|-h|-?] [--impress] [--invisible] [--infilter="<filter>"] [--math] [--minimized] [-n file]... [--nodefault] [--nolockcheck] [--nologo] [--norestore] [-o file]... [-p file...]  [--print-to-file [--printer-name printer_name] [--outdir output_dir] file]...  [--pt printername file...]  [--show Impress file]... [--unaccept=accept-string] [--terminate_after_init] [--view file]... [--web] [--writer]  [file...] lobase localc lodraw lofromtemplate loimpress lomath loweb lowriter
LibreOffice (LO for short) is a multi-platform office productivity suite. It was derived from OpenOffice.org 3.3 Beta on September 28, 2010.
libreoffice is a shell script that sets up the environment and passes the command line arguments to the soffice.bin binary.
Alternatively, the following helper scripts start the respective module:
sbase, scalc, sdraw, simpress, smath, sofficerc, swriter
--accept=accept-string Specifies a UNO-URL connect-string to create a UNO acceptor through which other programs can connect to access the API. Note that API access allows execution of arbitrary commands.  The syntax of a UNO-URL connect-string is: uno:connection- type,params;protocol-name,params;ObjectName
--base Starts the wizard for a new Base document.
--calc Starts with a new Calc document.
--convert-to output_file_extension[:output_filter_name] [--outdir output_dir] file... Batch converts files.  If --outdir is not specified then the current working directory is used as the output directory for the converted files. It implies --headless.
--convert-to pdf *.doc
Converts all .doc files to PDFs.
--convert-to pdf:writer_pdf_Export --outdir /home/user *.doc
Converts all .doc files to PDFs using the settings in the Writer PDF export dialog and saving them in /home/user.
--display display This option specifies the X server to use; see X(7)
--draw Starts with a new Draw document.
--global Starts with a new Global document.
--headless Starts in "headless mode", which allows using the application without user a interface.
This special mode can be used when the application is controlled by external clients via the API.
It implies --invisible and strictly ignores any GUI environment. --quickstart does not work with this parameter.
--help|-h|-? Lists LibreOffice command line parameters.
--impress Starts with a new Impress document.
--invisible Starts in invisible mode.
Neither the start-up logo nor the initial program window will be visible.  LO can be controlled and documents and dialogs can be opened via the API.
When started with this parameter, it can only be quit using the taskmanager (Windows) or the kill command (UNIX based systems).
--quickstart does not work with this parameter.
--infilter="<filter>" Force an input filter type if possible.  For example --infilter="Calc Office Open XML" only
--math Starts with a new Math document.
--minimized Keeps the splash screen minimized.
-n template... Creates the a new document from the given templates.
--nodefault Starts LO without creating a new document.  The next time you start LO, the welcome screen is shown.
It's used together with --nologo by quick starters. Note that --quickstart has no longer been supported since OpenOffice.org 2.0.0.
--nolockcheck Disables the check for remote instances using the installation.
--nologo Disables the splash screen at program start.
--norestore Disables restart and file recovery after a system crash. It is possible that LO will try to restore a file it keeps crashing on, if that happens --norestore is the only way to start LO.
--nosplash Disables the splash screen at program start.
-o file... Opens the given files for editing, even templates.
Without -o a template file would create a new document derived from that template.
-p file... Prints the given files to the default printer and ends. The splash screen does not appear.
If the file name contains spaces, then it must be enclosed in quotation marks.
--print-to-file [--printer-name printer_name] [--outdir output_dir] file... Batch print files to file.  If --printer-name is not specified the default printer is used.  If --outdir is not specified then the current working directory is used as the output directory for the converted files.
--print-to-file *.doc
Prints all .doc files to the current working directory using the default printer.
--print-to-file --printer-name nasty_lowres_printer --outdir /home/user *.doc
Prints all .doc files to /home/user directory using the nasty_lowres_printer.
--pt printername file... Prints the given files to the printer printername and ends. The splash screen does not appear.
If a file name contains spaces, then it must be enclosed in quotation marks.
--quickstart --quickstart=no Starts LO with its quick starter.  --quickstart disable the quick starter.
Does not work with --invisible or --headless.
--show Impress file... Opens the given Impress files, starts the presentation and quits after they have finished.
--unaccept=accept-string Closes an acceptor that was created with --accept option.
Use --unaccept=all to close all open acceptors.
--terminate_after_init Starts LO and terminates after it registers some UNO services. Doesn't show the splash during startup.
--view file... Opens the given files read-only creating a temporary copy of them at $TMPDIR.
--web  Starts with a new HTML document.
--writer Starts with a new Writer document.
See http://wiki.documentfoundation.org/BugReport for more details on how to report bugs in LibreOffice.
http://www.documentfoundation.org/
This manual page was created by Rene Engelhard <rene@debian.org> for the Debian GNU/Linux Distribution, because the original package does not have one. It was updated for Novell by Petr Mladek <petr.mladek@novell.com> and adapted for LibreOffice by Philipp Weissenbacher <philipp.weissenbacher@gmail.com>.
dotnet build command(1)             .NET Core            dotnet build command(1)
dotnet build This article applies to: ✓ .NET Core 1.x SDK and later versions
dotnet build - Builds a project and all of its dependencies.
dotnet build [<PROJECT>|<SOLUTION>] [-c|--configuration] [-f|--framework] [--force] [--interactive] [--no-dependencies] [--no-incremental] [--no-restore] [--nologo] [-o|--output] [-r|--runtime] [-v|--verbosity] [--version-suffix]
dotnet build [-h|--help]
The dotnet build command builds the project and its dependencies into a set of binaries.  The binaries include the project’s code in Intermediate Language (IL) files with a .dll extension.  Depending on the project type and settings, other files may be included, such as:
• An executable that can be used to run the application, if the project type is an executable targeting .NET Core 3.0 or later.
• Symbol files used for debugging with a .pdb extension.
• A .deps.json file, which lists the dependencies of the application or library.
• A .runtimeconfig.json file, which specifies the shared runtime and its version for an application.
• Other libraries that the project depends on (via project references or NuGet package references).
For executable projects targeting versions earlier than .NET Core 3.0, library dependencies from NuGet are typically NOT copied to the output folder.  They’re resolved from the NuGet global packages folder at run time.  With that in mind, the product of dotnet build isn’t ready to be transferred to another machine to run.  To create a version of the application that can be deployed, you need to publish it (for example, with the dotnet publish command).  For more information, see .NET Core Application Deployment.
For executable projects targeting .NET Core 3.0 and later, library dependencies are copied to the output folder.  This means that if there isn’t any other publish-specific logic (such as Web projects have), the build output should be deployable.
Building requires the project.assets.json file, which lists the dependencies of your application.  The file is created when dotnet restore is executed.  Without the assets file in place, the tooling can’t resolve reference assemblies, which results in errors.  With .NET Core 1.x SDK, you needed to explicitly run dotnet restore before running dotnet build.  Starting with .NET Core 2.0 SDK, dotnet restore runs implicitly when you run dotnet build.  If you want to disable implicit restore when running the build command, you can pass the --no-restore option.
Whether the project is executable or not is determined by the <OutputType> property in the project file.  The following example shows a project that produces executable code:
<PropertyGroup> <OutputType>Exe</OutputType> </PropertyGroup>
To produce a library, omit the <OutputType> property or change its value to Library.  The IL DLL for a library doesn’t contain entry points and can’t be executed.
MSBuild dotnet build uses MSBuild to build the project, so it supports both parallel and incremental builds.  For more information, see Incremental Builds.
In addition to its options, the dotnet build command accepts MSBuild options, such as -p for setting properties or -l to define a logger.  For more information about these options, see the MSBuild Command-Line Reference.  Or you can also use the dotnet msbuild command.
Running dotnet build is equivalent to running dotnet msbuild -restore; however, the default verbosity of the output is different.
Arguments PROJECT | SOLUTION
The project or solution file to build.  If a project or solution file isn’t specified, MSBuild searches the current working directory for a file that has a file extension that ends in either proj or sln and uses that file.
• -c|--configuration {Debug|Release}
Defines the build configuration.  The default for most projects is Debug, but you can override the build configuration settings in your project.
• -f|--framework <FRAMEWORK>
Compiles for a specific framework.  The framework must be defined in the project file.
• --force
Forces all dependencies to be resolved even if the last restore was successful.  Specifying this flag is the same as deleting the project.assets.json file.  Available since .NET Core 2.0 SDK.
• -h|--help
• --interactive
Allows the command to stop and wait for user input or action.  For example, to complete authentication.  Available since .NET Core 3.0 SDK.
• --no-dependencies
Ignores project-to-project (P2P) references and only builds the specified root project.
• --no-incremental
Marks the build as unsafe for incremental build.  This flag turns off incremental compilation and forces a clean rebuild of the project’s dependency graph.
• --no-restore
Doesn’t execute an implicit restore during build.  Available since .NET Core 2.0 SDK.
• --nologo
Doesn’t display the startup banner or the copyright message.  Available since .NET Core 3.0 SDK.
• -o|--output <OUTPUT_DIRECTORY>
Directory in which to place the built binaries.  If not specified, the default path is ./bin/<configuration>/<framework>/.  For projects with multiple target frameworks (via the TargetFrameworks property), you also need to define --framework when you specify this option.
• -r|--runtime <RUNTIME_IDENTIFIER>
Specifies the target runtime.  For a list of Runtime Identifiers (RIDs), see the RID catalog.
• -v|--verbosity <LEVEL>
Sets the MSBuild verbosity level.  Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].  The default is minimal.
• --version-suffix <VERSION_SUFFIX>
Sets the value of the $(VersionSuffix) property to use when building the project.  This only works if the $(Version) property isn’t set. Then, $(Version) is set to the $(VersionPrefix) combined with the $(VersionSuffix), separated by a dash.
• Build a project and its dependencies:
• Build a project and its dependencies using Release configuration:
dotnet build --configuration Release
• Build a project and its dependencies for a specific runtime (in this example, Ubuntu 18.04):
dotnet build --runtime ubuntu.18.04-x64
• Build the project and use the specified NuGet package source during the restore operation (.NET Core 2.0 SDK and later versions):
dotnet build --source c:\packages\mypackages
• Build the project and set version 1.2.3.4 as a build parameter using the -p MSBuild option:
dotnet build -p:Version=1.2.3.4
WINE(1)                          Windows On Unix                         WINE(1)
wine - run Windows programs on Unix
wine program [arguments] wine --help wine --version
For instructions on passing arguments to Windows programs, please see the PROGRAM/ARGUMENTS section of the man page.
wine loads and runs the given program, which can be a DOS, Windows 3.x, Win32 or Win64 executable (on 64-bit systems).
For debugging wine, use winedbg instead.
For running CUI executables (Windows console programs), use wineconsole instead of wine.  This will display the output in a separate window. Not using wineconsole for CUI programs will only provide very limited console support, and your program might not function properly.
When invoked with --help or --version as the only argument, wine will simply print a small help message or its version respectively and exit.
PROGRAM/ARGUMENTS The program name may be specified in DOS format (C:\\WINDOWS\\SOL.EXE) or in Unix format (/msdos/windows/sol.exe).  You may pass arguments to the program being executed by adding them to the end of the command line invoking wine (such as: wine notepad C:\\TEMP\\README.TXT).  Note that you need to '\' escape special characters (and spaces) when invoking Wine via a shell, e.g.
wine C:\\Program\ Files\\MyPrg\\test.exe
It can also be one of the Windows executables shipped with Wine, in which case specifying the full path is not mandatory, e.g. wine explorer or wine notepad.
wine makes the environment variables of the shell from which it is started accessible to the Windows/DOS processes started. So use the appropriate syntax for your shell to enter environment variables you need.
WINEPREFIX If set, the contents of this variable is taken as the name of the directory where Wine stores its data (the default is $HOME/.wine). This directory is also used to identify the socket which is used to communicate with the wineserver.  All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory, and config file.  By setting WINEPREFIX to different values for different wine processes, it is possible to run a number of truly independent wine processes.
WINESERVER Specifies the path and name of the wineserver binary. If not set, Wine will try to load /usr/bin/wineserver, and if this doesn't exist it will then look for a file named "wineserver" in the path and in a few other likely locations.
WINELOADER Specifies the path and name of the wine binary to use to launch new Windows processes. If not set, Wine will try to load /usr/bin/wine, and if this doesn't exist it will then look for a file named "wine" in the path and in a few other likely locations.
WINEDEBUG Turns debugging messages on or off. The syntax of the variable is of the form [class][+|-]channel[,[class2][+|-]channel2]
class is optional and can be one of the following: err, warn, fixme, or trace.  If class is not specified, all debugging messages for the specified channel are turned on.  Each channel will print messages about a particular component of Wine.  The following character can be either + or - to switch the specified channel on or off respectively.  If there is no class part before it, a leading + can be omitted. Note that spaces are not allowed anywhere in the string.
WINEDEBUG=warn+all will turn on all warning messages (recommended for debugging).
WINEDEBUG=warn+dll,+heap will turn on DLL warning messages and all heap messages.
WINEDEBUG=fixme-all,warn+cursor,+relay will turn off all FIXME messages, turn on cursor warning messages, and turn on all relay messages (API calls).
WINEDEBUG=relay will turn on all relay messages. For more control on including or excluding functions and dlls from the relay trace, look into the HKEY_CURRENT_USER\Software\Wine\Debug registry key.
For more information on debugging messages, see the Running Wine chapter of the Wine User Guide.
WINEDLLPATH Specifies the path(s) in which to search for builtin dlls and Winelib applications. This is a list of directories separated by ":". In addition to any directory specified in WINEDLLPATH, Wine will also look in /usr/lib32/wine.
WINEDLLOVERRIDES Defines the override type and load order of dlls used in the loading process for any dll. There are currently two types of libraries that can be loaded into a process address space: native windows dlls (native) and Wine internal dlls (builtin).  The type may be abbreviated with the first letter of the type (n or b). The library may also be disabled (''). Each sequence of orders must be separated by commas.
Each dll may have its own specific load order. The load order determines which version of the dll is attempted to be loaded into the address space. If the first fails, then the next is tried and so on. Multiple libraries with the same load order can be separated with commas. It is also possible to use specify different loadorders for different libraries by separating the entries by ";".
The load order for a 16-bit dll is always defined by the load order of the 32-bit dll that contains it (which can be identified by looking at the symbolic link of the 16-bit .dll.so file). For instance if ole32.dll is configured as builtin, storage.dll will be loaded as builtin too, since the 32-bit ole32.dll contains the 16-bit storage.dll.
WINEDLLOVERRIDES="comdlg32,shell32=n,b" Try to load comdlg32 and shell32 as native windows dll first and try the builtin version if the native load fails.
WINEDLLOVERRIDES="comdlg32,shell32=n;c:\\foo\\bar\\baz=b" Try to load the libraries comdlg32 and shell32 as native windows dlls. Furthermore, if an application request to load c:\foo\bar\baz.dll load the builtin library baz.
WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32=" Try to load comdlg32 as builtin first and try the native version if the builtin load fails; load shell32 always as builtin and comctl32 always as native; oleaut32 will be disabled.
WINEPATH Specifies additional path(s) to be prepended to the default Windows PATH environment variable. This is a list of Windows-style directories separated by ";".
For a permanent alternative, edit (create if needed) the PATH value under the HKEY_CURRENT_USER\Environment registry key.
WINEARCH Specifies the Windows architecture to support. It can be set either to win32 (support only 32-bit applications), or to win64 (support both 64-bit applications and 32-bit ones in WoW64 mode). The architecture supported by a given Wine prefix is set at prefix creation time and cannot be changed afterwards. When running with an existing prefix, Wine will refuse to start if WINEARCH doesn't match the prefix architecture.
DISPLAY Specifies the X11 display to use.
OSS sound driver configuration variables:
AUDIODEV Set the device for audio input / output. Default /dev/dsp.
MIXERDEV Set the device for mixer controls. Default /dev/mixer.
MIDIDEV Set the MIDI (sequencer) device. Default /dev/sequencer.
/usr/bin/wine The Wine program loader.
/usr/bin/wineconsole The Wine program loader for CUI (console) applications.
/usr/bin/wineserver The Wine server
/usr/bin/winedbg The Wine debugger
/usr/lib32/wine Directory containing Wine shared libraries