{ "mode": "man", "parameter": "XDVI", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/XDVI/1/json", "generated": "2026-10-10T01:53:35Z", "synopsis": "xdvi [+[page]] [--help] [-allowshell] [-altfont font] [-anchorposition anchor] [-bg color]\n[-browser WWWbrowser] [-copy] [-cr color] [-debug bitmask|string[,string ...]] [-display\nhost:display] [-dvipspath path] [-editor command] [-expert] [-expertmode flag] [-fg color]\n[-findstring string] [-font font] [-fullscreen ] [-gamma g] [-geometry geometry] [-gsalpha]\n[-gspalette palette] [-h] [-help] [-hl color] [-hush] [-hushbell] [-hushchars]\n[-hushchecksums] [-hushstdout] [-icongeometry geometry] [-iconic] [-install] [-interpreter\npath] [-keep] [-l] [-license] [-linkcolor color] [-linkstyle 0|1|2|3] [-margins dimen]\n[-mfmode mode-def[:dpi]] [-mgs[n] size] [-mousemode 0|1|2] [-nocolor] [-nofork]\n[-noghostscript] [-nogrey] [-nogssafer] [-noinstall] [-nomakepk] [-nomatchinverted]\n[-noomega] [-noscan] [-notempfile] [-notype1fonts] [-noxi2scrolling] [-offsets dimen] [-p\npixels] [-paper papertype] [-pause] [-pausespecial special-string] [-postscript flag]\n[-rulecolor color] [-rv] [-S density] [-s shrink] [-safer] [-sidemargin dimen]\n[-sourceposition line[:col][ ]filename] [-statusline] [-text-encoding encoding] [-thorough]\n[-topmargin dimen] [-unique] [-version] [-visitedlinkcolor color] [-warnspecials] [-watchfile\nsecs] [-wheelunit pixels] [-xoffset dimen] [-yoffset dimen] [dvifile]", "sections": { "NAME": { "content": "xdvi - DVI Previewer for the X Window System\n", "subsections": [] }, "SYNOPSIS": { "content": "xdvi [+[page]] [--help] [-allowshell] [-altfont font] [-anchorposition anchor] [-bg color]\n[-browser WWWbrowser] [-copy] [-cr color] [-debug bitmask|string[,string ...]] [-display\nhost:display] [-dvipspath path] [-editor command] [-expert] [-expertmode flag] [-fg color]\n[-findstring string] [-font font] [-fullscreen ] [-gamma g] [-geometry geometry] [-gsalpha]\n[-gspalette palette] [-h] [-help] [-hl color] [-hush] [-hushbell] [-hushchars]\n[-hushchecksums] [-hushstdout] [-icongeometry geometry] [-iconic] [-install] [-interpreter\npath] [-keep] [-l] [-license] [-linkcolor color] [-linkstyle 0|1|2|3] [-margins dimen]\n[-mfmode mode-def[:dpi]] [-mgs[n] size] [-mousemode 0|1|2] [-nocolor] [-nofork]\n[-noghostscript] [-nogrey] [-nogssafer] [-noinstall] [-nomakepk] [-nomatchinverted]\n[-noomega] [-noscan] [-notempfile] [-notype1fonts] [-noxi2scrolling] [-offsets dimen] [-p\npixels] [-paper papertype] [-pause] [-pausespecial special-string] [-postscript flag]\n[-rulecolor color] [-rv] [-S density] [-s shrink] [-safer] [-sidemargin dimen]\n[-sourceposition line[:col][ ]filename] [-statusline] [-text-encoding encoding] [-thorough]\n[-topmargin dimen] [-unique] [-version] [-visitedlinkcolor color] [-warnspecials] [-watchfile\nsecs] [-wheelunit pixels] [-xoffset dimen] [-yoffset dimen] [dvifile]\n", "subsections": [] }, "DESCRIPTION": { "content": "Xdvi is a program for previewing dvi files, as produced e.g. by the tex(1) program, under the\nX window system.\n\nXdvi can show the file shrunken by various integer factors, and it has a ``magnifying glass''\nfor viewing parts of the page enlarged (see the section MAGNIFIER below). This version of xd‐\nvi is also referred to as xdvik since it uses the kpathsea library to locate and generate\nfont files. In addition to that, it supports the following features:\n\n- hyperlinks in DVI files (section HYPERLINKS),\n\n- direct rendering of PostScript Type 1 fonts (section TYPE 1 FONTS),\n\n- source specials in the DVI file (section SOURCE SPECIALS),\n\n- string search in DVI files (section STRING SEARCH),\n\n- saving or printing (parts of) the DVI file (sections PRINT DIALOG and SAVE DIALOG).\n\nXdvi can be compiled with the Motif toolkit or the Xaw (Athena) toolkit (and variants of it),\nand the Motif version has a slightly different GUI; these differences are noted below.\n\nBefore displaying a page of a DVI file, xdvi will check to see if the file has changed since\nthe last time it was displayed. If this is the case, it will reload the file. This feature\nallows you to preview many versions of the same file while running xdvi only once. Since it\ncannot read partial DVI files, xdvik versions starting from 22.74.3 will create a temporary\ncopy of the DVI file being viewed, to ensure that the file can be viewed without interrup‐\ntions. (The -notempfile can be used to turn off this feature).\n\nXdvi can show PostScript specials by any of three methods. It will try first to use Dis‐\nplay PostScript, then NeWS, then it will try to use Ghostscript to render the images.\nAll of these options depend on additional software to work properly; moreover, some of them\nmay not be compiled into this copy of xdvi.\n\nFor performance reasons, xdvi does not render PostScript specials in the magnifying glass.\n\nIf no file name has been specified on the command line, xdvi will try to open the most re‐\ncently opened file; if the file history (accessible via the File > Open Recent menu) is emp‐\nty, or if none of the files in the history are valid DVI files, it will pop up a file selec‐\ntor for choosing a file name. (In previous versions, which didn't have a file history, the\nfile selector was always used; you can set the X resource noFileArgUseHistory to false to get\nback the old behaviour.)\n", "subsections": [] }, "OPTIONS": { "content": "In addition to specifying the dvi file (with or without the .dvi extension), xdvi supports\nthe following command line options. If the option begins with a `+' instead of a `-', the\noption is restored to its default value. By default, these options can be set via the re‐\nsource names given in parentheses in the description of each option.\n\n+page Specifies the first page to show. If + is given without a number, the last page is\nassumed; the first page is the default.\n", "subsections": [ { "name": "-allowshell", "content": "(.allowShell) This option enables the shell escape in PostScript specials. (For secu‐\nrity reasons, shell escapes are disabled by default.) This option should be rarely\nused; in particular it should not be used just to uncompress files: that function is\ndone automatically if the file name ends in .Z, .gz, or .bz2. Shell escapes are al‐\nways turned off if the -safer option is used.\n" }, { "name": "-altfont _", "content": "(.altFont) Declares a default font to use when the font in the dvi file cannot be\nfound. This is useful, for example, with PostScript fonts.\n" }, { "name": "-anchorposition _", "content": "Jump to anchor after opening the DVI file. This is only useful when invoking xdvi from\nother applications.\n" }, { "name": "-background _", "content": "(.background) Determines the color of the background. Same as -bg.\n" }, { "name": "-bg _", "content": "(.background) Determines the color of the background.\n" }, { "name": "-browser _", "content": "(.wwwBrowser) Defines the web browser used for handling external URLs. The value of\nthis option or resource has the same syntax as the BROWSER environment variable; see\nthe explanation of that variable in the section `ENVIRONMENT' below for a detailed de‐\nscription. If neither the option nor the X resource wwwBrowser is specified, the en‐\nvironment variables BROWSER and WWWBROWSER (in that order) are used to determine the\nbrowser command. If these are not set either, the following default value is used:\nxdg-open %s:htmlview %s:firefox -remote -remote \"openURL(%s,new-window)\":mozilla -re‐\nmote \"openURL(%s,new-window)\":netscape -raise -remote \"openURL(%s,new-window)\":xterm\n-e w3m %s:xterm -e lynx %s:xterm -e wget %s\n" }, { "name": "-copy", "content": "option may be necessary for correct operation on a color display, but overstrike char‐\nacters will be incorrect. If greyscale anti-aliasing is in use, the -copy operation\nwill disable the use of colorplanes and make overstrikes come out incorrectly. See\nalso -thorough.\n" }, { "name": "-cr _", "content": "(.cursorColor) Determines the color of the mouse cursor. The default is the same as\nthe foreground color.\n" }, { "name": "-debug _", "content": "(.debugLevel) If nonzero, prints additional information on standard output. The argu‐\nment can be either a bitmask specified as a decimal number, or comma-separated list of\nstrings.\nFor the bitmask representation, multiple values can be specified by adding the numbers\nthat represent the individual bits; e.g. to debug all file searching and opening com‐\nmands, use 4032 (= 2048 + 1024 + 512 + 256 + 128 + 64). Use -1 to turn on debugging of\neverything (this will produce huge output).\nFor the string representation, use the strings listed in the following table, with a\ncomma to separate the values; e.g. to debug all file searching and opening commands,\nuse search,expand,paths,hash,stat,open. (The option `kpathsea' is provided as a\nshorthand for these.) Note that such a list may need to be quoted to prevent the\nshell from interpreting commas or spaces in the list.\nThe individual numbers and strings have the following meanings:\n\n1 bitmap Bitmap creation\n2 dvi DVI translation\n4 pk PK fonts\n8 batch Batch mode: Exit after\nreading the DVI file\n16 event Event handling\n32 ps PostScript interpreter calls\n64 stat Kpathsea stat(2) calls\n128 hash Kpathsea hash table lookups\n256 open Kpathsea file opening\n512 paths Kpathsea path definitions\n1024 expand Kpathsea path expansion\n2048 search Kpathsea searching\n4032 kpathsea All Kpathsea options\n4096 htex Hypertex specials\n8192 src Source specials\n16384 client Client/server mode (see -unique\nand -sourceposition options)\n32768 ft FreeType library messages (Type 1 fonts)\n65536 ftverbose Verbose FreeType library messages (currently unused)\n131072 gui GUI elements\n262144 find Searching for strings in the DVI file\n524288 files File history and opening DVI files\n\nSome of the Kpathsea debugging options are actually provided by Kpathsea; see the De‐\nbugging section in the Kpathsea manual for more information on these.\n" }, { "name": "-density _", "content": "(.densityPercent) Determines the density used when shrinking bitmaps for fonts. A\nhigher value produces a lighter font. The default value is 40. If greyscaling is in\nuse, this argument does not apply; use -gamma instead. See also the `S' keystroke.\nSame as -S.\n" }, { "name": "-display _", "content": "Specifies the host and screen to be used for displaying the dvi file. By default this\nis obtained from the environment variable DISPLAY.\n" }, { "name": "-dvipspath _", "content": "(.dvipsPath) Use path as the dvips program to use when printing. The default for this\nis dvips. The program or script should read the DVI file from standard input, and\nwrite the PostScript file to standard output.\n" }, { "name": "-editor _", "content": "(.editor) Specifies the editor that will be invoked when the source-special() action\nis triggered to start a reverse search (by default via Ctrl-Mouse 1). The argument to\nthis option is a format string in which occurrences of ``%f'' are replaced by the file\nname, occurrences of ``%l'' are replaced by the line number within the file, and op‐\ntional occurrences of ``%c'' are replaced by the column number within the line.\n\nIf neither the option nor the X resource .editor is specified, the following environ‐\nment variables are checked to determine the editor command: XEDITOR, VISUAL, and EDI‐\nTOR (in this sequence). If the string is found as the value of the VISUAL or EDITOR\nenvironment variables, then ``xterm -e '' is prepended to the string; if the editor is\nspecified by other means, then it must be in the form of a shell command to pop up an\nX window with an editor in it. If none of these variables is set, a warning message is\ndisplayed and the command ``xterm -e vi +%l %f'' is used.\n\nIf no ``%f'' or ``%l'' occurs in the string, the missing format strings are appended\nautomatically. (This is for compatibility with other programs when using one of the\nenvironment variables).\n\nA new instance of the editor is started each time this command is used; therefore it\nis preferable to use an editor that can be invoked in `client' mode to load new files\ninto the same instance. Example settings are:\n\nemacsclient --no-wait\n(older Emacsen)\n\ngnuclient -q\n(XEmacs and newer Emacsen)\n\ngvim --servername xdvi --remote\n(VIM v6.0+; the `--servername xdvi' option will cause gvim to run a dedicated\ninstance for the files opened by xdvi.)\n" }, { "name": "nc (nedit)", "content": "Note that those strings need to be enclosed into quotes when using them on the com‐\nmand-line to protect them from the shell; when using them as argument for the .editor\nresource in an X resource file, no quotes should be used.\n\nNOTE ON SECURITY: The argument of this option isn't executed as a shell command, but\nvia exec() to prevent evil tricks with the contents of source specials.\n" }, { "name": "-expert", "content": "This option is only supported for backwards compatibility; it is equivalent to -ex‐\npertmode 0, which should be preferred.\n" }, { "name": "-expertmode _", "content": "(.expertMode) With an argument of 0, this option switches off the display of the but‐\ntons, scrollbars, the toolbar (Motif only), the statusline and the page list. These\nGUI elements can also be (de)activated separately, by combining the appropriate values\nin the flag argument. This acts similar to the -debug option: The integer flag is\ntreated as a bitmap where each bit represents one element. If the bit has the value 1,\nthe element is switched on, if it has the value 0, the element is switched off. The\nmeaning of the bits is as follows:\n\n1 statusline\n2 scrollbars\n4 Motif: pagelist, Xaw: buttons and pagelist\n8 toolbar (Motif only)\n16 menubar (Motif only)\n\nFor example, to turn on only the statusline and the scrollbars, use 3 (= 1 + 2). See\nalso the `x' keystroke, where the bits are addressed by their positions, from 1 to 3\n(Xaw) or 5 (Motif), respectively.\n\nIf the statusline is not active, all messages that would normally be printed to the sta‐\ntusline will be printed to stdout, unless the -hushstdout option is used.\n" }, { "name": "-fg _", "content": "(.foreground) Determines the color of the text (foreground).\n" }, { "name": "-findstring _", "content": "This option triggers a search for string in the DVI file mentioned on the command-\nline, similar to forward search (see the description of the sourceposition option): If\nthere is already another instance of xdvi running on the displaying that DVI file, it\nwill cause that instance to perform the search instead. The search starts at the top\nof the current page of the DVI file.\n" }, { "name": "-font _", "content": "(*font) Sets the font used in menus, buttons etc., as described in the X(7x) man page.\nThe font for child windows can be set separately, e.g.:\n\nxdvi*statusline*font: \\\n-*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*\n\n" }, { "name": "-foreground _", "content": "Same as -fg.\n" }, { "name": "-fullscreen", "content": "When this option is used, xdvi will (try to) run in fullscreen mode, with no window\ndecorations. This option is not guaranteed to work with all windowmanagers/desktops;\nif you're experiencing problems with it, please use the -geometry option instead, and\na suitable window manager setting to remove the window decorations. When using this\noption for presentations, you might want to get rid of all the control widgets as\nwell, using the -expertmode option. This option can also be toggled at runtime using\nthe fullscreen action (by default bound to Ctrl-l).\n" }, { "name": "-gamma _", "content": "(.gamma) Controls the interpolation of colors in the greyscale anti-aliasing color\npalette. Default value is 1.0. For 0 < gamma < 1, the fonts will be lighter (more\nlike the background), and for gamma > 1, the fonts will be darker (more like the fore‐\nground). Negative values behave the same way, but use a slightly different algorithm.\nFor color and grayscale displays; for monochrome, see -density. See also the `S' key‐\nstroke.\n" }, { "name": "-geometry _", "content": "(.geometry) Specifies the initial geometry of the main window, as described in the\nX(7x) man page. The geometry of child windows can be set separately, e.g.:\nxdvi*helpwindow.geometry: 600x800\n" }, { "name": "-gsalpha", "content": "(.gsAlpha) Causes Ghostscript to be called with the x11alpha driver instead of the x11\ndriver. The x11alpha driver enables anti-aliasing in PostScript specials, for a nicer\nappearance. It is available on newer versions of Ghostscript. This option can also\nbe toggled with the `V' keystroke.\n" }, { "name": "-gspalette _", "content": "(.palette) Specifies the palette to be used when using Ghostscript for rendering Post‐\nScript specials. Possible values are Color, Greyscale, and Monochrome. The default\nis Color.\n" }, { "name": "-h -help --help", "content": "Prints a short help text with an overview of the command-line options to standard out‐\nput.\n", "flag": "-h", "long": "--help" }, { "name": "-hl _", "content": "(.highlight) Determines the color of the page border, of the ruler in `ruler mode',\nand of the highlighting markers in forward search and string search. The default is\nthe foreground color.\n" }, { "name": "-hush", "content": "" }, { "name": "-hushbell", "content": "(.hushBell) Don't sound the X bell when an error occurs.\n" }, { "name": "-hushchars", "content": "(.hushLostChars) Causes xdvi to suppress warnings about references to characters which\nare not defined in the font.\n" }, { "name": "-hushchecksums", "content": "(.hushChecksums) Causes xdvi to suppress warnings about checksum mismatches between\nthe dvi file and the font file.\n" }, { "name": "-hushstdout", "content": "(.hushStdout) Suppresses printing of status messages to stdout. Note that errors or\nwarnings will still be printed to stderr even if this option is used.\n" }, { "name": "-icongeometry _", "content": "(.iconGeometry) Specifies the initial position for the icon.\n" }, { "name": "-iconic", "content": "(.iconic) Causes the xdvi window to start in the iconic state. The default is to\nstart with the window open.\n" }, { "name": "-install", "content": "(.install) If xdvi is running under a PseudoColor visual, then (by default) it will\ncheck for TrueColor visuals with more bits per pixel, and switch to such a visual if\none exists. If no such visual exists, it will use the current visual and colormap.\nIf -install is selected, however, it will still use a TrueColor visual with a greater\ndepth, if one is available; otherwise, it will install its own colormap on the current\nvisual. If the current visual is not PseudoColor, then xdvi will not switch the visu‐\nal or colormap, regardless of its options. The default value of the install resource\nis the special value, maybe. There is no +install option. See also -noinstall, and\nthe GREYSCALING AND COLORMAPS section.\n" }, { "name": "-interpreter _", "content": "(.interpreter) Use filename as the Ghostscript interpreter. By default it uses gs.\n" }, { "name": "-keep", "content": "when moving to a new page. See also the `k' keystroke. This flag is honored by all\npage switching actions and by up-or-previous() / down-or-next(), although the latter\nonly honor the horizontal position, not the vertical one. This allows for a \"continu‐\nous\" scrolling back an forth through a document with a display window narrower than a\npage width.\n" }, { "name": "-l", "content": "", "flag": "-l" }, { "name": "-license", "content": "Prints licensing information.\n" }, { "name": "-linkcolor", "content": "(.linkColor) Color used for unvisited hyperlinks (`Blue2' by default). Hyperlinks are\nunvisited before you click on them, or after the DVI file has been reloaded. The val‐\nue should be either a valid X color name (such as DarkGoldenrod4) or a hexadecimal\ncolor string (such as #8b6508). See also -visitedlinkcolor and -linkstyle.\n" }, { "name": "-linkstyle", "content": "(.LinkStyle) Determines the style in which hyperlinks are displayed. Possible values\nand their meanings are:\n\n0 No highlighting of links\n1 Underline links with link color\n2 No underlining, color text with link color\n3 Underline and display text colored with\nlink color\n\nThe values for link color are specified by the options/resources -linkcolor and -vis‐\nitedlinkcolor (which see).\n" }, { "name": "-margins _", "content": "(.Margin) Specifies the size of both the top margin and side margin. This determines\nthe ``home'' position of the page within the window as follows. If the entire page\nfits in the window, then the margin settings are ignored. If, even after removing the\nmargins from the left, right, top, and bottom, the page still cannot fit in the win‐\ndow, then the page is put in the window such that the top and left margins are hidden,\nand presumably the upper left-hand corner of the text on the page will be in the upper\nleft-hand corner of the window. Otherwise, the text is centered in the window. The\ndimension should be a decimal number optionally followed by any of the two-letter ab‐\nbreviations for units accepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By de‐\nfault, the unit will be cm (centimeters). See also -sidemargin, -topmargin, and the\nkeystroke `M.'\n" }, { "name": "-mfmode _", "content": "(.mfMode) Specifies a mode-def string, which can be used in searching for fonts (see\nENVIRONMENT, below). Generally, when changing the mode-def, it is also necessary to\nchange the font size to the appropriate value for that mode. This is done by adding a\ncolon and the value in dots per inch; for example, -mfmode ljfour:600. This method\noverrides any value given by the pixelsPerInch resource or the -p command-line argu‐\nment. The metafont mode is also passed to metafont during automatic creation of\nfonts. By default, it is unspecified.\n" }, { "name": "-mgs _", "content": "Same as -mgs1.\n" }, { "name": "-mgs[_", "content": "(.magnifierSize[n]) Specifies the size of the window to be used for the ``magnifying\nglass'' for Button n. The size may be given as an integer (indicating that the magni‐\nfying glass is to be square), or it may be given in the form widthxheight. See the\nMOUSE ACTIONS section. Defaults are 200x150, 400x250, 700x500, 1000x800, and\n1200x1200.\n" }, { "name": "-mousemode [_", "content": "(.mouseMode) Specifies the default mode of xdvi at startup: Magnifier (0), Text Selec‐\ntion Mode (1) or Ruler Mode (2). See the section MODES, below, for more information.\n" }, { "name": "-nocolor", "content": "(.color) Turns off the use of color specials. This option can be toggled with the `C'\nkeystroke. (Note: -nocolor corresponds to color:off; +nocolor to color:on.)\n" }, { "name": "-nofork", "content": "(.fork) With the -sourceposition and -unique options, the default behavior is for xdvi\nto put itself into the background (like a daemon) if there is no appropriate instance\nof xdvi already running. This argument makes it run in the foreground instead. This\nis useful for debugging, or if your client application cannot deal well with a program\nself-backgrounding itself in this way -- e.g. the IPC functions in emacs are known to\nhave problems with this. If no -sourceposition or -unique argument is given, then\nthis option has no effect. (Note: -nofork corresponds to fork:off; +nofork to\nfork:on.)\n" }, { "name": "-noghostscript", "content": "(.ghostscript) Inhibits the use of Ghostscript for displaying PostScript specials.\n(Note: -noghostscript corresponds to ghostscript:off; +noghostscript to ghost‐\nscript:on.)\n" }, { "name": "-nogrey", "content": "(.grey) Turns off the use of greyscale anti-aliasing when printing shrunken bitmaps.\n(Note: -nogrey corresponds to grey:off; +nogrey to grey:on.) See also the `G' key‐\nstroke.\n" }, { "name": "-nogssafer", "content": "(.gsSafer) Normally, if Ghostscript is used to render PostScript specials, the Ghost‐\nscript interpreter is run with the option -dSAFER. The -nogssafer option runs Ghost‐\nscript without -dSAFER. The -dSAFER option in Ghostscript disables PostScript opera‐\ntors such as deletefile, to prevent possibly malicious PostScript programs from having\nany effect. If the -safer option is specified, then this option has no effect; in\nthat case Ghostscript is always run with -dSAFER. (Note: -nogssafer corresponds to\ngsSafer:off; +nogssafer to gsSafer:on.)\n" }, { "name": "-noinstall", "content": "(.install) Inhibit the default behavior of switching to a TrueColor visual if one is\navailable with more bits per pixel than the current visual. (Note: -noinstall corre‐\nsponds install:off; there is no +noinstall option.) See also -install, and the\nGREYSCALING AND COLORMAPS section.\n" }, { "name": "-nomakepk", "content": "(.makePk) Turns off automatic generation of font files that cannot be found by other\nmeans. (Note: -nomakepk corresponds to makePk:off; +nomakepk to makePK:on.)\n" }, { "name": "-nomatchinverted", "content": "(.matchInverted) Don't highlight string search matches in inverted color; instead,\ndraw a rectangle in highlight color (see the -hl option) around the match. This option\nis activated automatically if the display isn't running in TrueColor. (Note: -no‐\nmatchinverted corresponds to matchInverted:off; +nomatchinverted to matchInverted:on.)\n" }, { "name": "-noomega", "content": "(.omega) This will disable the use of Omega extensions when interpreting DVI files.\nBy default, the additional opcodes 129 and 134 are recognized by xdvi as Omega exten‐\nsions and interpreted as requests to set 2-byte characters. The only drawback is that\nthe virtual font array will require 65536 positions instead of the default 256 posi‐\ntions, i.e. the memory requirements of xdvi will be slightly larger. If you find this\nunacceptable or encounter another problem with the Omega extensions, you can switch\nthis extension off by using -noomega (but please do send a bug report if you find such\nproblems - see the bug address in the AUTHORS section below).\n(Note: -noomega corresponds to omega: off; +noomega to omega: on.)\n" }, { "name": "-noscan", "content": "(.prescan) By default, xdvi does a preliminary scan of the dvi file to process any pa‐\npersize specials; this is especially important at startup since the paper size may be\nneeded to determine the window size. If PostScript is in use, then prescanning is\nalso necessary in order to properly process header files. In addition, prescanning is\nneeded to correctly determine the background color of a page. This option turns off\nsuch prescanning. (Prescanning will be automatically be turned back on if xdvi de‐\ntects any of the specials mentioned above.) (Note: -noscan corresponds to pres‐\ncan:off; +noscan to prescan:on.)\n" }, { "name": "-notempfile", "content": "(.tempFile) As mentioned in the section DESCRIPTION above, xdvi will create a tempo‐\nrary copy of the DVI file so that it can be accessed without interruptions even while\nthe file is being rewritten by TeX. Since this introduces the overhead of copying the\nfile every time it has changed, the -notempfile allows you to turn off this behaviour.\nIn this case, exposing parts of the window while the DVI file is being written by TeX\nwill erase the current window contents until the DVI file can be completely reread.\n(Note: -notempfile corresponds to tempFile:off; +notempfile to tempFile:on.)\n" }, { "name": "-notype1fonts", "content": "(.type1) This will disable the use of the FreeType library to display PostScript\nType 1 fonts. Use this option as a workaround when you encounter problems with the\ndisplay of Type 1 fonts (but please don't forget to send a bug report in this case, to\nthe URL mentioned in the section AUTHORS below).\n(Note: -notype1fonts corresponds to type1:off; +notype1fonts to type1:on.)\n" }, { "name": "-noxi2scrolling", "content": "(.xi2Scrolling) This will disable the use of high-resolution scrolling using the XIn‐\nput 2.1 features of the X Server. When enabled, horizontal and vertical scrolling is\ndone in smaller increments than would correspond to a single click of a mouse wheel.\nThis is only available for hardware that supports the feature, generally touchpads.\nIt is not available for traditional wheel mice. If suitable hardware is not present\nor if the X server does not support XInput 2.1 or higher, then the high-resolution\nscrolling feature is turned off and has no effect.\n(Note: -noxi2scrolling corresponds to xi2Scrolling:off; +noxi2scrolling, to\nxi2Scrolling:on.)\n" }, { "name": "-offsets _", "content": "(.Offset) Specifies the size of both the horizontal and vertical offsets of the output\non the page. By decree of the Stanford TeX Project, the default TeX page origin is\nalways 1 inch over and down from the top-left page corner, even when non-American pa‐\nper sizes are used. Therefore, the default offsets are 1.0 inch. The argument dimen\nshould be a decimal number optionally followed by any of the two-letter abbreviations\nfor units accepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By default, the\nunit will be cm (centimeters). See also -xoffset and -yoffset.\n" }, { "name": "-p _", "content": "(.pixelsPerInch) Defines the size of the fonts to use, in pixels per inch. The de‐\nfault value is 600. This option is provided only for backwards compatibility; the\npreferred way is to set both the resolution and the Metafont mode via the -mfmode op‐\ntion (which see).\n", "flag": "-p" }, { "name": "-paper _", "content": "(.paper) Specifies the size of the printed page. Note that in most cases it's best to\nspecify the paper size in the TeX input file via the line\n\n\\usepackage[dvips]{geometry}\n\nwhich will be recognized by both dvips and xdvi; in that case the use of a `-paper'\noption should be unnecessary.\nThe paper size may be specified in the form widthxheight optionally followed by a\nunit, where width and height are decimal numbers giving the width and height of the\npaper, respectively, and the unit is any of the two-letter abbreviations for units ac‐\ncepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By default, the unit is cm\n(centimeters).\nThere are also synonyms which may be used: us (8.5x11in), legal (8.5x14in), foolscap\n(13.5x17in), as well as the ISO sizes a1-a7, b1-b7, c1-c7. Each of these also has a\nlandscape or `rotated' variant: usr (11x8.5in), a1r-a7r, etc. For compatibility with\ndvips, the formats letter (8.5x11in), ledger (17x11in) and tabloid (11x17in) are also\nsupported (these don't have rotated variants).\nAny of the above sizes may be preceded by a plus sign (`+'); this causes the paper\nsize given here to override any paper size given in the dvi file. The default paper\nsize is 21 x 29.7 cm (A4 size).\n" }, { "name": "-pause", "content": "play, which can be used for presentations. When this option is used, xdvi will pause\nthe display of the current page whenever it encounters a special special-string (xd‐\nvi:pause by default; the string can be customized via -pausespecial, see below), and\nthe cursor will change its shape. The action unpause-or-next() (by default bound to\nthe Space key) will display the next portion of the page up to the following special-\nstring, or until the end of the page is reached. When the option is not used, spe‐\ncials containing special-string will be ignored.\n" }, { "name": "-pausespecial _", "content": "(.pauseSpecial) Sets the special string that causes xdvi to pause when the -pause op‐\ntion is active. The default value of special-string is xdvi:pause.\n" }, { "name": "-postscript _", "content": "(.postscript) If flag = 0, rendering of PostScript specials is disabled; instead,\nbounding boxes will be displayed (if available). A value of 1 (the default) switches\nPostScript specials on. With a value of 2, the PostScript specials are dis‐\nplayed along with their bounding boxes; this allows you to visually check the correct‐\nness of the bounding boxes. The values can also be toggled at runtime with the `v'\nkeystroke and the corresponding numerical prefix arguments 0, 1 and 2.\n" }, { "name": "-ps2pdfpath _", "content": "(.ps2pdfPath) Use path as a conversion program from PostScript to PDF. The program or\nscript should accept two command-line arguments: The PostScript file as first argu‐\nment, and the PDF output file as second argument.\n" }, { "name": "-rulecolor _", "content": "(.ruleColor) Determines the color of the rules used for the magnifier (default: fore‐\nground color).\n" }, { "name": "-q", "content": "and don't write it at exit). This forces the defaults defined in $HOME/.Xdefaults to\nbe used. See FILES for more information on $HOME/.xdvirc.\n", "flag": "-q" }, { "name": "-rv", "content": "ground, instead of vice versa.\n" }, { "name": "-S _", "content": "(.densityPercent) Same as -density (which see).\n", "flag": "-S" }, { "name": "-s _", "content": "(.shrinkFactor) Defines the initial shrink factor. The default value is 8. If shrink\nis given as 0, then the initial shrink factor is computed so that the page fits within\nthe window (as if the `s' keystroke were given without a number).\n", "flag": "-s" }, { "name": "-safer", "content": "when xdvi is called by a browser that obtains a dvi or TeX file from another site.\nThis option selects +nogssafer and +allowshell.\n" }, { "name": "-sidemargin _", "content": "(.sideMargin) Specifies the side margin (see -margins).\n" }, { "name": "-sourceposition _", "content": "This option makes xdvi search in the dvi file for the place corresponding to the indi‐\ncated line (and, optionally, column) in the .tex source file, and highlight the place\nfound by drawing a rectangle in the highlight color (see the -hl option) around the\ncorresponding text. In addition, when run with this argument (and the -nofork option\nis not given, which see), xdvi will always return immediately: if it finds another\ninstance of xdvi already showing dvifile, then it will cause that instance to raise\nits window and move to the given place in the dvi file; otherwise it will start up its\nown instance in the background. If several instances of xdvi are displaying the re‐\nspective dvi file, the instance which was last raised to the foreground will be used.\n\nThe space before filename is only needed if the filename starts with a digit. When\nthe space is used, the argument needs to be enclosed in quotes to prevent the shell\nfrom misinterpreting the space as argument separator.\n\nThis option requires that dvifile be prepared with source special information. See\nthe section on SOURCE SPECIALS for details on how to do this.\n\nHere is a more detailed description of how the filename in the -sourceposition argu‐\nment is matched with the filename in the source specials:\n\n1. If neither of the filenames contains a path name component, the filenames are com‐\npared ignoring the `.tex' extensions in both filenames.\n\n2. Otherwise, if one of the filenames does contain a path component (e.g.: ./test.tex,\n../test.tex, /my/homedir/tex/test.tex or any combination of these), both filenames\nare expanded to a full path, with any occurrences of ../ and ./ expanded, and mul‐\ntiple slashes removed.\nThe pathname in the -sourceposition is expanded relative to the current working di‐\nrectory of the xdvi -sourceposition invocation, and the pathnames in the source\nspecials are expanded relative to the path of the current DVI file being viewed.\nThe path names are then compared ignoring the `.tex' extensions in both path names.\n" }, { "name": "-statusline", "content": "(.statusline) This option is obsolete; use -expertmode flag instead (which see).\n" }, { "name": "-text-encoding _", "content": "(.textEncoding) Use encoding as the text encoding of the string in the \"Find\" window.\nUsually, this should not be needed since the encoding is determined from the locale\nsettings.\n" }, { "name": "-thorough", "content": "(.thorough) Xdvi will usually try to ensure that overstrike characters (e.g. \\notin)\nare printed correctly. On monochrome displays, this is always possible with one logi‐\ncal operation, either and or or. On color displays, however, this may take two opera‐\ntions, one to set the appropriate bits and one to clear other bits. If this is the\ncase, then by default xdvi will instead use the copy operation, which does not handle\noverstriking correctly. The -thorough option chooses the slower but more correct\nchoice. See also -copy.\n" }, { "name": "-topmargin _", "content": "(.topMargin) Specifies the top and bottom margins (see -margins).\n" }, { "name": "-unique", "content": "(.unique) This option will make another instance of xdvi running on the same display\nact as a `server'. For example, the invocation\n\nxdvi -unique +5 file.dvi\n\nwill cause this other instance to load file.dvi on page 5 in place of the file that it\nis currently displaying. If there is already another instance of xdvi already display‐\ning the file file.dvi, then it will just jump to page 5. If the other instance of xd‐\nvi is displaying a different file, it will load file.dvi instead. Otherwise, if no\nother instance of xdvi is currently running on the display, this option instead starts\na new instance of xdvi in the background (unless the -nofork option is specified,\nwhich see) displaying page 5 of file.dvi.\nThe filename and the +n option for the page number are the only options available for\ncontrolling a remote instance of xdvi like this; all other options are currently ig‐\nnored.\n" }, { "name": "-useTeXpages", "content": "Use logical TeX pages (the values of the \\count0 register) instead of physical pages\nfor the pagelist labels and when jumping to a page in a document with the `g' key‐\nstroke (or the goto-page() action). This option can be toggled via the `T' keystroke.\n" }, { "name": "-version", "content": "Print information on the version of xdvi.\n" }, { "name": "-visitedlinkcolor", "content": "(.visitedLinkColor) Color used for visited hyperlinks (`Purple4' by default). Hyper‐\nlinks become visited once you click on them. As for linkColor, the value should be ei‐\nther a valid X color name or a hexadecimal color string.\n" }, { "name": "-warnspecials", "content": "(.warnSpecials) Causes xdvi to print warnings about \\special strings that it cannot\nprocess to stderr. These warnings are suppressed by default.\n" }, { "name": "-watchfile _", "content": "(.watchFile) If this option is set to a value larger than 0, xdvi will check the DVI\nfile for changes every n seconds. If the DVI file has been completely written by TeX,\nit will be reloaded automatically. Fractional values (e.g. `2.5') are possible. The\ndefault for this option is 0, i.e. no watching.\nSince xdvi cannot handle partial DVI files, it tries not to reload the file while it\nis being rewritten. However, use of the magnifier or switching of pages requires\nreading (a part of) the DVI file, and if the tempfile option is switched off, this\nwill erase the current contents of the window until the DVI file can be read entirely.\n" }, { "name": "-wheelunit _", "content": "(.wheelUnit) Sets the number of pixels that a motion of a wheel mouse will move the\nimage up, down, left, or right. (See the wheel and hwheel actions, below, for more in‐\nformation on this.) If set to zero, the wheel mouse functionality is (essentially)\ndisabled. The default value is 80.\n" }, { "name": "-xoffset _", "content": "(.xOffset) Specifies the size of the horizontal offset of the output on the page. See\n-offsets.\n" }, { "name": "-yoffset _", "content": "(.yOffset) Specifies the size of the vertical offset of the output on the page. See\n-offsets.\n" } ] }, "KEYSTROKES": { "content": "Xdvi recognizes the following keystrokes when typed in its window. Each may optionally be\npreceded by a (positive or negative) number, a `prefix argument', whose interpretation will\ndepend on the particular keystroke. This prefix argument can be discarded by pressing the\n``Escape'' key. If present, the ``Help'', ``Prior'' and ``Next'' keys are synonyms for `?',\n`b', and `f' keys, respectively.\n\nThe key bindings listed here are those that xdvi assigns by default. The names appearing in\nbrackets at the beginning of the descriptions are the names of the actions associated with\nthe keys; these can be used to customize the key bindings, as explained in more detail in the\nsection CUSTOMIZATION below. If only a lowercase binding is listed, both upper- and lowercase\nkeys will work for that binding.\n\nESC key\n[discard-number()] The escape key discards the numerical prefix for all actions (use‐\nful when you mistyped a number).\n\nReturn key\n[forward-page()] Moves to the next page (or to the nth next page if a number is giv‐\nen). Synonyms are `n', `f' and Line Feed.\n\nBackspace key\n[back-page()] Moves to the previous page (or back n pages). Synonyms are `p', `b' and\nCtrl-h.\n\nDelete key\n[up-or-previous()] Moves up two-thirds of a window-full, or to the top of the previous\npage if already at the top of the page. With a float argument, moves up the corre‐\nsponding fraction of a window-full.\n\nSpace key\n[unpause-or-next()] Moves down two-thirds of a window-full, or to the next page if al‐\nready at the bottom of the page.\nWhen the option -pause special-string is used and the display is currently paused,\nthis key will instead display the next portion of the page until the next special-\nstring or the end of the page is encountered. See the description of the -pause op‐\ntion for details. The action [down-or-next()] does a similar thing, but without paus‐\ning; it is not bound to a key by default.\n\nCtrl-Home (Xaw), Ctrl-osfBeginLine (Motif)\n[goto-page(1)] Moves to the first page of the document.\n\nCtrl-End (Xaw), Ctrl-osfEndLine (Motif)\n[goto-page()] Moves to the last page of the document.\n\nHome (Xaw), osfBeginLine (Motif)\n[home-or-top()] Move to the ``home'' position of the page, or to the top of the page\nif the keep flag is set (in this case, the page doesn't scroll horizontally).\n\nEnd (Xaw), osfEndLine (Motif)\n[end-or-bottom()] Move to the ``end'' position of the page (the lower right-hand cor‐\nner), or to the bottom of the page if the keep flag is set (in this case, the page\ndoesn't scroll horizontally).\n", "subsections": [ { "name": "Down arrow", "content": "[down(0.015)] Scrolls page down.\n" }, { "name": "Up arrow", "content": "[up(0.015)] Scrolls page up.\n" }, { "name": "Right arrow", "content": "[right(0.015)] Scrolls page right.\n" }, { "name": "Left arrow", "content": "[left(0.015)] Scrolls page left.\n" }, { "name": "Alt-Ctrl-+", "content": "[change-density(25)] Increase the darkness of the fonts in the DVI window by adding to\nthe gamma value (see also the `S' keystroke).\n" }, { "name": "Alt-Ctrl--", "content": "[change-density(-25)] Decrease the darkness of the fonts in the DVI window by sub‐\ntracting from the gamma value (see also the `S' keystroke).\n\nCtrl-+ [set-shrink-factor(+)] Increase the shrink factor (see also the `s' keystroke).\n\nCtrl-- [set-shrink-factor(-)] Decrease the shrink factor (see also the `s' keystroke).\n\nCtr-[ [pagehistory-delete-backward()] Delete the current item in the page history and move\nto the history item before the deleted one. With a prefix argument n, delete n previ‐\nous history items. See PAGE HISTORY for details.\n\n[ [pagehistory-back()] Move back in the page history (see PAGE HISTORY for details).\nWith a prefix argument n, move back n history items.\n\nCtr-] [pagehistory-delete-forward()] Delete the current item in the page history and move to\nthe history item after the deleted one. With a prefix argument n, delete n next histo‐\nry items. See PAGE HISTORY for details.\n\n] [pagehistory-forward()] Move forward in the page history (see PAGE HISTORY for de‐\ntails). With a prefix argument n, move forward n history items.\n\n^ [home()] Move to the ``home'' position of the page. This is normally the upper left-\nhand corner of the page, depending on the margins as described in the -margins option,\nabove.\n\n? [help()] Same as the h key (which see).\n\nB [htex-back()] This key jumps back to the previous hyperlink anchor. See the section\nHYPERLINKS for more information on navigating the links.\n\nb [back-page()] Moves to the previous page (or back n pages). Synonyms are `p', Ctrl-h\nand Backspace.\n\nC [set-color()] This key toggles the use of color specials. The key sequences `0C' and\n`1C' turn interpretation of color specials off and on, respectively. See also the\n-nocolor option.\n\nc [center()] Moves the page so that the point currently beneath the mouse cursor is\nmoved to the middle of the window, and warps the mouse cursor to the same place.\n\nD [toggle-grid-mode()] This key toggles the use of a grid on the displayed page. If no\nnumber is given, the grid mode is switched on or off. By prepending a number from 1\nto 3, 3 different grid levels can be set. The units of the grid are inches or cen‐\ntimeters, depending on whether the paper format is letter (in) or a4 (cm).\n\nd [down()] Moves page down two thirds of a window-full. With a float argument to\n``down'', moves down the corresponding fraction of a window-full.\n\nCtrl-f [find()] Pop up a window to search for a string in the DVI file. See the section\nSTRING SEARCH, below, for more details.\n\nf [forward-page()] Moves to the next page (or to the nth next page if a number is giv‐\nen). Synonyms are `n', Return, and Line Feed.\n\nG [set-greyscaling()] This key toggles the use of greyscale anti-aliasing for displaying\nshrunken bitmaps. In addition, the key sequences `0G' and `1G' clear and set this\nflag, respectively. See also the -nogrey option.\n\nIf given a numeric argument that is not 0 or 1, greyscale anti-aliasing is turned on,\nand the gamma resource is set to the value divided by 100. E.g. `150G' turns on\ngreyscale and sets gamma to 1.5.\n\nCtrl-g [find-next()] Find the next match string in the DVI file; this can be used instead of\npressing the `Find' button in the search window.\n\ng [goto-page()] Moves to the page with the given number. If no page number is given, xd‐\nvi jumps to the last page.\nIf the option/resource useTeXpages is active, the numbers correspond to the actual\npage numbers in the TeX file; otherwise, absolute page numbers (starting from 1) are\nused. In the latter case, the page numbers can be changed with the `P' keystroke, be‐\nlow. Note that with the useTeXpages option it is possible that the same page number\noccurs multiple times; in such a case, xdvi will use the first page number that match‐\nes.\n\nh Pops up a help window with a short explanation of the most important key bindings and\nconcepts.\n\nk [set-keep-flag()] Normally when xdvi switches pages, it moves to the home position as\nwell. The `k' keystroke toggles a `keep-position' flag which, when set, will keep the\nsame position when moving between pages. Also `0k' and `1k' clear and set this flag,\nrespectively. See also the -keep option.\n\nCtrl-l [fullscreen(toggle)] Toggles fullscreen mode (see the description of the -fullscreen\noption for more information on this). This is even more flaky than using the command-\nline option: There is no universal standard how a window could change its own geometry\nor window decorations at run-time, so this will not work with most window managers or\ndesktops. Generally, it's better to use the window manager controls to change the size\nor decorations of the xdvi window.\n\nl [left()] Moves page left two thirds of a window-full.\n\nM [set-margins()] Sets the margins so that the point currently under the mouse cursor\ndefines the upper left-hand corner of the text in the page. Note that the command\ndoes not move the image, but only determines the margins for the page switching com‐\nmands. For details on how the margins are used, see the -margins option.\n\nm [toggle-mark()] Toggles the mark for the current page in the page list. When a page is\nmarked, it is displayed with a small star `*' next to the page number. The marked\npages can then be printed or saved to a file. A page or several pages can also be\nmarked by clicking or dragging Mouse-2 in the page list.\n\nCtrl-n [toggle-mark()forward-page()] Toggles the mark for the current page in the page list,\nand moves to the next page. This lets you quickly mark a series of subsequent pages.\n\nn [forward-page()] Moves to the next page (or to the nth next page if a number is giv‐\nen). Synonyms are `f', Return, and Line Feed.\n\nCtrl-o [select-dvi-file()] Read a new dvi file. A file-selection widget is popped up for you\nto choose the DVI file from. If a prefix argument n is given, the n th file from the\nfile history is opened instead.\n\nP [declare-page-number()] ``This is page number n.'' This can be used to make the `g'\nkeystroke refer to a different page number than the physical page. (If you want to\nuse `logical' or TeX page numbers instead of physical pages, consider using the option\n-useTeXpages instead.) The argument n should be given as prefix to this key.\n\nCtrl-p [print()] Opens a popup window for printing the DVI file, or parts of it. See the\nsection PRINT DIALOG for an explanation of the options available, and the resources to\ncustomize the default behaviour.\n\np [back-page()] Moves to the previous page (or back n pages). Synonyms are `b', Ctrl-h\nand Backspace.\n\nq [quit()] Quits the program.\n\nCtrl-r [forward-page(0)] Redisplays the current page.\n\nR [reread-dvi-file()] Forces the dvi file to be reread. This allows you to preview many\nversions of the same file while running xdvi only once.\n\nr [right()] Moves page right two thirds of a window-full.\n\nCtrl-s [save()] Opens a popup window for saving the DVI file, or parts of it. See the section\nSAVE DIALOG below for more information on this.\n\nS [set-density()] Sets the density factor to be used when shrinking bitmaps. This\nshould be a number between 0 and 100; higher numbers produce lighter characters. If\ngreyscaling mode is in effect, this changes the value of gamma instead. The new value\nof gamma is the given number divided by 100; negative values are allowed.\n\ns [set-shrink-factor()] Changes the shrink factor to the given number. If no number is\ngiven, the smallest factor that makes the entire page fit in the window will be used.\n(Margins are ignored in this computation.)\n\nT [use-tex-pages()] Use logical TeX pages (the values of the \\count0 register) instead\nof physical pages for the pagelist labels and when jumping to a page in a document via\ngoto-page(). See also the -useTeXpages option.\n\nt [switch-magnifier-units()] Switches the units used for the magnifier tick marks, and\nfor reporting the distance between the mouse pointer and the ruler centre in ruler\nmode (see the section MODES). The default value is specified by the X resource tickU‐\nnits (`mm' by default). The units toggle through the following values; except for\n`px', they all correspond to TeX's units: mm (millimeters) pt (TeX points), in (inch‐\nes), sp (scaled points, the unit used internally by TeX) bp (big points or `PostScript\npoints'), cc (cicero points), dd (didot points), pc (pica), and px (screen pixels).\n\nCtrl-u [back-page()toggle-mark()] Moves to the previous page, and toggles the mark for that\npage. This is the dual action to Ctrl-n.\n\nu [up()] Moves page up two thirds of a window-full. With a float argument to ``up'',\nmoves up the corresponding fraction of a window-full.\n\nCtrl-v [show-source-specials()] Show bounding boxes for every source special on the current\npage, and print the strings contained in these specials to stderr. With prefix 1, show\nevery bounding box on the page. This is for debugging purposes mainly.\n\nV [set-gs-alpha()] This key toggles the anti-aliasing of PostScript specials when\nGhostscript is used as renderer. In addition the key sequences `0V' and `1V' clear\nand set this flag, respectively. See also the -gsalpha option.\n\nv [set-ps()] This key toggles the rendering of PostScript specials between 3 states:\n\n- specials (like EPS graphics) are displayed;\n\n- specials are displayed along with their bounding box (if available);\n\n- only the bounding box is displayed.\n\nThe states can also be selected directly by using `1v', `2v' and `0v' respectively.\nSee also the -postscript option.\n\nCtrl-x [source-what-special()] Display information about the source special next to the mouse\ncursor in the statusline. This is the same special that would be found by source-spe‐\ncial(), but without invoking the editor. For debugging purposes.\n\nx [set-expert-mode()] Toggles expert mode, in which the statusline, the scrollbars, the\nmenu buttons, the toolbar (Motif only) and the page list are not shown. Typing `1x'\ntoggles the display of the statusline at the bottom of the window. Typing `2x' toggles\nthe scrollbars (if available). For Xaw, `3x' toggles the menu buttons and the page\nlist, for Motif, it toggles the page list. In Motif, the additional bindings `4x' tog‐\ngle the toolbar, and `5x' the menu bar.\nWithout a prefix argument, all of the mentioned GUI elements are either switched on\n(if they had been invisible before) or off.\nToggling the scrollbars may behave erratically with the Xaw widgets; e.g. the scroll‐\nbars may reappear after resizing the window, and at certain window sizes one of the\nscrollbars may fail to disappear.\nSee also the option -expertmode (the numbers above correspond to the bits in the argu‐\nment to -expertmode).\n" } ] }, "MOUSE ACTIONS IN THE MAIN WINDOW": { "content": "The mouse actions can be customized by setting the X resource mouseTranslations. Since there\nare three different mouse modes (see the section MODES below), there is a special action\nmouse-modes which lists the actions for each of the three modes: mouse-modes(\"ACTIONS-FOR-\nMODE1\", \"ACTIONS-FOR-MODE2\", \"ACTIONS-FOR-MODE3\"). If only one argument is specified, this\naction is used for all modes. The default bindings are as follows:\n\nxdvi.mouseTranslations: \\\nShift:mouse-modes(\"drag(+)\")\\n\\\nShift:mouse-modes(\"drag(|)\")\\n\\\nShift:mouse-modes(\"drag(-)\")\\n\\\nCtrl:mouse-modes(\"source-special()\")\\n\\\n: mouse-modes(\"do-href()magnifier(*2)\", \"text-selection()\", \"ruler()\")\\n\\\n: mouse-modes(\"do-href-newwindow()magnifier(*2)\", \"text-selection()\", \"ruler()\")\\n\\\n: mouse-modes(\"magnifier(*3)\")\\n\\\n: mouse-modes(\"wheel(-0.2)\")\\n\\\n: mouse-modes(\"wheel(0.2)\")\\n\\\n: mouse-modes(\"hwheel(-0.2)\")\\n\\\n: mouse-modes(\"hwheel(0.2)\")\\n\\\n\nAll of these actions are described in more detail below. Note the use of quote symbols\naround the action strings, which are necessary to group them into one argument. Buttons 4,\n5, 6, and 7 refer to wheel movements (wheel up/down/left/right) on wheel mice. Not all mice\nsupport horizontal scrolling.\n\nThe X Toolkit routines that implement translations do not support event types of Btn6Down or\nBtn7Down. Because of this, xdvi implements its own parser for translations given in mouse‐\nTranslations. This parser is more limited than the parser built in to the X Toolkit. The\nstring given in mouseTranslations should not begin with ``#replace'', ``#augment'', or\n``#override''. Modifiers of the form @keysym are not supported, and the event type must be\nof the form BtnDown or BtnnDown, where n is a positive integer without leading zeroes. Also,\nsome limitations apply to the action field.\n", "subsections": [ { "name": "do-href()", "content": "" }, { "name": "do-href-newwindow()", "content": "Usually, if a binding specifies more then one action, all actions are executed in a\nsequence. The hyperlink bindings do-href() and do-href-newwindow() are special in that\nthey are used as an alternative to other actions that might follow them if the mouse\nis currently located on a hyperlink. In this case, none of the other actions will be\nexecuted; otherwise, only the other actions are executed.\nThe action do-href() jumps to the link target in the current xdvi window (eventually\nswitching to another page), and do-href-newwindow() opens a new instance of xdvi for\nthe link target. In both cases, the location of the target is indicated by a small\narrow drawn in the same color as a visited link in the left corner of the window.\n" }, { "name": "magnifier(n x m)", "content": "magnifier(*n)\nThis action will pop up a ``magnifying glass'' which shows the unshrunk image of the\nregion around the mouse pointer. The magnifier disappears when the mouse button is\nreleased. Moving the mouse cursor while holding the button down will move the magnifi‐\ner.\nDifferent mouse buttons produce different sized windows, as indicated by the argument\nof the magnifier() action. Its argument is either a string of the form widthxheight,\nas in the -mgsn command-line option, or one of the strings *1 through *5, referring to\nthe value specified by the corresponding -mgsn option.\n" }, { "name": "drag(+)", "content": "" }, { "name": "drag(|)", "content": "" }, { "name": "drag(-)", "content": "Drags the page with the mouse. This action should have one parameter, the character\n``|'', ``-'', or ``+'', indicating vertical dragging only, horizontal dragging only,\nor dragging in all directions.\n" }, { "name": "source-special()", "content": "This action starts a ``reverse search'', opening the editor at the location in the TeX\nfile corresponding to the pointer location in the DVI file. See the section on SOURCE\nSPECIALS, below, for more information on this.\n" }, { "name": "wheel()", "content": "This action can be used to scroll the image with a wheel mouse, where it is usually\nbound to mouse button 4 (wheel up) or 5 (wheel down). The action takes one parameter,\ngiving the distance to scroll the image. If the parameter contains a decimal point,\nthe distance is given in wheel units; otherwise, pixels. A negative value scrolls up,\na positive value scrolls down.\n" }, { "name": "hwheel()", "content": "This action can be used to scroll the image horizontally with a wheel mouse, where it\nis usually bound to mouse button 6 (wheel left) or 7 (wheel right). The action takes\none parameter, giving the distance to scroll the image. If the parameter contains a\ndecimal point, the distance is given in wheel units; otherwise, pixels. A negative\nvalue scrolls left, a positive value scrolls right. Not all mice support horizontal\nscrolling; this is mostly for touchpads, trackpads, etc.\n" }, { "name": "text-selection()", "content": "This action allows you to mark a rectangular region of text in the DVI file. The text\nis put into the X selection buffer and can be pasted into other applications (e.g.\ntext editors). This works similar to the Plain text option in the Save dialog; see the\ndiscussion there for more information on encoding issues.\n" }, { "name": "ruler()", "content": "This action creates a cross-shaped ruler. Moving the mouse and holding the button down\ndrags the ruler and lets you measure distances on the page. See the section Ruler\nMode for more information on this.\n" } ] }, "UNBOUND ACTIONS": { "content": "The following actions are not bound to a key by default, but are available for customization.\n", "subsections": [ { "name": "quit-confirm()", "content": "Pops up a confirmation window to quit xdvi. To bind it to the `q' key instead of the\ndefault `quit()' action, put the following into your ~/.Xdefaults file:\n\nxdvi.mainTranslations: #override\\\nq: quit-confirm()\\n\n" }, { "name": "down-or-next()", "content": "Similar to unpause-or-next(): Moves down two-thirds of a window-full, or to the next\npage if already at the bottom of the page.\n" }, { "name": "shrink-to-dpi()", "content": "This action takes one (required) argument. It sets the shrink factor to an integer so\nas to approximate the use of fonts with the corresponding number of dots per inch. If\nxdvi is using fonts scaled for p dots per inch, and the argument to shrink-to-dpi is\nn, then the corresponding shrink factor is the ratio p/n, rounded to the nearest inte‐\nger.\n" }, { "name": "user-exec()", "content": "This action takes one (required) argument. Runs an external program specified by the\nargument, which is tokenized on whitespace. The XDVIFILE environment variable is set\nto the absolute pathname of the DVI file, so that the program can find the DVI. As an\nexample, to establish the key `m' as a keybinding that regenerates the DVI file with\n`make', put the following into your ~/.Xdefaults file:\n\nxdvi.mainTranslations: #override\\\nm: user-exec(xdvi-remake)\\n\n\nwhere `xdvi-remake' names a program in your PATH analogous to `cd $(dirname $XD‐\nVIFILE) && make $(basename $XDVIFILE)'. (See also the section SIGNALS for a way to\nget xdvi to reload the DVI file once it has been regenerated.)\n" } ] }, "CUSTOMIZATION": { "content": "Key and mouse button assignments can be changed by setting the mainTranslations resource to a\nstring of translations as defined in the documentation for the X toolkit. The actions should\ntake the form of action names listed in the KEYSTROKES and MOUSE ACTIONS sections.\n\nAn exception to this are the Motif keys osfPageUp (PgUp), osfPageDown (PgDown), osfBeginLine\n(Home) and osfEndLine (End) which are currently not customizable in the Motif version.\n\nKey actions will usually be without arguments; if they are passed an argument, it represents\nthe optional number or `prefix argument' typed prior to the action.\n\nSome key actions may take special arguments, as follows: The argument of goto-page may be the\nletter `e', indicating the action of going to the end of the document. The argument of set-\nshrink-factor may be the letter `a', indicating that the shrink factor should be set to the\nsmallest value such that the page will fit in the window, or one of the signs `+' or `-', in‐\ndicating that the shrink factor should be increased or decreased, respectively. Finally, ac‐\ntions that would perform a toggle, such as set-keep-flag, may receive an argument `t', indi‐\ncating that the action should toggle regardless of the current prefix argument.\n\nMouse actions should refer only to ButtonPress events (e.g. :magnifier(*1)). The\ncorresponding motion and release events will be handled internally. A key action may be\nbound to a mouse event, but not vice versa.\n\nUsually the string of translations should begin with ``#override'', indicating that the de‐\nfault key and mouse button assignments should not be discarded.\n\nWhen keys or mouse buttons involving modifiers (such as Ctrl or Shift) are customized togeth‐\ner with their non-modified equivalents, the modified keys should come first, for example:\n\nxdvi.mainTranslations: #override \\\nShifts: select-dvi-file()\\n\\\nCtrls: save()\\n\\\ns: find()\\n\n\n\nBecause xdvi needs to capture pointer motion events, and because the X Toolkit translations\nmechanism cannot accommodate both motion events and double-click events at the same time, it\nis not possible to specify double-click actions in xdvi customizations. For information on\nthis and other aspects of translations, see the X Toolkit Intrinsics documentation.\n\nThere is no command-line option to set the mainTranslations resource, since changing this re‐\nsource on the command line would be cumbersome. To set the resource for testing purposes,\nuse the -xrm command-line option provided by the X toolkit. For example, xdvi -xrm 'XD‐\nvi.mainTranslations: #override \"z\":quit()' ... or xdvi -xrm 'XDvi.mainTranslations: #over‐\nride z:quit()' ... will cause the key `z' to quit xdvi.\n\nSome resources are provided to allow customization of the geometry of the Xaw command but‐\ntons. Again, they are not changeable via command-line options, other than via the -xrm op‐\ntion. All of these resources take integer values.\n", "subsections": [ { "name": "buttonSideSpacing", "content": "The number of pixels to be placed on either side of the buttons. The default value is\n6.\n" }, { "name": "buttonTopSpacing", "content": "The number of pixels between the top button and the top of the window. The default\nvalue is 50.\n" }, { "name": "buttonBetweenSpacing", "content": "The number of pixels between the buttons. The default value is 20.\n" }, { "name": "buttonBetweenExtra", "content": "The number of pixels of additional space to be inserted if the buttonTranslations re‐\nsource string contains an extra newline character. The default value is 50.\n" }, { "name": "buttonBorderWidth", "content": "The border width of the button windows. The default value is 1.\n" } ] }, "PAGE LIST": { "content": "The scrollable page list on the right of the main window allows you to jump directly to a\npage in the DVI file.\n", "subsections": [ { "name": "Mouse-1", "content": "Jumps to the page the mouse is located on.\n" }, { "name": "Mouse-2", "content": "[toggle-mark()] Toggle the mark of the current page. The marks are used by the `Print'\nand `Save to file' dialogs to select only marked pages from the DVI file.\n\nWhen the mouse pointer is inside the page list, the mouse wheel switches to the next or pre‐\nvious page.\n" } ] }, "SCROLLBARS": { "content": "The scrollbars (if present) behave in the standard way: pushing Button 2 in a scrollbar\nmoves the top or left edge of the scrollbar to that point and optionally drags it; pushing\nButton 1 moves the image up or right by an amount equal to the distance from the button press\nto the upper left-hand corner of the window; pushing Button 3 moves the image down or left by\nthe same amount.\n\nThe scrollbars can be removed via the -expertmode flag/keystroke (which see).\n", "subsections": [] }, "MAGNIFIER": { "content": "By default, the mouse buttons 1 to 5 will pop up a ``magnifying glass'' that shows an un‐\nshrunken image of the page (i.e. an image at the resolution determined by the option/X re‐\nsource pixels or mfmode) at varying sizes. When the magnifier is moved, small ruler-like tick\nmarks are displayed at the edges of the magnifier (unless the X resource delayRulers is set\nto false, in which case the tick marks will always be displayed). The unit of the marks is\ndetermined by the X resource tickUnits (mm by default). This unit can be changed at runtime\nvia the action switch-magnifier-units(), by default bound to the keystroke `t' (see the de‐\nscription of that key, and of switch-magnifier-units() for more details on the units avail‐\nable).\nThe length of the tick marks can be changed via the X resource tickLength (4 by default). A\nzero or negative value suppresses the tick marks.\n", "subsections": [] }, "PAGE HISTORY": { "content": "Xdvi keeps a history of viewed pages, and you can move through the history and delete items\nusing the keys [ (pagehistory-back()), ] (pagehistory-forward()), Ctr-[ (pagehistory-delete-\nbackward()) and Ctr-] (pagehistory-delete-forward()).\n\nWhen one of the history commands is used, the page history is displayed in the status line at\nthe bottom of the window, with the current list item marked by square brackets `[', `]' and a\nleft and right context of at most 10 items. File boundaries are marked by `#'.\n\nThe size of the history can be customized with the X resource pageHistorySize (the default\nsize is 1000 items). If the size is set to 0, the history commands are disabled.\n", "subsections": [] }, "HYPERLINKS": { "content": "The actions do-href() and do-href-newwindow() (by default bound to Mouse-1 and Mouse-2 if the\npointer is currently located on a hyperlink) can be used to open the link target in the same\nwindow (do-href()) or in a new window (do-href-newwindow()).\n\nIf the link target is not a file on the local disk, xdvi tries to launch a web browser (as\nspecified by the -browser command line option, the BROWSER environment variable or the www‐\nBrowser X resource, in this order) to retrieve the document. See the description of the\nBROWSER environment variable, below, for an example setting.\n\nIf the file is a local file, xdvi tries to determine if it is a DVI file. If it is, xdvi will\ntry to display the file; otherwise it will try to determine the MIME type of the file, and\nfrom that an application suitable for opening the file. This is done by parsing the files\nspecified by the environment variable EXTENSIONMAPS for a mapping of filename extensions to\nMIME types, and the files determined by the environment variable MAILCAPS for a mapping of\nMIME types to application programs. See the descriptions of these variables in the section\nENVIRONMENT, below, for a more detailed description and the default values of these vari‐\nables. If no suitable files are found, a set of built-in default MIME types and applications\nis used.\n\nXdvi currently uses no heuristics apart from the filename suffix to determine the mime type\nof a file. If a filename has no suffix, the value of the resource noMimeSuffix is used (by\ndefault application/x-unknown). If the suffix doesn't match any of the suffixes in\nmime.types, the value of the resource unknownMimeSuffix is used (by default application/x-un‐\nknown). If the mailcap entries do not list a viewer for a given mime type, xdvi will show a\nwarning popup. If you want to avoid this warning, and for example want to always use the\nnetscape browser for unknown MIME types, you could add the following line to your ~/.mailcap\nfile:\n\napplication/xdvi-unknown; \\\nnetscape -raise -remote 'openURL(%s,new-window)'\n\n", "subsections": [] }, "STRING SEARCH": { "content": "The keystroke Ctrl-f or the menu entry File > Find ... (or the `Binoculars' symbol in the\ntoolbar, for Motif) opens a dialog window to search for a text string or a regular expression\nin the DVI file. The keystroke Ctrl-g jumps to the next match (like pressing the `Find' but‐\nton in the search window).\n\nBy default, the matches are highlighted in inverted color. If the display isn't running in\nTrueColor, or if the X resource matchHighlightInverted is set to false or the command-line\noption -nomatchinverted is used, xdvi will instead draw a rectangle in highlight color (see\nthe -hl option) around the match.\n\nIf a match crosses a page boundary, only the part on the first page is highlighted. Xdvi\nwill scan up to 2 adjacent pages to match strings crossing page boundaries; but note that\nheader or footer lines, or intervening float pages will be treated as parts of the scanned\ntext. Such text will usually cause multi-page matching to fail.\n\nThis emphasizes the fact that searching in the formatted text (the DVI output) works differ‐\nently from searching in the source text: Searching in the DVI file makes it easier to skip\nformatting instructions, and makes it possible to search for e.g. hyphenation and equation\nnumbers; but sometimes the formatting results can also get in the way, e.g. in the case of\nfootnotes. In these cases it's better to search in the TeX source instead. The use of source\nspecials will make switching between the xdvi display and the editor with the TeX source eas‐\nier; see the section SOURCE SPECIALS below for more information on this.\n\nThe text extracted from the DVI file is in encoded in UTF-8 (you can view that text by saving\nthe file in UTF-8 format via the File > Save as ... menu item). If xdvi has been compiled\nwith locale, nllanginfo() and iconv support, the search term is converted from the character\nset specified by the current locale into UTF-8. (See the output of locale -a for a list of\nlocale settings available on your system). If nllanginfo() is not available, but iconv is,\nyou can specify the input encoding for iconv via the X resource textEncoding (see the output\nof iconv -l for a list of valid encodings). If iconv support is not available, only the en‐\ncodings ISO-8859-1 and UTF-8 are supported (these names are case-insensitive).\n\nIdeographic characters from CJKV fonts are treated specially: All white space (spaces and\nnewlines) before and after such characters is ignored in the search string and in the DVI\nfile.\n\nTo match a newline character, use \\n in the search string; to match the string \\n, use \\\\n.\n\nIf the checkbox Regular Expression is activated, the string is treated as a regular expres‐\nsion in extended POSIX syntax, with the following properties:\n\n- a? matches a zero or one times.\n\n- a* matches a zero or more times.\n\n- a+ matches a one or more times. Note that * and + are greedy, i.e. they match the\nlongest possible substring.\n\n- The pattern . matches any character except for newline. To also match a newline, use\n`(.|\\n)'.\n\n- a{n} matches a exactly n times.\n\n- a{n,m} matches a at least n and no more than m times.\n\n- a|b matches a or b. Brackets can be used for grouping, e.g.: (a|b)|c.\n\n- The string matched by the nth group can be referenced by \\n, e.g. \\1 refers to the first\nmatch.\n\n- The characters ^ and $ match the beginning and the end of a line, respectively.\n\n- [abc] matches any of the letters a, b, c, and [a-z] matches all characters from a to z.\n\n- Each item in a regular expression can also be one of the following POSIX character class‐\nes:\n[[:alnum:]] [[:alpha:]] [[:blank:]] [[:cntrl:]] [[:digit:]]\n[[:graph:]] [[:lower:]] [[:print:]] [[:space:]] [[:upper:]]\n\n\nThese can be negated by inserting a ^ symbol after the first bracket: [^[:alpha:]]\n\nFor more details on POSIX regular expressions, see e.g. the IEEE Std 1003.1 standard def‐\ninition available online from:\n\nhttp://www.opengroup.org/onlinepubs/007904975/basedefs/xbdchap09.html\n\n- As a non-standard extension, the following Perl-like abbreviations can be used instead of\nthe POSIX classes:\n\nSymbol Meaning POSIX Class\n\n\\w an alphanumeric character [[:alnum:]]\n\\W a non-alphanumeric character [^[:alnum:]]\n\\d a digit character [[:digit:]]\n\\D a non-digit character [^[:digit:]]\n\\s a whitespace character [[:space:]]\n\\S a non-whitespace character [^[:space:]]\n\n\n- The following characters are special symbols; they need to be escaped with \\ in order to\nmatch them literally: ( ) [ ] . * ? + ^ $ \\.\n\n- Matches of length zero are silently skipped.\n\nThe dialog also provides checkboxes to:\n\n- search backwards;\n\n- match in a case-sensitive manner (the default is to ignore case, i.e. a search string\nTest will match both the strings test and TEST in the DVI file);\n\n- ignore line breaks and hyphens: This removes all hyphens at the ends of lines and the\nfollowing newline characters, and replaces all remaining newline characters by white\nspaces. So hyphenated words will appear as one word to the search, and a search for two\nwords with a space in between will also match the words if they are separated by a line‐\nbreak.\nNote that the hyphen removal may cause unwanted side effects for compound words contain‐\ning hyphens that are wrapped after the hyphen, and that replacing the newlines affects\nthe interpretation of regular expressions as follows: The . pattern will also match new‐\nlines, and ^ and $ won't match begin and end of lines any more. (Since currently there is\nno option for turning off the greediness of * and +, turning on this option will usually\nresult in matches that are longer than desired.)\n\nThe current checkbox settings are saved in the ~/.xdvirc file.\n", "subsections": [] }, "PRINT DIALOG": { "content": "The print dialog window allows you to print all pages, marked pages (click or drag Mouse-2 in\nthe page list to mark them), or a range of pages. Note that the page numbers always refer to\nphysical pages, so if you're using the option `use TeX pages', you may want to disable it to\nmake it easier to determine the correct page numbers (or avoid this problem altogether by\nmarking the pages to be printed).\n\nThe value of the Printer text filed is passed to dvips via the -o! mechanism, as a single\nargument after the `!'. Any arguments listed in the Dvips options field are segmented at\nwhitespace and passed as separate arguments to dvips. If you e.g. want to print the file\n2-up, you should enter the following string into the Printer field:\n\npsnup -2 -q | lpr -Plp\n\n\nThere are several resources for customizing the behaviour and the default entries of the\nprint dialog:\n", "subsections": [ { "name": "dvipsPrinterString", "content": "" }, { "name": "dvipsOptionsString", "content": "These can be used to provide default entries for the Printer and the Dvips options\ntext fields, respectively. If no paper size is specified in the DVI file (via e.g.\n\\usepackage[dvips]{geometry} - this is the preferred method), the input field is ini‐\ntialized with the current value of the command line option/X resource paper. E.g. the\noption -paper a4r is translated into the dvips options -t a4 -t landscape. Note that\nno check is performed whether dvips actually understands these options (it will ignore\nthem if it can't); currently not all options used by xdvi are also covered by dvips.\n" }, { "name": "dvipsHangTime", "content": "" }, { "name": "dvipsFailHangTime", "content": "These specify the time (in milliseconds) that the printing progress window will stay\nopen after the dvips process has terminated. The value of dvipsHangTime is used if the\nprocess terminates successfully; dvipsFailHangTime is used if it terminates with an\nerror. The default values are 1.5 and 5 seconds, respectively. If both values are\nnegative, the window will stay open until it is closed by the user.\n" } ] }, "SAVE DIALOG": { "content": "This dialog allows you to save all or selected/marked pages in the current DVI file. You can\nsave in one of the following formats:\n\n- PostScript (uses dvips to convert the DVI file to a PostScript file, just like when\nprinting to a PostScript file).\n\n- PDF (first uses dvips to convert the DVI file to a PostScript file, then uses ps2pdf to\nconvert the PostScript file to PDF).\n\n- Plain text in ISO-8859-1 or UTF-8 encoding. The latter will preserve more of the special\nLaTeX characters e.g. from mathematical mode. Note however that e.g. only few of LaTeX's\nmathematical symbols can be rendered correctly as text; so this functionality works best\nfor plain text documents. If a character cannot be displayed in the selected charset, it\nis replaced by `\\' followed by the hexadecimal character code. If a character is not\nrecognized at all, it is replaced by `?'.\n\nThe programs for PostScript and PDF conversion can be customized via the command line options\nor X resources -dvipspath/.dvipsPath and -ps2pdfpath/.ps2pdfPath, respectively; see the ex‐\nplanation of these options above for more details.\n", "subsections": [] }, "MODES": { "content": "The keystroke Ctrl-m [switch-mode()] switches between three different mouse bindings, which\ncan also be activated via the Modes menu (in Motif, this is a submenu of the Options menu\ncalled Mouse Mode). The default mode at startup can be customized via the X resource mouse‐\nMode or the command-line option -mousemode. The default startup mode is Magnifier Mode.\n\nNote: The modes are implemented by changing the magnifier() action. Switching the mode will\nnot work if Mouse-1 has been customized to an action sequence that does not contain the mag‐\nnifier() action.\n", "subsections": [ { "name": "Magnifier Mode", "content": "In this mode, the mouse buttons 1 to 5 pop up a ``magnifying glass'' that shows an un‐\nshrunken image of the page (i.e. an image at the resolution determined by the option/X\nresource pixels or mfmode) at varying sizes. When the magnifier is moved, small ruler-\nlike tick marks are displayed at the edges of the magnifier (unless the X resource de‐\nlayRulers is set to false, in which case the tick marks are always displayed). The\nunit of the marks is determined by the X resource tickUnits (mm by default). This unit\ncan be changed at runtime via the action switch-magnifier-units(), by default bound to\nthe keystroke `t' (see the description of that key, and of switch-magnifier-units()\nfor more details on the units available).\nThe length of the tick marks can be changed via the X resource tickLength (4 by de‐\nfault). A zero or negative value suppresses the tick marks.\n" }, { "name": "Text Selection Mode", "content": "This mode allows you to select a rectangular region of text in the DVI file by holding\ndown Mouse-1 and moving the mouse. The text is put into the X primary selection so\nthat it can be pasted into other X applications with Mouse-2 as usual.\nIf xdvi has been compiled with locale, nllanginfo() and iconv support, the selected\ntext is converted into the character set of the current locale (see the output of lo‐\ncale -a for a list of locale settings available on your system). If nllanginfo() is\nnot available, but iconv is, you can specify the input encoding for iconv via the X\nresource textEncoding (see the output of iconv -l for a list of valid encodings). If\niconv support is not available, only the encodings ISO-8859-1 and UTF-8 are supported\n(these names are case-insensitive).\nNote that UTF-8 is the only encoding that can render all characters (e.g. mathematical\nsymbols) of a DVI file. If ISO-8859-1 is active, characters that cannot be displayed\nare replaced by `\\' followed by the hexadecimal character code. For other encodings,\nsuch characters may trigger iconv error messages. If a character is not recognized at\nall, it is replaced by `?'.\nTo extract larger portions of text, you can alternatively save selected pages or the\nentire file in text format via the File > Save as ... menu.\n" }, { "name": "Ruler Mode", "content": "This mode provides a simple way of measuring distances on the page.\nWhen this mode is activated, the mouse cursor changes into a thin cross, and a larger,\ncross-shaped ruler is drawn in the highlight color at the mouse location. The ruler\ndoesn't have units attached to it; instead, the current distance between the ruler and\nthe mouse cursor is continuously printed to the statusline.\nWhen activating Ruler Mode, the ruler is at first attached to the mouse and can be\nmoved around. It can then be positioned at a fixed place by clicking Mouse-1. After\nthat, the mouse cursor can be moved to measure the horizontal (dx), vertical (dy) and\ndirect (shortest) (dr) distance between the ruler center point and the mouse.\nClicking Mouse-1 again will move the ruler to the current mouse position, and holding\ndown Mouse-1 will drag the ruler around.\nIn Ruler Mode, the following special keybindings extend or replace the default bind‐\nings:\n\no [ruler-snap-origin()] Snap the ruler back to the origin coordinate (0,0).\n\nt [overrides switch-magnifier-units()] Toggle between various ruler units, which\ncan be specified by the X resource tickUnits (`mm' by default).\n\nP [overrides declare-page-number()] Print the distances shown in the statusline\nto standard output.\n\nTOOLBAR (Motif only)\nThe Motif toolbar can also be customized. The XPM file used for the toolbar icons can be\nspecified via the resource toolbarPixmapFile, which should contain a filename that can be\nfound in one of XFILESEARCHPATH or XDVIINPUTS (see the section FILE SEARCHING below for more\ninformation on these variables). Xdvi will try to split this pixmap horizontally into n\npieces, where each piece is as wide as the pixmap is high and is treated as an image for\ntoolbar button n. This means that each icon should be a square, and that the entire pixmap\nshould have width n x h if h is the height of the pixmap.\n\nThe resource toolbarTranslations can be used to map icons/buttons to specific actions. The\nresource should contain a string separated by newline characters, similar to the resources\nmainTranslations and menuTranslations. Every line must contain either a spacer definition,\nor an icon definition:\n\nA spacer definition is a string SPACER(n), where n is the number of pixels inserted as sepa‐\nrator to the following button.\n\nAn icon definition is a colon-separated list containing the following elements:\n\n- the index of an icon in the pixmap file (starting from zero);\n\n- a long tooltip string, displayed in the status area;\n\n- a short tooltip string, displayed as popup;\n\n- a sequence of actions to be performed when the corresponding toolbar button is pushed.\n\nTo illustrate this, the default value of toolbarTranslations looks as follows:\n\nxdvi.toolbarTranslations: \\\nSPACER(5)\\n\\\n0:Open a new document (Key\\\\: Ctrl-f):\\\nOpen file:select-dvi-file()\\n\\\nSPACER(10)\\n\\\n1:Reread this document (Key\\\\: R):\\\nReread file:reread-dvi-file()\\n\\\nSPACER(10)\\n\\\n2:Go to the first page of this document (Key\\\\: 1g):\\\nGo to first page:goto-page(1)\\n\\\n3:Go to the previous page of this document (Key\\\\: p):\\\nGo to previous page:back-page(1)\\n\\\n4:Go to the next page of this document (Key\\\\: n):\\\nGo to next page:forward-page(1)\\n\\\n5:Go to the last page of this document (Key\\\\: g):\\\nGo to last page:goto-page()\\n\\\nSPACER(10)\\n\\\n6:Enlarge the display (Key\\\\: Ctrl-+):Zoom in:\\\nset-shrink-factor(+)\\n\\\n7:Shrink the display (Key\\\\: Ctrl--):Zoom out:\\\nset-shrink-factor(-)\\n\\\nSPACER(10)\\n\\\n8:Jump back to the previous hyperlink (Key\\\\: B):\\\nBack hyperlink:htex-back()\\n\\\nSPACER(10)\\n\\\n10:Print this document:Print:print()\\n\\\nSPACER(10)\\n\\\n11:Toggle marks for odd pages (Key\\\\: 1m):\\\nToggle odd:toggle-mark(1)\\n\\\n12:Toggle marks for even pages (Key\\\\: 2m):\\\nToggle even:toggle-mark(2)\\n\\\n13:Toggle mark for current page (Key\\\\: 2m):\\\nToggle current:toggle-mark()\\n\\\n14:Unmark all pages (Key\\\\: 0m):\\\nUnmark all:toggle-mark(0)\\n\\\nSPACER(10)\\n\\\n18:Display fonts darker (Key\\\\: Alt-Ctrl-+):\\\nFonts darker:change-density(5)\\n\\\n19:Display fonts lighter (Key\\\\: Alt-Ctrl--):\\\nFonts lighter:change-density(-5)\\n\n\n\nWhen the mouse remains over a toolbar button for a certain period, a `tooltip' window is\nshown, describing what the button does using the short tooltip string from the above re‐\nsource. At the same time, the long tooltip string is displayed in the statusline. The ap‐\npearance and behaviour of these tooltips can be customized via the following resources:\n" }, { "name": "tipShell.background", "content": "Background color of the tooltip window.\n" }, { "name": "tipShell.fontSet", "content": "Font used for the tooltip.\n" }, { "name": "tipShell.waitPeriod", "content": "The time (in milliseconds) the mouse pointer needs to be over the button before the\ntooltip is shown. Set it to a negative value to suppress the tooltips altogether.\n\n" } ] }, "GREYSCALING AND COLORMAPS": { "content": "The greyscale anti-aliasing feature in xdvi will not work at its best if the display does not\nhave enough colors available. This can happen if other applications are using most of the\ncolormap (even if they are iconified). If this occurs, then xdvi will print an error message\nand turn on the -copy option. This will result in overstrike characters appearing wrong; it\nmay also result in poor display quality if the number of available colors is very small.\n\nTypically this problem occurs on displays that allocate eight bits of video memory per pixel.\nTo see how many bits per pixel your display uses, type xwininfo in an xterm window, and then\nclick the mouse on the root window when asked. The ``Depth:'' entry will tell you how many\nbits are allocated per pixel.\n\nDisplays using at least 15 bits per pixel are typically TrueColor visuals, which do not have\nthis problem, since their colormap is permanently allocated and available to all applica‐\ntions. (The visual class is also displayed by xwininfo.) For more information on visual\nclasses see the documentation for the X Window System.\n\nTo alleviate this problem, therefore, one may (a) run with more bits per pixel (this may re‐\nquire adding more video memory or replacing the video card), (b) shut down other applications\nthat may be using much of the colormap and then restart xdvi, or (c) run xdvi with the -in‐\nstall option.\n\nOne application which is often the cause of this problem is Netscape. In this case there are\ntwo more alternatives to remedying the situation. One can run ``netscape -install'' to cause\nNetscape to install a private colormap. This can cause colors to change in bizarre ways when\nthe mouse is moved to a different window. Or, one can run ``netscape -ncols 220'' to limit\nNetscape to a smaller number of colors. A smaller number will ensure that other applications\nhave more colors available, but will degrade the color quality in the Netscape window.\n\n", "subsections": [] }, "HANDLING OF POSTSCRIPT FIGURES": { "content": "Xdvi can display Encapsulated PostScript (EPS) files included in the dvi file. Such files\nare first searched for in the directory where the dvi file is, and then using normal Kpathsea\nrules. There is an exception to this, however: if the file name begins with a backtick (`),\nthen the remaining characters in the file name give a shell command (often zcat) which is ex‐\necuted; its standard output is then sent to be interpreted as PostScript. Since the execu‐\ntion of arbitrary shell commands with the user's permissions is a huge security risk, evalua‐\ntion of these backtick commands is disabled by default. It needs to be activated via the -al‐\nlowshell command-line option. NOTE: You should never use this option when viewing documents\nthat you didn't compile yourself. The backtick specials are not needed for uncompressing\ngzipped PostScript files, since xdvi can do that on the fly if the filename ends with .eps.gz\nor .eps.Z (and if the first bytes of the file indicate that the file is indeed compressed).\nThis is both safer and more flexible than the backtick approach, since the default file\nsearching rules will apply to such filenames too.\n", "subsections": [] }, "TYPE 1 FONTS": { "content": "Using FreeType (version 2), xdvi can render PostScript Type 1 fonts directly, without the\nroute via TeX pixel (pk) fonts. The advantage of this is that only one size of each font\nneeds to be stored on disk. Unless the -notype1fonts option is used, xdvi will try to render\nevery font using FreeType. Only as a fallback will it invoke an external program (like mktex‐\npk, which in turn may invoke utilities like ps2pk or gsftopk) to generate a pixel font from\nthe Type 1 source. The direct rendering of the Computer Modern fonts should work out-of-the\nbox, whereas other Type 1 fonts such as the 35 `standard' PostScript fonts resident in\nprinters may need to be made accessible for use with xdvi, unless your system administrator\nor TeX distribution has already done so (which is the case e.g. for current TeX Live sys‐\ntems). For the 35 PostScript resident fonts, xdvik will search using the Fontmap provided\nwith Ghostscript, if necessary. Also, the xdvik distribution comes with a utility called\nt1mapper to make these fonts available for xdvi; see the manual page for t1mapper(1) for us‐\nage details. This program is likely to be dropped in the future, however, since it is proba‐\nbly not needed anymore.\n\nSPECIALS (GENERALLY)\nAny of the specials used by xdvi may be preceded by the characters ``xdvi:''. Doing so does\nnot change the behavior of the special under xdvi, but it tells other dvi drivers (such as\ne.g. dvips) to ignore the special.\n", "subsections": [] }, "SOURCE SPECIALS": { "content": "Some TeX implementations or macro packages provide the facility to automatically include so-\ncalled `source specials' into a DVI file. These contain the line number, eventually a column\nnumber, and the filename of the .tex source. This makes it possible to jump from a .dvi file\nto the corresponding place in the .tex source and vice versa (also called `inverse search' -\njumping from the DVI file to the TeX file is also known as `reverse search', and jumping from\nthe TeX file to the DVI file as `forward search').\n\nTo be usable with xdvi, source specials in the dvi file must have one of the following for‐\nmats:\n\nsrc:line[ ]filename\nsrc:line:col[ ]filename\nsrc:line\nsrc:line:col\nsrc::col\n\nIf filename or line are omitted, the most recent values are used. The first source special\non each page must be in one of the first two forms, since defaults are not inherited across\npages.\n\nYou will need a TeX implementation that provides an appropriate switch (e.g. -src) or a macro\npackage (such as srcltx.sty or srctex.sty, available from CTAN:macros/latex/contrib/support‐\ned/srcltx/) to insert such source specials into the DVI file.\n\nFor reverse search, the combination Ctrl-Mouse 1 will make xdvi open an editor (the value of\nthe -editor command line option) with the file and the line number of the .tex source. See\nthe description of the -editor option for more information and example settings.\n\nFor forward search, xdvi has a -sourceposition option that makes xdvi jump to the page in the\nDVI file corresponding to the given line (or the closest line having a source special) of the\nspecified file and highlight the found region. See the description of the -sourceposition op‐\ntion for more details.\n\nMore information on setting up various editors for use with source specials can be found at:\n\nhttp://xdvi.sourceforge.net/inverse-search.html\n\n", "subsections": [] }, "PAPERSIZE SPECIALS": { "content": "xdvi accepts specials to set the paper size for the document. These specials should be of\nthe form\n\npapersize=[*]width,height\n\n\nwhere width and height give the width and height of the paper, respectively. Each of these\nshould appear in the form of a decimal number followed by any of the two-letter abbreviations\nfor units accepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). If an asterisk (*) ap‐\npears just before the width, then the measurements refer to the document dimensions (e.g. pt\nas opposed to truept). This allows a macro package to vary the page size according to ele‐\nments of the document; e.g.\n\n\\special{xdvi: papersize=*\\number\\wd\\mybox sp,\n\\number\\ht\\mybox sp}\n\n\nExcept for the asterisk, this format is compatible with dvips.\n\nThe last papersize special on a page determines the size of that page. If there is no such\nspecial on a given page, the most recent papersize is used, or, if there are no papersize\nspecials on any preceding page, then the value of the paper resource (or -paper option on the\ncommand line) is used. Thus the paper size may vary for different pages of the dvi file.\n\nIf the paper resource (or -paper command-line option) begins with a plus sign (`+'), then all\npapersize specials in the dvi file are ignored.\n", "subsections": [] }, "COLOR SPECIALS": { "content": "The color specials supported by xdvi are the same as those supported by dvips, except that\nthe literal PostScript color specification (as in the AggiePattern example in the dvips docu‐\nmentation) is not supported. There are also some restrictions due to the way xdvi's drawing\nroutines are implemented; e.g. the \\colorbox and \\fcolorbox macros don't work with xdvi. See\nthe section LIMITATIONS below for more information on these restrictions. Xdvi supports the\nsame list of named colors as dvips does, namely:\n\nApricot, Aquamarine, Bittersweet, Black, Blue, BlueGreen, BlueViolet, BrickRed, Brown, Burn‐\ntOrange, CadetBlue, CarnationPink, Cerulean, CornflowerBlue, Cyan, Dandelion, DarkOrchid,\nEmerald, ForestGreen, Fuchsia, Goldenrod, Gray, Green, GreenYellow, JungleGreen, Lavender,\nLimeGreen, Magenta, Mahogany, Maroon, Melon, MidnightBlue, Mulberry, NavyBlue, OliveGreen,\nOrange, OrangeRed, Orchid, Peach, Periwinkle, PineGreen, Plum, ProcessBlue, Purple, RawSien‐\nna, Red, RedOrange, RedViolet, Rhodamine, RoyalBlue, RoyalPurple, RubineRed, Salmon, Sea‐\nGreen, Sepia, SkyBlue, SpringGreen, Tan, TealBlue, Thistle, Turquoise, Violet, VioletRed,\nWhite, WildStrawberry, Yellow, YellowGreen, YellowOrange.\n\nNote that these names are case sensitive.\n\nThe documentation of the LaTeX color package provides more details on how to use such spe‐\ncials with LaTeX; see the dvips documentation for a detailed description of the syntax and\nsemantics of the color specials.\n", "subsections": [] }, "SIGNALS": { "content": "When xdvi receives a SIGUSR1 signal, it rereads the dvi file.\n", "subsections": [] }, "ENVIRONMENT": { "content": "Xdvik uses the same environment variables and algorithms for searching for font files as TeX\nand friends. See the documentation for the Kpathsea library, kpathsea.dvi, for a detailed\ndescription of these.\n\nIn addition, xdvik accepts the following variables:\n\nDISPLAY\nSpecifies which graphics display terminal to use.\n\nKPATHSEADEBUG\nTrace Kpathsea lookups; set it to -1 (= all bits on) for complete tracing.\n\nEXTENSIONMAPS\nA list of files to be searched for mime types entries (as for Acrobat Reader). Earli‐\ner entries in one of these files override later ones. If this variable is not set,\nthe following default path is used:\n\n$HOME/.mime.types:/etc/mime.types:\\\n/usr/etc/mime.types:/usr/local/etc/mime.types\n\n\n\nMAILCAPS\nA list of files to be searched for mailcap entries, as defined by RFC 1343. See this\nRFC or the mailcap(4) manual page for a detailed description of the mailcap file for‐\nmat. Currently, only the following mailcap features are supported:\n\ntest=command\nThe entry is only used if command can be executed via the system() call and if\nthe system() call returns with value 0 (success). The command string may con‐\ntain the format string %s, which will be replaced by the file name.\n\nneedsterminal\nIf this flag is used, the command will be executed in a new xterm window by\nprepending ``xterm -e '' to the command string.\n\nAll other fields in the mailcap entry are ignored by xdvi. Earlier entries in one of\nthese files override later ones. If the variable is not defined, the following de‐\nfault path is used:\n\n$HOME/.mailcap:/etc/mailcap:/usr/etc/mailcap:\\\n/usr/local/etc/mailcap\n\nFor security reasons, some special characters (i.e. ( ) ` \\ ;) are escaped in the ar‐\ngument before passing it to system().\n\nBROWSER\nDetermines the web browser used to open external links (i.e. all URLs that don't start\nwith the `file:' scheme and are not relative links in the local DVI file), and to open\nlinks for which no viewer has been specified in the mailcap files. The value of this\nvariable is a colon-separated list of commands. Xdvi will try each of them in sequence\nuntil one succeeds (i.e. doesn't immediately return with status 0). This allows you to\nspecify your favourite browser at the beginning, and fallback browsers at the end.\nEvery occurrence of %s in the string is replaced by the target URL; every occurrence\nof %% is replaced by a single %. If no %s is present, the URL string is added as an\nextra argument.\nAn example setting is:\n\nnetscape -raise -remote 'openURL(%s,new-window)':xterm -e lynx %s:xterm -e wget\n%s:lynx %s:wget %s\n\nSee\n\nhttp://www.catb.org/~esr/BROWSER/\n\nfor more details on the BROWSER environment variable.\n\nGSLIB A colon-separated list of directories to search for Fontmap files, etc., as used for\nGhostscript. It has the same meaning as it does when running Ghostscript. In xdvik,\nit is used when searching for font files when the map file does not give a file name\nfor the font (this should be quite rare). The command gs -h will list the default\nvalue that Ghostscript uses. See also the XDVIGSLIB environment variable (below).\n\nXDVIGSLIB\nThis has the same effect as GSLIB but affects only xdvi. Use this when you want to\nuse a different value for GSLIB when running xdvi, but use either the compiled-in de‐\nfault value or some other value when running Ghostscript. If both GSLIB and XD‐\nVIGSLIB are set, then xdvi uses XDVIGSLIB. To use the default value compiled in\nto xdvi while still retaining the ability to set GSLIB for use with Ghostscript, you\ncan set XDVIGSLIB to the empty string.\n\nTMPDIR The directory to use for storing temporary files created when uncompressing PostScript\nfiles.\n\nXEDITOR\nDetermines the editor command used for source special `reverse search', if neither the\n-editor command-line option nor the .editor resource are specified. See the de‐\nscription of the -editor command line option for details on the format.\n\nVISUAL Determines an editor to be opened in an xterm window if neither of -editor, .editor,\nor XEDITOR is specified.\n\nEDITOR Determines an editor to be opened in an xterm window if neither of -editor, .editor,\nXEDITOR or VISUAL is specified.\n\nWWWBROWSER\nObsolete; use BROWSER instead.\n", "subsections": [] }, "LIMITATIONS": { "content": "xdvi accepts many but not all types of PostScript specials accepted by dvips. For example,\nit accepts most specials generated by epsf and psfig. It does not, however, support bop-hook\nor eop-hook, nor does it allow PostScript commands to affect the rendering of things that are\nnot PostScript (for example, the ``NEAT'' and rotated ``A'' examples in the dvips manual).\nThese restrictions are due to the design of xdvi; in all likelihood they will always remain.\n\nLaTeX2e rotation specials are currently not supported.\n\nMetaPost files containing included text are not supported.\n\nXdvi's color handling doesn't support the \\colorbox and \\fcolorbox macros; this is not like‐\nly to change in the near future. This also means that e.g. colored tables (as created by the\ncolortbl package) may render incorrectly: Text in colors different from the default fore‐\nground color may not be displayed. When the page is redrawn (e.g. after using the magnifier),\nthe background color of the cells may overdraw the text.\n", "subsections": [] }, "FILES": { "content": "", "subsections": [ { "name": "$HOME/.xdvirc", "content": "A file that holds all settings that the user changed via the keys, the `Options' and\nthe Xaw `Modes' menu and the dialogs, as X resources. These resources override the\nsettings in $HOME/.Xdefaults. This file is ignored if the -q option is used or the\nnoInitFile X resource is set.\n" }, { "name": "config.xdvi", "content": "An optional configuration file for the Type 1 font setup, which specifies dvips-style\nmap files specific to xdvik. If used, it should be present in the directory deter‐\nmined by the TEXCONFIG environment variable. Its format is similar to configuration\nfiles for dvips, except that it is only scanned for the names of map files (p and p+\ndirectives).\n" } ] }, "SEE ALSO": { "content": "X(1), dvips(1), mktexpk(1), ps2pk(1), gsftopk(1), t1mapper(1), mailcap(4), the Kpathsea docu‐\nmentation, https://ctan.org/pkg/xdvi/, and the Xdvik home page at http://xdvi.source‐\nforge.net/.\n", "subsections": [] }, "AUTHORS": { "content": "Eric Cooper, CMU, did a version for direct output to a QVSS. Modified for X by Bob Scheifler,\nMIT Laboratory for Computer Science. Modified for X11 by Mark Eichin, MIT SIPB. Additional\nenhancements by many others.\n\nThe current maintainer of the original xdvi is Paul Vojta, U.C. Berkeley.\n\nCode for the xdvik variant has been contributed by many people, whose names are scattered\nacross the source files.\n\nFor the most up-to-date information, please visit:\n", "subsections": [ { "name": "http://xdvi.sourceforge.net", "content": "Please report all bugs to the SourceForge bug tracker:\n" }, { "name": "http://sourceforge.net/tracker/?func=add&group_id=23164&atid=377580", "content": "Xdvik 22.87.06 2022-02-17 XDVI(1)" } ] } }, "summary": "xdvi - DVI Previewer for the X Window System", "flags": [ { "flag": "", "long": null, "arg": null, "description": "(.allowShell) This option enables the shell escape in PostScript specials. (For secu‐ rity reasons, shell escapes are disabled by default.) This option should be rarely used; in particular it should not be used just to uncompress files: that function is done automatically if the file name ends in .Z, .gz, or .bz2. Shell escapes are al‐ ways turned off if the -safer option is used." }, { "flag": "", "long": null, "arg": null, "description": "(.altFont) Declares a default font to use when the font in the dvi file cannot be found. This is useful, for example, with PostScript fonts." }, { "flag": "", "long": null, "arg": null, "description": "Jump to anchor after opening the DVI file. This is only useful when invoking xdvi from other applications." }, { "flag": "", "long": null, "arg": null, "description": "(.background) Determines the color of the background. Same as -bg." }, { "flag": "", "long": null, "arg": null, "description": "(.background) Determines the color of the background." }, { "flag": "", "long": null, "arg": null, "description": "(.wwwBrowser) Defines the web browser used for handling external URLs. The value of this option or resource has the same syntax as the BROWSER environment variable; see the explanation of that variable in the section `ENVIRONMENT' below for a detailed de‐ scription. If neither the option nor the X resource wwwBrowser is specified, the en‐ vironment variables BROWSER and WWWBROWSER (in that order) are used to determine the browser command. If these are not set either, the following default value is used: xdg-open %s:htmlview %s:firefox -remote -remote \"openURL(%s,new-window)\":mozilla -re‐ mote \"openURL(%s,new-window)\":netscape -raise -remote \"openURL(%s,new-window)\":xterm -e w3m %s:xterm -e lynx %s:xterm -e wget %s" }, { "flag": "", "long": null, "arg": null, "description": "option may be necessary for correct operation on a color display, but overstrike char‐ acters will be incorrect. If greyscale anti-aliasing is in use, the -copy operation will disable the use of colorplanes and make overstrikes come out incorrectly. See also -thorough." }, { "flag": "", "long": null, "arg": null, "description": "(.cursorColor) Determines the color of the mouse cursor. The default is the same as the foreground color." }, { "flag": "", "long": null, "arg": null, "description": "(.debugLevel) If nonzero, prints additional information on standard output. The argu‐ ment can be either a bitmask specified as a decimal number, or comma-separated list of strings. For the bitmask representation, multiple values can be specified by adding the numbers that represent the individual bits; e.g. to debug all file searching and opening com‐ mands, use 4032 (= 2048 + 1024 + 512 + 256 + 128 + 64). Use -1 to turn on debugging of everything (this will produce huge output). For the string representation, use the strings listed in the following table, with a comma to separate the values; e.g. to debug all file searching and opening commands, use search,expand,paths,hash,stat,open. (The option `kpathsea' is provided as a shorthand for these.) Note that such a list may need to be quoted to prevent the shell from interpreting commas or spaces in the list. The individual numbers and strings have the following meanings: 1 bitmap Bitmap creation 2 dvi DVI translation 4 pk PK fonts 8 batch Batch mode: Exit after reading the DVI file 16 event Event handling 32 ps PostScript interpreter calls 64 stat Kpathsea stat(2) calls 128 hash Kpathsea hash table lookups 256 open Kpathsea file opening 512 paths Kpathsea path definitions 1024 expand Kpathsea path expansion 2048 search Kpathsea searching 4032 kpathsea All Kpathsea options 4096 htex Hypertex specials 8192 src Source specials 16384 client Client/server mode (see -unique and -sourceposition options) 32768 ft FreeType library messages (Type 1 fonts) 65536 ftverbose Verbose FreeType library messages (currently unused) 131072 gui GUI elements 262144 find Searching for strings in the DVI file 524288 files File history and opening DVI files Some of the Kpathsea debugging options are actually provided by Kpathsea; see the De‐ bugging section in the Kpathsea manual for more information on these." }, { "flag": "", "long": null, "arg": null, "description": "(.densityPercent) Determines the density used when shrinking bitmaps for fonts. A higher value produces a lighter font. The default value is 40. If greyscaling is in use, this argument does not apply; use -gamma instead. See also the `S' keystroke. Same as -S." }, { "flag": "", "long": null, "arg": null, "description": "Specifies the host and screen to be used for displaying the dvi file. By default this is obtained from the environment variable DISPLAY." }, { "flag": "", "long": null, "arg": null, "description": "(.dvipsPath) Use path as the dvips program to use when printing. The default for this is dvips. The program or script should read the DVI file from standard input, and write the PostScript file to standard output." }, { "flag": "", "long": null, "arg": null, "description": "(.editor) Specifies the editor that will be invoked when the source-special() action is triggered to start a reverse search (by default via Ctrl-Mouse 1). The argument to this option is a format string in which occurrences of ``%f'' are replaced by the file name, occurrences of ``%l'' are replaced by the line number within the file, and op‐ tional occurrences of ``%c'' are replaced by the column number within the line. If neither the option nor the X resource .editor is specified, the following environ‐ ment variables are checked to determine the editor command: XEDITOR, VISUAL, and EDI‐ TOR (in this sequence). If the string is found as the value of the VISUAL or EDITOR environment variables, then ``xterm -e '' is prepended to the string; if the editor is specified by other means, then it must be in the form of a shell command to pop up an X window with an editor in it. If none of these variables is set, a warning message is displayed and the command ``xterm -e vi +%l %f'' is used. If no ``%f'' or ``%l'' occurs in the string, the missing format strings are appended automatically. (This is for compatibility with other programs when using one of the environment variables). A new instance of the editor is started each time this command is used; therefore it is preferable to use an editor that can be invoked in `client' mode to load new files into the same instance. Example settings are: emacsclient --no-wait (older Emacsen) gnuclient -q (XEmacs and newer Emacsen) gvim --servername xdvi --remote (VIM v6.0+; the `--servername xdvi' option will cause gvim to run a dedicated instance for the files opened by xdvi.)" }, { "flag": "", "long": null, "arg": null, "description": "This option is only supported for backwards compatibility; it is equivalent to -ex‐ pertmode 0, which should be preferred." }, { "flag": "", "long": null, "arg": null, "description": "(.expertMode) With an argument of 0, this option switches off the display of the but‐ tons, scrollbars, the toolbar (Motif only), the statusline and the page list. These GUI elements can also be (de)activated separately, by combining the appropriate values in the flag argument. This acts similar to the -debug option: The integer flag is treated as a bitmap where each bit represents one element. If the bit has the value 1, the element is switched on, if it has the value 0, the element is switched off. The meaning of the bits is as follows: 1 statusline 2 scrollbars 4 Motif: pagelist, Xaw: buttons and pagelist 8 toolbar (Motif only) 16 menubar (Motif only) For example, to turn on only the statusline and the scrollbars, use 3 (= 1 + 2). See also the `x' keystroke, where the bits are addressed by their positions, from 1 to 3 (Xaw) or 5 (Motif), respectively. If the statusline is not active, all messages that would normally be printed to the sta‐ tusline will be printed to stdout, unless the -hushstdout option is used." }, { "flag": "", "long": null, "arg": null, "description": "(.foreground) Determines the color of the text (foreground)." }, { "flag": "", "long": null, "arg": null, "description": "This option triggers a search for string in the DVI file mentioned on the command- line, similar to forward search (see the description of the sourceposition option): If there is already another instance of xdvi running on the displaying that DVI file, it will cause that instance to perform the search instead. The search starts at the top of the current page of the DVI file." }, { "flag": "", "long": null, "arg": null, "description": "(*font) Sets the font used in menus, buttons etc., as described in the X(7x) man page. The font for child windows can be set separately, e.g.: xdvi*statusline*font: \\ -*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*" }, { "flag": "", "long": null, "arg": null, "description": "Same as -fg." }, { "flag": "", "long": null, "arg": null, "description": "When this option is used, xdvi will (try to) run in fullscreen mode, with no window decorations. This option is not guaranteed to work with all windowmanagers/desktops; if you're experiencing problems with it, please use the -geometry option instead, and a suitable window manager setting to remove the window decorations. When using this option for presentations, you might want to get rid of all the control widgets as well, using the -expertmode option. This option can also be toggled at runtime using the fullscreen action (by default bound to Ctrl-l)." }, { "flag": "", "long": null, "arg": null, "description": "(.gamma) Controls the interpolation of colors in the greyscale anti-aliasing color palette. Default value is 1.0. For 0 < gamma < 1, the fonts will be lighter (more like the background), and for gamma > 1, the fonts will be darker (more like the fore‐ ground). Negative values behave the same way, but use a slightly different algorithm. For color and grayscale displays; for monochrome, see -density. See also the `S' key‐ stroke." }, { "flag": "", "long": null, "arg": null, "description": "(.geometry) Specifies the initial geometry of the main window, as described in the X(7x) man page. The geometry of child windows can be set separately, e.g.: xdvi*helpwindow.geometry: 600x800" }, { "flag": "", "long": null, "arg": null, "description": "(.gsAlpha) Causes Ghostscript to be called with the x11alpha driver instead of the x11 driver. The x11alpha driver enables anti-aliasing in PostScript specials, for a nicer appearance. It is available on newer versions of Ghostscript. This option can also be toggled with the `V' keystroke." }, { "flag": "", "long": null, "arg": null, "description": "(.palette) Specifies the palette to be used when using Ghostscript for rendering Post‐ Script specials. Possible values are Color, Greyscale, and Monochrome. The default is Color." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Prints a short help text with an overview of the command-line options to standard out‐ put." }, { "flag": "", "long": null, "arg": null, "description": "(.highlight) Determines the color of the page border, of the ruler in `ruler mode', and of the highlighting markers in forward search and string search. The default is the foreground color." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "(.hushBell) Don't sound the X bell when an error occurs." }, { "flag": "", "long": null, "arg": null, "description": "(.hushLostChars) Causes xdvi to suppress warnings about references to characters which are not defined in the font." }, { "flag": "", "long": null, "arg": null, "description": "(.hushChecksums) Causes xdvi to suppress warnings about checksum mismatches between the dvi file and the font file." }, { "flag": "", "long": null, "arg": null, "description": "(.hushStdout) Suppresses printing of status messages to stdout. Note that errors or warnings will still be printed to stderr even if this option is used." }, { "flag": "", "long": null, "arg": null, "description": "(.iconGeometry) Specifies the initial position for the icon." }, { "flag": "", "long": null, "arg": null, "description": "(.iconic) Causes the xdvi window to start in the iconic state. The default is to start with the window open." }, { "flag": "", "long": null, "arg": null, "description": "(.install) If xdvi is running under a PseudoColor visual, then (by default) it will check for TrueColor visuals with more bits per pixel, and switch to such a visual if one exists. If no such visual exists, it will use the current visual and colormap. If -install is selected, however, it will still use a TrueColor visual with a greater depth, if one is available; otherwise, it will install its own colormap on the current visual. If the current visual is not PseudoColor, then xdvi will not switch the visu‐ al or colormap, regardless of its options. The default value of the install resource is the special value, maybe. There is no +install option. See also -noinstall, and the GREYSCALING AND COLORMAPS section." }, { "flag": "", "long": null, "arg": null, "description": "(.interpreter) Use filename as the Ghostscript interpreter. By default it uses gs." }, { "flag": "", "long": null, "arg": null, "description": "when moving to a new page. See also the `k' keystroke. This flag is honored by all page switching actions and by up-or-previous() / down-or-next(), although the latter only honor the horizontal position, not the vertical one. This allows for a \"continu‐ ous\" scrolling back an forth through a document with a display window narrower than a page width." }, { "flag": "-l", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "Prints licensing information." }, { "flag": "", "long": null, "arg": null, "description": "(.linkColor) Color used for unvisited hyperlinks (`Blue2' by default). Hyperlinks are unvisited before you click on them, or after the DVI file has been reloaded. The val‐ ue should be either a valid X color name (such as DarkGoldenrod4) or a hexadecimal color string (such as #8b6508). See also -visitedlinkcolor and -linkstyle." }, { "flag": "", "long": null, "arg": null, "description": "(.LinkStyle) Determines the style in which hyperlinks are displayed. Possible values and their meanings are: 0 No highlighting of links 1 Underline links with link color 2 No underlining, color text with link color 3 Underline and display text colored with link color The values for link color are specified by the options/resources -linkcolor and -vis‐ itedlinkcolor (which see)." }, { "flag": "", "long": null, "arg": null, "description": "(.Margin) Specifies the size of both the top margin and side margin. This determines the ``home'' position of the page within the window as follows. If the entire page fits in the window, then the margin settings are ignored. If, even after removing the margins from the left, right, top, and bottom, the page still cannot fit in the win‐ dow, then the page is put in the window such that the top and left margins are hidden, and presumably the upper left-hand corner of the text on the page will be in the upper left-hand corner of the window. Otherwise, the text is centered in the window. The dimension should be a decimal number optionally followed by any of the two-letter ab‐ breviations for units accepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By de‐ fault, the unit will be cm (centimeters). See also -sidemargin, -topmargin, and the keystroke `M.'" }, { "flag": "", "long": null, "arg": null, "description": "(.mfMode) Specifies a mode-def string, which can be used in searching for fonts (see ENVIRONMENT, below). Generally, when changing the mode-def, it is also necessary to change the font size to the appropriate value for that mode. This is done by adding a colon and the value in dots per inch; for example, -mfmode ljfour:600. This method overrides any value given by the pixelsPerInch resource or the -p command-line argu‐ ment. The metafont mode is also passed to metafont during automatic creation of fonts. By default, it is unspecified." }, { "flag": "", "long": null, "arg": null, "description": "Same as -mgs1." }, { "flag": "", "long": null, "arg": null, "description": "(.magnifierSize[n]) Specifies the size of the window to be used for the ``magnifying glass'' for Button n. The size may be given as an integer (indicating that the magni‐ fying glass is to be square), or it may be given in the form widthxheight. See the MOUSE ACTIONS section. Defaults are 200x150, 400x250, 700x500, 1000x800, and 1200x1200." }, { "flag": "", "long": null, "arg": null, "description": "(.mouseMode) Specifies the default mode of xdvi at startup: Magnifier (0), Text Selec‐ tion Mode (1) or Ruler Mode (2). See the section MODES, below, for more information." }, { "flag": "", "long": null, "arg": null, "description": "(.color) Turns off the use of color specials. This option can be toggled with the `C' keystroke. (Note: -nocolor corresponds to color:off; +nocolor to color:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.fork) With the -sourceposition and -unique options, the default behavior is for xdvi to put itself into the background (like a daemon) if there is no appropriate instance of xdvi already running. This argument makes it run in the foreground instead. This is useful for debugging, or if your client application cannot deal well with a program self-backgrounding itself in this way -- e.g. the IPC functions in emacs are known to have problems with this. If no -sourceposition or -unique argument is given, then this option has no effect. (Note: -nofork corresponds to fork:off; +nofork to fork:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.ghostscript) Inhibits the use of Ghostscript for displaying PostScript specials. (Note: -noghostscript corresponds to ghostscript:off; +noghostscript to ghost‐ script:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.grey) Turns off the use of greyscale anti-aliasing when printing shrunken bitmaps. (Note: -nogrey corresponds to grey:off; +nogrey to grey:on.) See also the `G' key‐ stroke." }, { "flag": "", "long": null, "arg": null, "description": "(.gsSafer) Normally, if Ghostscript is used to render PostScript specials, the Ghost‐ script interpreter is run with the option -dSAFER. The -nogssafer option runs Ghost‐ script without -dSAFER. The -dSAFER option in Ghostscript disables PostScript opera‐ tors such as deletefile, to prevent possibly malicious PostScript programs from having any effect. If the -safer option is specified, then this option has no effect; in that case Ghostscript is always run with -dSAFER. (Note: -nogssafer corresponds to gsSafer:off; +nogssafer to gsSafer:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.install) Inhibit the default behavior of switching to a TrueColor visual if one is available with more bits per pixel than the current visual. (Note: -noinstall corre‐ sponds install:off; there is no +noinstall option.) See also -install, and the GREYSCALING AND COLORMAPS section." }, { "flag": "", "long": null, "arg": null, "description": "(.makePk) Turns off automatic generation of font files that cannot be found by other means. (Note: -nomakepk corresponds to makePk:off; +nomakepk to makePK:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.matchInverted) Don't highlight string search matches in inverted color; instead, draw a rectangle in highlight color (see the -hl option) around the match. This option is activated automatically if the display isn't running in TrueColor. (Note: -no‐ matchinverted corresponds to matchInverted:off; +nomatchinverted to matchInverted:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.omega) This will disable the use of Omega extensions when interpreting DVI files. By default, the additional opcodes 129 and 134 are recognized by xdvi as Omega exten‐ sions and interpreted as requests to set 2-byte characters. The only drawback is that the virtual font array will require 65536 positions instead of the default 256 posi‐ tions, i.e. the memory requirements of xdvi will be slightly larger. If you find this unacceptable or encounter another problem with the Omega extensions, you can switch this extension off by using -noomega (but please do send a bug report if you find such problems - see the bug address in the AUTHORS section below). (Note: -noomega corresponds to omega: off; +noomega to omega: on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.prescan) By default, xdvi does a preliminary scan of the dvi file to process any pa‐ persize specials; this is especially important at startup since the paper size may be needed to determine the window size. If PostScript is in use, then prescanning is also necessary in order to properly process header files. In addition, prescanning is needed to correctly determine the background color of a page. This option turns off such prescanning. (Prescanning will be automatically be turned back on if xdvi de‐ tects any of the specials mentioned above.) (Note: -noscan corresponds to pres‐ can:off; +noscan to prescan:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.tempFile) As mentioned in the section DESCRIPTION above, xdvi will create a tempo‐ rary copy of the DVI file so that it can be accessed without interruptions even while the file is being rewritten by TeX. Since this introduces the overhead of copying the file every time it has changed, the -notempfile allows you to turn off this behaviour. In this case, exposing parts of the window while the DVI file is being written by TeX will erase the current window contents until the DVI file can be completely reread. (Note: -notempfile corresponds to tempFile:off; +notempfile to tempFile:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.type1) This will disable the use of the FreeType library to display PostScript Type 1 fonts. Use this option as a workaround when you encounter problems with the display of Type 1 fonts (but please don't forget to send a bug report in this case, to the URL mentioned in the section AUTHORS below). (Note: -notype1fonts corresponds to type1:off; +notype1fonts to type1:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.xi2Scrolling) This will disable the use of high-resolution scrolling using the XIn‐ put 2.1 features of the X Server. When enabled, horizontal and vertical scrolling is done in smaller increments than would correspond to a single click of a mouse wheel. This is only available for hardware that supports the feature, generally touchpads. It is not available for traditional wheel mice. If suitable hardware is not present or if the X server does not support XInput 2.1 or higher, then the high-resolution scrolling feature is turned off and has no effect. (Note: -noxi2scrolling corresponds to xi2Scrolling:off; +noxi2scrolling, to xi2Scrolling:on.)" }, { "flag": "", "long": null, "arg": null, "description": "(.Offset) Specifies the size of both the horizontal and vertical offsets of the output on the page. By decree of the Stanford TeX Project, the default TeX page origin is always 1 inch over and down from the top-left page corner, even when non-American pa‐ per sizes are used. Therefore, the default offsets are 1.0 inch. The argument dimen should be a decimal number optionally followed by any of the two-letter abbreviations for units accepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By default, the unit will be cm (centimeters). See also -xoffset and -yoffset." }, { "flag": "-p", "long": null, "arg": null, "description": "(.pixelsPerInch) Defines the size of the fonts to use, in pixels per inch. The de‐ fault value is 600. This option is provided only for backwards compatibility; the preferred way is to set both the resolution and the Metafont mode via the -mfmode op‐ tion (which see)." }, { "flag": "", "long": null, "arg": null, "description": "(.paper) Specifies the size of the printed page. Note that in most cases it's best to specify the paper size in the TeX input file via the line \\usepackage[dvips]{geometry} which will be recognized by both dvips and xdvi; in that case the use of a `-paper' option should be unnecessary. The paper size may be specified in the form widthxheight optionally followed by a unit, where width and height are decimal numbers giving the width and height of the paper, respectively, and the unit is any of the two-letter abbreviations for units ac‐ cepted by TeX (pt, pc, in, bp, cm, mm, dd, cc, or sp). By default, the unit is cm (centimeters). There are also synonyms which may be used: us (8.5x11in), legal (8.5x14in), foolscap (13.5x17in), as well as the ISO sizes a1-a7, b1-b7, c1-c7. Each of these also has a landscape or `rotated' variant: usr (11x8.5in), a1r-a7r, etc. For compatibility with dvips, the formats letter (8.5x11in), ledger (17x11in) and tabloid (11x17in) are also supported (these don't have rotated variants). Any of the above sizes may be preceded by a plus sign (`+'); this causes the paper size given here to override any paper size given in the dvi file. The default paper size is 21 x 29.7 cm (A4 size)." }, { "flag": "", "long": null, "arg": null, "description": "play, which can be used for presentations. When this option is used, xdvi will pause the display of the current page whenever it encounters a special special-string (xd‐ vi:pause by default; the string can be customized via -pausespecial, see below), and the cursor will change its shape. The action unpause-or-next() (by default bound to the Space key) will display the next portion of the page up to the following special- string, or until the end of the page is reached. When the option is not used, spe‐ cials containing special-string will be ignored." }, { "flag": "", "long": null, "arg": null, "description": "(.pauseSpecial) Sets the special string that causes xdvi to pause when the -pause op‐ tion is active. The default value of special-string is xdvi:pause." }, { "flag": "", "long": null, "arg": null, "description": "(.postscript) If flag = 0, rendering of PostScript specials is disabled; instead, bounding boxes will be displayed (if available). A value of 1 (the default) switches PostScript specials on. With a value of 2, the PostScript specials are dis‐ played along with their bounding boxes; this allows you to visually check the correct‐ ness of the bounding boxes. The values can also be toggled at runtime with the `v' keystroke and the corresponding numerical prefix arguments 0, 1 and 2." }, { "flag": "", "long": null, "arg": null, "description": "(.ps2pdfPath) Use path as a conversion program from PostScript to PDF. The program or script should accept two command-line arguments: The PostScript file as first argu‐ ment, and the PDF output file as second argument." }, { "flag": "", "long": null, "arg": null, "description": "(.ruleColor) Determines the color of the rules used for the magnifier (default: fore‐ ground color)." }, { "flag": "-q", "long": null, "arg": null, "description": "and don't write it at exit). This forces the defaults defined in $HOME/.Xdefaults to be used. See FILES for more information on $HOME/.xdvirc." }, { "flag": "", "long": null, "arg": null, "description": "ground, instead of vice versa." }, { "flag": "-S", "long": null, "arg": null, "description": "(.densityPercent) Same as -density (which see)." }, { "flag": "-s", "long": null, "arg": null, "description": "(.shrinkFactor) Defines the initial shrink factor. The default value is 8. If shrink is given as 0, then the initial shrink factor is computed so that the page fits within the window (as if the `s' keystroke were given without a number)." }, { "flag": "", "long": null, "arg": null, "description": "when xdvi is called by a browser that obtains a dvi or TeX file from another site. This option selects +nogssafer and +allowshell." }, { "flag": "", "long": null, "arg": null, "description": "(.sideMargin) Specifies the side margin (see -margins)." }, { "flag": "", "long": null, "arg": null, "description": "This option makes xdvi search in the dvi file for the place corresponding to the indi‐ cated line (and, optionally, column) in the .tex source file, and highlight the place found by drawing a rectangle in the highlight color (see the -hl option) around the corresponding text. In addition, when run with this argument (and the -nofork option is not given, which see), xdvi will always return immediately: if it finds another instance of xdvi already showing dvifile, then it will cause that instance to raise its window and move to the given place in the dvi file; otherwise it will start up its own instance in the background. If several instances of xdvi are displaying the re‐ spective dvi file, the instance which was last raised to the foreground will be used. The space before filename is only needed if the filename starts with a digit. When the space is used, the argument needs to be enclosed in quotes to prevent the shell from misinterpreting the space as argument separator. This option requires that dvifile be prepared with source special information. See the section on SOURCE SPECIALS for details on how to do this. Here is a more detailed description of how the filename in the -sourceposition argu‐ ment is matched with the filename in the source specials: 1. If neither of the filenames contains a path name component, the filenames are com‐ pared ignoring the `.tex' extensions in both filenames. 2. Otherwise, if one of the filenames does contain a path component (e.g.: ./test.tex, ../test.tex, /my/homedir/tex/test.tex or any combination of these), both filenames are expanded to a full path, with any occurrences of ../ and ./ expanded, and mul‐ tiple slashes removed. The pathname in the -sourceposition is expanded relative to the current working di‐ rectory of the xdvi -sourceposition invocation, and the pathnames in the source specials are expanded relative to the path of the current DVI file being viewed. The path names are then compared ignoring the `.tex' extensions in both path names." }, { "flag": "", "long": null, "arg": null, "description": "(.statusline) This option is obsolete; use -expertmode flag instead (which see)." }, { "flag": "", "long": null, "arg": null, "description": "(.textEncoding) Use encoding as the text encoding of the string in the \"Find\" window. Usually, this should not be needed since the encoding is determined from the locale settings." }, { "flag": "", "long": null, "arg": null, "description": "(.thorough) Xdvi will usually try to ensure that overstrike characters (e.g. \\notin) are printed correctly. On monochrome displays, this is always possible with one logi‐ cal operation, either and or or. On color displays, however, this may take two opera‐ tions, one to set the appropriate bits and one to clear other bits. If this is the case, then by default xdvi will instead use the copy operation, which does not handle overstriking correctly. The -thorough option chooses the slower but more correct choice. See also -copy." }, { "flag": "", "long": null, "arg": null, "description": "(.topMargin) Specifies the top and bottom margins (see -margins)." }, { "flag": "", "long": null, "arg": null, "description": "(.unique) This option will make another instance of xdvi running on the same display act as a `server'. For example, the invocation xdvi -unique +5 file.dvi will cause this other instance to load file.dvi on page 5 in place of the file that it is currently displaying. If there is already another instance of xdvi already display‐ ing the file file.dvi, then it will just jump to page 5. If the other instance of xd‐ vi is displaying a different file, it will load file.dvi instead. Otherwise, if no other instance of xdvi is currently running on the display, this option instead starts a new instance of xdvi in the background (unless the -nofork option is specified, which see) displaying page 5 of file.dvi. The filename and the +n option for the page number are the only options available for controlling a remote instance of xdvi like this; all other options are currently ig‐ nored." }, { "flag": "", "long": null, "arg": null, "description": "Use logical TeX pages (the values of the \\count0 register) instead of physical pages for the pagelist labels and when jumping to a page in a document with the `g' key‐ stroke (or the goto-page() action). This option can be toggled via the `T' keystroke." }, { "flag": "", "long": null, "arg": null, "description": "Print information on the version of xdvi." }, { "flag": "", "long": null, "arg": null, "description": "(.visitedLinkColor) Color used for visited hyperlinks (`Purple4' by default). Hyper‐ links become visited once you click on them. As for linkColor, the value should be ei‐ ther a valid X color name or a hexadecimal color string." }, { "flag": "", "long": null, "arg": null, "description": "(.warnSpecials) Causes xdvi to print warnings about \\special strings that it cannot process to stderr. These warnings are suppressed by default." }, { "flag": "", "long": null, "arg": null, "description": "(.watchFile) If this option is set to a value larger than 0, xdvi will check the DVI file for changes every n seconds. If the DVI file has been completely written by TeX, it will be reloaded automatically. Fractional values (e.g. `2.5') are possible. The default for this option is 0, i.e. no watching. Since xdvi cannot handle partial DVI files, it tries not to reload the file while it is being rewritten. However, use of the magnifier or switching of pages requires reading (a part of) the DVI file, and if the tempfile option is switched off, this will erase the current contents of the window until the DVI file can be read entirely." }, { "flag": "", "long": null, "arg": null, "description": "(.wheelUnit) Sets the number of pixels that a motion of a wheel mouse will move the image up, down, left, or right. (See the wheel and hwheel actions, below, for more in‐ formation on this.) If set to zero, the wheel mouse functionality is (essentially) disabled. The default value is 80." }, { "flag": "", "long": null, "arg": null, "description": "(.xOffset) Specifies the size of the horizontal offset of the output on the page. See -offsets." }, { "flag": "", "long": null, "arg": null, "description": "(.yOffset) Specifies the size of the vertical offset of the output on the page. See -offsets." } ], "examples": [], "see_also": [ { "name": "X", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/X/1/json" }, { "name": "dvips", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/dvips/1/json" }, { "name": "mktexpk", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/mktexpk/1/json" }, { "name": "ps2pk", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/ps2pk/1/json" }, { "name": "gsftopk", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/gsftopk/1/json" }, { "name": "t1mapper", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/t1mapper/1/json" }, { "name": "mailcap", "section": "4", "url": "https://www.chedong.com/phpMan.php/man/mailcap/4/json" } ] }