Vim documentation: term
main help file*term.txt* For Vim version 7.2. Last change: 2008 Jun 21 VIM REFERENCE MANUAL by Bram Moolenaar Terminal information *terminal-info* Vim uses information about the terminal you are using to fill the screen and recognize what keys you hit. If this information is not correct, the screen may be messed up or keys may not be recognized. The actions which have to be performed on the screen are accomplished by outputting a string of characters. Special keys produce a string of characters. These strings are stored in the terminal options, see |terminal-options|. NOTE: Most of this is not used when running the |GUI|. 1. Startup |startup-terminal| 2. Terminal options |terminal-options| 3. Window size |window-size| 4. Slow and fast terminals |slow-fast-terminal| 5. Using the mouse |mouse-using|
1. Startup *startup-terminal* When Vim is started a default terminal type is assumed. For the Amiga this is a standard CLI window, for MS-DOS the pc terminal, for Unix an ansi terminal. A few other terminal types are always available, see below |builtin-terms|. You can give the terminal name with the '-T' Vim argument. If it is not given Vim will try to get the name from the TERM environment variable. *termcap* *terminfo* *E557* *E558* *E559* On Unix the terminfo database or termcap file is used. This is referred to as "termcap" in all the documentation. At compile time, when running configure, the choice whether to use terminfo or termcap is done automatically. When running Vim the output of ":version" will show |+terminfo| if terminfo is used. Also see |xterm-screens|. On non-Unix systems a termcap is only available if Vim was compiled with TERMCAP defined. *builtin-terms* *builtin_terms* Which builtin terminals are available depends on a few defines in feature.h, which need to be set at compile time: define output of ":version" terminals builtin NO_BUILTIN_TCAPS -builtin_terms none SOME_BUILTIN_TCAPS +builtin_terms most common ones (default) ALL_BUILTIN_TCAPS ++builtin_terms all available You can see a list of available builtin terminals with ":set term=xxx" (when not running the GUI). Also see |+builtin_terms|. If the termcap code is included Vim will try to get the strings for the terminal you are using from the termcap file and the builtin termcaps. Both are always used, if an entry for the terminal you are using is present. Which one is used first depends on the 'ttybuiltin' option: 'ttybuiltin' on 1: builtin termcap 2: external termcap 'ttybuiltin' off 1: external termcap 2: builtin termcap If an option is missing in one of them, it will be obtained from the other one. If an option is present in both, the one first encountered is used. Which external termcap file is used varies from system to system and may depend on the environment variables "TERMCAP" and "TERMPATH". See "man tgetent". Settings depending on terminal *term-dependent-settings* If you want to set options or mappings, depending on the terminal name, you can do this best in your .vimrc. Example: if &term == "xterm" ... xterm maps and settings ... elseif &term =~ "vt10." ... vt100, vt102 maps and settings ... endif *raw-terminal-mode* For normal editing the terminal will be put into "raw" mode. The strings defined with 't_ti' and 't_ks' will be sent to the terminal. Normally this puts the terminal in a state where the termcap codes are valid and activates the cursor and function keys. When Vim exits the terminal will be put back into the mode it was before Vim started. The strings defined with 't_te' and 't_ke' will be sent to the terminal. On the Amiga, with commands that execute an external command (e.g., "!!"), the terminal will be put into Normal mode for a moment. This means that you can stop the output to the screen by hitting a printing key. Output resumes when you hit <BS>. *cs7-problem* Note: If the terminal settings are changed after running Vim, you might have an illegal combination of settings. This has been reported on Solaris 2.5 with "stty cs8 parenb", which is restored as "stty cs7 parenb". Use "stty cs8 -parenb -istrip" instead, this is restored correctly. Some termcap entries are wrong in the sense that after sending 't_ks' the cursor keys send codes different from the codes defined in the termcap. To avoid this you can set 't_ks' (and 't_ke') to empty strings. This must be done during initialization (see |initialization|), otherwise it's too late. Some termcap entries assume that the highest bit is always reset. For example: The cursor-up entry for the Amiga could be ":ku=\E[A:". But the Amiga really sends "\233A". This works fine if the highest bit is reset, e.g., when using an Amiga over a serial line. If the cursor keys don't work, try the entry ":ku=\233A:". Some termcap entries have the entry ":ku=\E[A:". But the Amiga really sends "\233A". On output "\E[" and "\233" are often equivalent, on input they aren't. You will have to change the termcap entry, or change the key code with the :set command to fix this. Many cursor key codes start with an <Esc>. Vim must find out if this is a single hit of the <Esc> key or the start of a cursor key sequence. It waits for a next character to arrive. If it does not arrive within one second a single <Esc> is assumed. On very slow systems this may fail, causing cursor keys not to work sometimes. If you discover this problem reset the 'timeout' option. Vim will wait for the next character to arrive after an <Esc>. If you want to enter a single <Esc> you must type it twice. Resetting the 'esckeys' option avoids this problem in Insert mode, but you lose the possibility to use cursor and function keys in Insert mode. On the Amiga the recognition of window resizing is activated only when the terminal name is "amiga" or "builtin_amiga". Some terminals have confusing codes for the cursor keys. The televideo 925 is such a terminal. It sends a CTRL-H for cursor-left. This would make it impossible to distinguish a backspace and cursor-left. To avoid this problem CTRL-H is never recognized as cursor-left. *vt100-cursor-keys* *xterm-cursor-keys* Other terminals (e.g., vt100 and xterm) have cursor keys that send <Esc>OA, <Esc>OB, etc. Unfortunately these are valid commands in insert mode: Stop insert, Open a new line above the new one, start inserting 'A', 'B', etc. Instead of performing these commands Vim will erroneously recognize this typed key sequence as a cursor key movement. To avoid this and make Vim do what you want in either case you could use these settings: :set notimeout " don't timeout on mappings :set ttimeout " do timeout on terminal key codes :set timeoutlen=100 " timeout after 100 msec This requires the key-codes to be sent within 100 msec in order to recognize them as a cursor key. When you type you normally are not that fast, so they are recognized as individual typed commands, even though Vim receives the same sequence of bytes. *vt100-function-keys* *xterm-function-keys* An xterm can send function keys F1 to F4 in two modes: vt100 compatible or not. Because Vim may not know what the xterm is sending, both types of keys are recognized. The same happens for the <Home> and <End> keys. normal vt100 <F1> t_k1 <Esc>[11~ <xF1> <Esc>OP *<xF1>-xterm* <F2> t_k2 <Esc>[12~ <xF2> <Esc>OQ *<xF2>-xterm* <F3> t_k3 <Esc>[13~ <xF3> <Esc>OR *<xF3>-xterm* <F4> t_k4 <Esc>[14~ <xF4> <Esc>OS *<xF4>-xterm* <Home> t_kh <Esc>[7~ <xHome> <Esc>OH *<xHome>-xterm* <End> t_@7 <Esc>[4~ <xEnd> <Esc>OF *<xEnd>-xterm* When Vim starts, <xF1> is mapped to <F1>, <xF2> to <F2> etc. This means that by default both codes do the same thing. If you make a mapping for <xF2>, because your terminal does have two keys, the default mapping is overwritten, thus you can use the <F2> and <xF2> keys for something different. *xterm-shifted-keys* Newer versions of xterm support shifted function keys and special keys. Vim recognizes most of them. Use ":set termcap" to check which are supported and what the codes are. Mostly these are not in a termcap, they are only supported by the builtin_xterm termcap. *xterm-modifier-keys* Newer versions of xterm support Alt and Ctrl for most function keys. To avoid having to add all combinations of Alt, Ctrl and Shift for every key a special sequence is recognized at the end of a termcap entry: ";*X". The "X" can be any character, often '~' is used. The ";*" stands for an optional modifier argument. ";2" is Shift, ";3" is Alt, ";5" is Ctrl and ";9" is Meta (when it's different from Alt). They can be combined. Examples: :set <F8>=^[[19;*~ :set <Home>=^[[1;*H Another speciality about these codes is that they are not overwritten by another code. That is to avoid that the codes obtained from xterm directly |t_RV| overwrite them. *xterm-scroll-region* The default termcap entry for xterm on Sun and other platforms does not contain the entry for scroll regions. Add ":cs=\E[%i%d;%dr:" to the xterm entry in /etc/termcap and everything should work. *xterm-end-home-keys* On some systems (at least on FreeBSD with XFree86 3.1.2) the codes that the <End> and <Home> keys send contain a <Nul> character. To make these keys send the proper key code, add these lines to your ~/.Xdefaults file: *VT100.Translations: #override \n\ <Key>Home: string("0x1b") string("[7~") \n\ <Key>End: string("0x1b") string("[8~") *xterm-8bit* *xterm-8-bit* Xterm can be run in a mode where it uses 8-bit escape sequences. The CSI code is used instead of <Esc>[. The advantage is that an <Esc> can quickly be recognized in Insert mode, because it can't be confused with the start of a special key. For the builtin termcap entries, Vim checks if the 'term' option contains "8bit" anywhere. It then uses 8-bit characters for the termcap entries, the mouse and a few other things. You would normally set $TERM in your shell to "xterm-8bit" and Vim picks this up and adjusts to the 8-bit setting automatically. When Vim receives a response to the |t_RV| (request version) sequence and it starts with CSI, it assumes that the terminal is in 8-bit mode and will convert all key sequences to their 8-bit variants.
2. Terminal options *terminal-options* *termcap-options* *E436* The terminal options can be set just like normal options. But they are not shown with the ":set all" command. Instead use ":set termcap" It is always possible to change individual strings by setting the appropriate option. For example: :set t_ce=^V^[[K (CTRL-V, <Esc>, [, K) {Vi: no terminal options. You have to exit Vi, edit the termcap entry and try again} The options are listed below. The associated termcap code is always equal to the last two characters of the option name. Only one termcap code is required: Cursor motion, 't_cm'. The options 't_da', 't_db', 't_ms', 't_xs' represent flags in the termcap. When the termcap flag is present, the option will be set to "y". But any non-empty string means that the flag is set. An empty string means that the flag is not set. 't_CS' works like this too, but it isn't a termcap flag. OUTPUT CODES option meaning t_AB set background color (ANSI) *t_AB* *'t_AB'* t_AF set foreground color (ANSI) *t_AF* *'t_AF'* t_AL add number of blank lines *t_AL* *'t_AL'* t_al add new blank line *t_al* *'t_al'* t_bc backspace character *t_bc* *'t_bc'* t_cd clear to end of screen *t_cd* *'t_cd'* t_ce clear to end of line *t_ce* *'t_ce'* t_cl clear screen *t_cl* *'t_cl'* t_cm cursor motion (required!) *E437* *t_cm* *'t_cm'* t_Co number of colors *t_Co* *'t_Co'* t_CS if non-empty, cursor relative to scroll region *t_CS* *'t_CS'* t_cs define scrolling region *t_cs* *'t_cs'* t_CV define vertical scrolling region *t_CV* *'t_CV'* t_da if non-empty, lines from above scroll down *t_da* *'t_da'* t_db if non-empty, lines from below scroll up *t_db* *'t_db'* t_DL delete number of lines *t_DL* *'t_DL'* t_dl delete line *t_dl* *'t_dl'* t_fs set window title end (from status line) *t_fs* *'t_fs'* t_ke exit "keypad transmit" mode *t_ke* *'t_ke'* t_ks start "keypad transmit" mode *t_ks* *'t_ks'* t_le move cursor one char left *t_le* *'t_le'* t_mb blinking mode *t_mb* *'t_mb'* t_md bold mode *t_md* *'t_md'* t_me Normal mode (undoes t_mr, t_mb, t_md and color) *t_me* *'t_me'* t_mr reverse (invert) mode *t_mr* *'t_mr'* *t_ms* *'t_ms'* t_ms if non-empty, cursor can be moved in standout/inverse mode t_nd non destructive space character *t_nd* *'t_nd'* t_op reset to original color pair *t_op* *'t_op'* t_RI cursor number of chars right *t_RI* *'t_RI'* t_Sb set background color *t_Sb* *'t_Sb'* t_Sf set foreground color *t_Sf* *'t_Sf'* t_se standout end *t_se* *'t_se'* t_so standout mode *t_so* *'t_so'* t_sr scroll reverse (backward) *t_sr* *'t_sr'* t_te out of "termcap" mode *t_te* *'t_te'* t_ti put terminal in "termcap" mode *t_ti* *'t_ti'* t_ts set window title start (to status line) *t_ts* *'t_ts'* t_ue underline end *t_ue* *'t_ue'* t_us underline mode *t_us* *'t_us'* t_Ce undercurl end *t_Ce* *'t_Ce'* t_Cs undercurl mode *t_Cs* *'t_Cs'* t_ut clearing uses the current background color *t_ut* *'t_ut'* t_vb visual bell *t_vb* *'t_vb'* t_ve cursor visible *t_ve* *'t_ve'* t_vi cursor invisible *t_vi* *'t_vi'* t_vs cursor very visible *t_vs* *'t_vs'* *t_xs* *'t_xs'* t_xs if non-empty, standout not erased by overwriting (hpterm) t_ZH italics mode *t_ZH* *'t_ZH'* t_ZR italics end *t_ZR* *'t_ZR'* Added by Vim (there are no standard codes for these): t_IS set icon text start *t_IS* *'t_IS'* t_IE set icon text end *t_IE* *'t_IE'* t_WP set window position (Y, X) in pixels *t_WP* *'t_WP'* t_WS set window size (height, width) in characters *t_WS* *'t_WS'* t_SI start insert mode (bar cursor shape) *t_SI* *'t_SI'* t_EI end insert mode (block cursor shape) *t_EI* *'t_EI'* |termcap-cursor-shape| t_RV request terminal version string (for xterm) *t_RV* *'t_RV'* |xterm-8bit| |v:termresponse| |'ttymouse'| |xterm-codes| KEY CODES Note: Use the <> form if possible option name meaning t_ku <Up> arrow up *t_ku* *'t_ku'* t_kd <Down> arrow down *t_kd* *'t_kd'* t_kr <Right> arrow right *t_kr* *'t_kr'* t_kl <Left> arrow left *t_kl* *'t_kl'* <xUp> alternate arrow up *<xUp>* <xDown> alternate arrow down *<xDown>* <xRight> alternate arrow right *<xRight>* <xLeft> alternate arrow left *<xLeft>* <S-Up> shift arrow up <S-Down> shift arrow down t_%i <S-Right> shift arrow right *t_%i* *'t_%i'* t_#4 <S-Left> shift arrow left *t_#4* *'t_#4'* t_k1 <F1> function key 1 *t_k1* *'t_k1'* <xF1> alternate F1 *<xF1>* t_k2 <F2> function key 2 *<F2>* *t_k2* *'t_k2'* <xF2> alternate F2 *<xF2>* t_k3 <F3> function key 3 *<F3>* *t_k3* *'t_k3'* <xF3> alternate F3 *<xF3>* t_k4 <F4> function key 4 *<F4>* *t_k4* *'t_k4'* <xF4> alternate F4 *<xF4>* t_k5 <F5> function key 5 *<F5>* *t_k5* *'t_k5'* t_k6 <F6> function key 6 *<F6>* *t_k6* *'t_k6'* t_k7 <F7> function key 7 *<F7>* *t_k7* *'t_k7'* t_k8 <F8> function key 8 *<F8>* *t_k8* *'t_k8'* t_k9 <F9> function key 9 *<F9>* *t_k9* *'t_k9'* t_k; <F10> function key 10 *<F10>* *t_k;* *'t_k;'* t_F1 <F11> function key 11 *<F11>* *t_F1* *'t_F1'* t_F2 <F12> function key 12 *<F12>* *t_F2* *'t_F2'* t_F3 <F13> function key 13 *<F13>* *t_F3* *'t_F3'* t_F4 <F14> function key 14 *<F14>* *t_F4* *'t_F4'* t_F5 <F15> function key 15 *<F15>* *t_F5* *'t_F5'* t_F6 <F16> function key 16 *<F16>* *t_F6* *'t_F6'* t_F7 <F17> function key 17 *<F17>* *t_F7* *'t_F7'* t_F8 <F18> function key 18 *<F18>* *t_F8* *'t_F8'* t_F9 <F19> function key 19 *<F19>* *t_F9* *'t_F9'* <S-F1> shifted function key 1 <S-xF1> alternate <S-F1> *<S-xF1>* <S-F2> shifted function key 2 *<S-F2>* <S-xF2> alternate <S-F2> *<S-xF2>* <S-F3> shifted function key 3 *<S-F3>* <S-xF3> alternate <S-F3> *<S-xF3>* <S-F4> shifted function key 4 *<S-F4>* <S-xF4> alternate <S-F4> *<S-xF4>* <S-F5> shifted function key 5 *<S-F5>* <S-F6> shifted function key 6 *<S-F6>* <S-F7> shifted function key 7 *<S-F7>* <S-F8> shifted function key 8 *<S-F8>* <S-F9> shifted function key 9 *<S-F9>* <S-F10> shifted function key 10 *<S-F10>* <S-F11> shifted function key 11 *<S-F11>* <S-F12> shifted function key 12 *<S-F12>* t_%1 <Help> help key *t_%1* *'t_%1'* t_&8 <Undo> undo key *t_&8* *'t_&8'* t_kI <Insert> insert key *t_kI* *'t_kI'* t_kD <Del> delete key *t_kD* *'t_kD'* t_kb <BS> backspace key *t_kb* *'t_kb'* t_kB <S-Tab> back-tab (shift-tab) *<S-Tab>* *t_kB* *'t_kB'* t_kh <Home> home key *t_kh* *'t_kh'* t_#2 <S-Home> shifted home key *<S-Home>* *t_#2* *'t_#2'* <xHome> alternate home key *<xHome>* t_@7 <End> end key *t_@7* *'t_@7'* t_*7 <S-End> shifted end key *<S-End>* *t_star7* *'t_star7'* <xEnd> alternate end key *<xEnd>* t_kP <PageUp> page-up key *t_kP* *'t_kP'* t_kN <PageDown> page-down key *t_kN* *'t_kN'* t_K1 <kHome> keypad home key *t_K1* *'t_K1'* t_K4 <kEnd> keypad end key *t_K4* *'t_K4'* t_K3 <kPageUp> keypad page-up key *t_K3* *'t_K3'* t_K5 <kPageDown> keypad page-down key *t_K5* *'t_K5'* t_K6 <kPlus> keypad plus key *<kPlus>* *t_K6* *'t_K6'* t_K7 <kMinus> keypad minus key *<kMinus>* *t_K7* *'t_K7'* t_K8 <kDivide> keypad divide *<kDivide>* *t_K8* *'t_K8'* t_K9 <kMultiply> keypad multiply *<kMultiply>* *t_K9* *'t_K9'* t_KA <kEnter> keypad enter key *<kEnter>* *t_KA* *'t_KA'* t_KB <kPoint> keypad decimal point *<kPoint>* *t_KB* *'t_KB'* t_KC <k0> keypad 0 *<k0>* *t_KC* *'t_KC'* t_KD <k1> keypad 1 *<k1>* *t_KD* *'t_KD'* t_KE <k2> keypad 2 *<k2>* *t_KE* *'t_KE'* t_KF <k3> keypad 3 *<k3>* *t_KF* *'t_KF'* t_KG <k4> keypad 4 *<k4>* *t_KG* *'t_KG'* t_KH <k5> keypad 5 *<k5>* *t_KH* *'t_KH'* t_KI <k6> keypad 6 *<k6>* *t_KI* *'t_KI'* t_KJ <k7> keypad 7 *<k7>* *t_KJ* *'t_KJ'* t_KK <k8> keypad 8 *<k8>* *t_KK* *'t_KK'* t_KL <k9> keypad 9 *<k9>* *t_KL* *'t_KL'* <Mouse> leader of mouse code *<Mouse>* Note about t_so and t_mr: When the termcap entry "so" is not present the entry for "mr" is used. And vice versa. The same is done for "se" and "me". If your terminal supports both inversion and standout mode, you can see two different modes. If your terminal supports only one of the modes, both will look the same. *keypad-comma* The keypad keys, when they are not mapped, behave like the equivalent normal key. There is one exception: if you have a comma on the keypad instead of a decimal point, Vim will use a dot anyway. Use these mappings to fix that: :noremap <kPoint> , :noremap! <kPoint> , *xterm-codes* There is a special trick to obtain the key codes which currently only works for xterm. When |t_RV| is defined and a response is received which indicates an xterm with patchlevel 141 or higher, Vim uses special escape sequences to request the key codes directly from the xterm. The responses are used to adjust the various t_ codes. This avoids the problem that the xterm can produce different codes, depending on the mode it is in (8-bit, VT102, VT220, etc.). The result is that codes like <xF1> are no longer needed. Note: This is only done on startup. If the xterm options are changed after Vim has started, the escape sequences may not be recognized any more. *termcap-colors* Note about colors: The 't_Co' option tells Vim the number of colors available. When it is non-zero, the 't_AB' and 't_AF' options are used to set the color. If one of these is not available, 't_Sb' and 't_Sf' are used. 't_me' is used to reset to the default colors. *termcap-cursor-shape* *termcap-cursor-color* When Vim enters Insert mode the 't_SI' escape sequence is sent. When leaving Insert mode 't_EI' is used. But only if both are defined. This can be used to change the shape or color of the cursor in Insert mode. These are not standard termcap/terminfo entries, you need to set them yourself. Example for an xterm, this changes the color of the cursor: if &term =~ "xterm" let &t_SI = "\<Esc>]12;purple\x7" let &t_EI = "\<Esc>]12;blue\x7" endif NOTE: When Vim exits the shape for Normal mode will remain. The shape from before Vim started will not be restored. {not available when compiled without the +cursorshape feature} *termcap-title* The 't_ts' and 't_fs' options are used to set the window title if the terminal allows title setting via sending strings. They are sent before and after the title string, respectively. Similar 't_IS' and 't_IE' are used to set the icon text. These are Vim-internal extensions of the Unix termcap, so they cannot be obtained from an external termcap. However, the builtin termcap contains suitable entries for xterm and iris-ansi, so you don't need to set them here. *hpterm* If inversion or other highlighting does not work correctly, try setting the 't_xs' option to a non-empty string. This makes the 't_ce' code be used to remove highlighting from a line. This is required for "hpterm". Setting the 'weirdinvert' option has the same effect as making 't_xs' non-empty, and vice versa. *scroll-region* Some termcaps do not include an entry for 'cs' (scroll region), although the terminal does support it. For example: xterm on a Sun. You can use the builtin_xterm or define t_cs yourself. For example: :set t_cs=^V^[[%i%d;%dr Where ^V is CTRL-V and ^[ is <Esc>. The vertical scroll region t_CV is not a standard termcap code. Vim uses it internally in the GUI. But it can also be defined for a terminal, if you can find one that supports it. The two arguments are the left and right column of the region which to restrict the scrolling to. Just like t_cs defines the top and bottom lines. Defining t_CV will make scrolling in vertically split windows a lot faster. Don't set t_CV when t_da or t_db is set (text isn't cleared when scrolling). Unfortunately it is not possible to deduce from the termcap how cursor positioning should be done when using a scrolling region: Relative to the beginning of the screen or relative to the beginning of the scrolling region. Most terminals use the first method. A known exception is the MS-DOS console (pcterm). The 't_CS' option should be set to any string when cursor positioning is relative to the start of the scrolling region. It should be set to an empty string otherwise. It defaults to "yes" when 'term' is "pcterm". Note for xterm users: The shifted cursor keys normally don't work. You can make them work with the xmodmap command and some mappings in Vim. Give these commands in the xterm: xmodmap -e "keysym Up = Up F13" xmodmap -e "keysym Down = Down F16" xmodmap -e "keysym Left = Left F18" xmodmap -e "keysym Right = Right F19" And use these mappings in Vim: :map <t_F3> <S-Up> :map! <t_F3> <S-Up> :map <t_F6> <S-Down> :map! <t_F6> <S-Down> :map <t_F8> <S-Left> :map! <t_F8> <S-Left> :map <t_F9> <S-Right> :map! <t_F9> <S-Right> Instead of, say, <S-Up> you can use any other command that you want to use the shift-cursor-up key for. (Note: To help people that have a Sun keyboard with left side keys F14 is not used because it is confused with the undo key; F15 is not used, because it does a window-to-front; F17 is not used, because it closes the window. On other systems you can probably use them.)
3. Window size *window-size* [This is about the size of the whole window Vim is using, not a window that is created with the ":split" command.] If you are running Vim on an Amiga and the terminal name is "amiga" or "builtin_amiga", the amiga-specific window resizing will be enabled. On Unix systems three methods are tried to get the window size: - an ioctl call (TIOCGSIZE or TIOCGWINSZ, depends on your system) - the environment variables "LINES" and "COLUMNS" - from the termcap entries "li" and "co" If everything fails a default size of 24 lines and 80 columns is assumed. If a window-resize signal is received the size will be set again. If the window size is wrong you can use the 'lines' and 'columns' options to set the correct values. One command can be used to set the screen size: *:mod* *:mode* *E359* *E362* :mod[e] [mode] Without argument this only detects the screen size and redraws the screen. With MS-DOS it is possible to switch screen mode. [mode] can be one of these values: "bw40" 40 columns black&white "c40" 40 columns color "bw80" 80 columns black&white "c80" 80 columns color (most people use this) "mono" 80 columns monochrome "c4350" 43 or 50 lines EGA/VGA mode number mode number to use, depends on your video card
4. Slow and fast terminals *slow-fast-terminal* *slow-terminal* If you have a fast terminal you may like to set the 'ruler' option. The cursor position is shown in the status line. If you are using horizontal scrolling ('wrap' option off) consider setting 'sidescroll' to a small number. If you have a slow terminal you may want to reset the 'showcmd' option. The command characters will not be shown in the status line. If the terminal scrolls very slowly, set the 'scrolljump' to 5 or so. If the cursor is moved off the screen (e.g., with "j") Vim will scroll 5 lines at a time. Another possibility is to reduce the number of lines that Vim uses with the command "z{height}<CR>". If the characters from the terminal are arriving with more than 1 second between them you might want to set the 'timeout' and/or 'ttimeout' option. See the "Options" chapter |options|. If your terminal does not support a scrolling region, but it does support insert/delete line commands, scrolling with multiple windows may make the lines jump up and down. If you don't want this set the 'ttyfast' option. This will redraw the window instead of scroll it. If your terminal scrolls very slowly, but redrawing is not slow, set the 'ttyscroll' option to a small number, e.g., 3. This will make Vim redraw the screen instead of scrolling, when there are more than 3 lines to be scrolled. If you are using a color terminal that is slow, use this command: hi NonText cterm=NONE ctermfg=NONE This avoids that spaces are sent when they have different attributes. On most terminals you can't see this anyway. If you are using Vim over a slow serial line, you might want to try running Vim inside the "screen" program. Screen will optimize the terminal I/O quite a bit. If you are testing termcap options, but you cannot see what is happening, you might want to set the 'writedelay' option. When non-zero, one character is sent to the terminal at a time (does not work for MS-DOS). This makes the screen updating a lot slower, making it possible to see what is happening.
5. Using the mouse *mouse-using* This section is about using the mouse on a terminal or a terminal window. How to use the mouse in a GUI window is explained in |gui-mouse|. For scrolling with a mouse wheel see |scroll-mouse-wheel|. Don't forget to enable the mouse with this commands: :set mouse=a Otherwise Vim won't recognize the mouse in all modes (See 'mouse'). Currently the mouse is supported for Unix in an xterm window, in a *BSD console with |sysmouse|, in a Linux console (with GPM |gpm-mouse|), for MS-DOS and in a Windows console. Mouse clicks can be used to position the cursor, select an area and paste. These characters in the 'mouse' option tell in which situations the mouse will be used by Vim: n Normal mode v Visual mode i Insert mode c Command-line mode h all previous modes when in a help file a all previous modes r for |hit-enter| prompt The default for 'mouse' is empty, the mouse is not used. Normally you would do: :set mouse=a to start using the mouse (this is equivalent to setting 'mouse' to "nvich"). If you only want to use the mouse in a few modes or also want to use it for the two questions you will have to concatenate the letters for those modes. For example: :set mouse=nv Will make the mouse work in Normal mode and Visual mode. :set mouse=h Will make the mouse work in help files only (so you can use "g<LeftMouse>" to jump to tags). Whether the selection that is started with the mouse is in Visual mode or Select mode depends on whether "mouse" is included in the 'selectmode' option. In an xterm, with the currently active mode included in the 'mouse' option, normal mouse clicks are used by Vim, mouse clicks with the shift or ctrl key pressed go to the xterm. With the currently active mode not included in 'mouse' all mouse clicks go to the xterm. *xterm-clipboard* In the Athena and Motif GUI versions, when running in a terminal and there is access to the X-server (DISPLAY is set), the copy and paste will behave like in the GUI. If not, the middle mouse button will insert the unnamed register. In that case, here is how you copy and paste a piece of text: Copy/paste with the mouse and Visual mode ('mouse' option must be set, see above): 1. Press left mouse button on first letter of text, move mouse pointer to last letter of the text and release the button. This will start Visual mode and highlight the selected area. 2. Press "y" to yank the Visual text in the unnamed register. 3. Click the left mouse button at the insert position. 4. Click the middle mouse button. Shortcut: If the insert position is on the screen at the same time as the Visual text, you can do 2, 3 and 4 all in one: Click the middle mouse button at the insert position. Note: When the |-X| command line argument is used, Vim will not connect to the X server and copy/paste to the X clipboard (selection) will not work. Use the shift key with the mouse buttons to let the xterm do the selection. *xterm-command-server* When the X-server clipboard is available, the command server described in |x11-clientserver| can be enabled with the --servername command line argument. *xterm-copy-paste* NOTE: In some (older) xterms, it's not possible to move the cursor past column 95. This is an xterm problem, not Vim's. Get a newer xterm |color-xterm|. Copy/paste in xterm with (current mode NOT included in 'mouse'): 1. Press left mouse button on first letter of text, move mouse pointer to last letter of the text and release the button. 2. Use normal Vim commands to put the cursor at the insert position. 3. Press "a" to start Insert mode. 4. Click the middle mouse button. 5. Press ESC to end Insert mode. (The same can be done with anything in 'mouse' if you keep the shift key pressed while using the mouse.) Note: if you lose the 8th bit when pasting (special characters are translated into other characters), you may have to do "stty cs8 -istrip -parenb" in your shell before starting Vim. Thus in an xterm the shift and ctrl keys cannot be used with the mouse. Mouse commands requiring the CTRL modifier can be simulated by typing the "g" key before using the mouse: "g<LeftMouse>" is "<C-LeftMouse> (jump to tag under mouse click) "g<RightMouse>" is "<C-RightMouse> ("CTRL-T") *mouse-mode-table* *mouse-overview* A short overview of what the mouse buttons do, when 'mousemodel' is "extend": Normal Mode: event position selection change action cursor window <LeftMouse> yes end yes <C-LeftMouse> yes end yes "CTRL-]" (2) <S-LeftMouse> yes no change yes "*" (2) *<S-LeftMouse>* <LeftDrag> yes start or extend (1) no *<LeftDrag>* <LeftRelease> yes start or extend (1) no <MiddleMouse> yes if not active no put <MiddleMouse> yes if active no yank and put <RightMouse> yes start or extend yes <A-RightMouse> yes start or extend blockw. yes *<A-RightMouse>* <S-RightMouse> yes no change yes "#" (2) *<S-RightMouse>* <C-RightMouse> no no change no "CTRL-T" <RightDrag> yes extend no *<RightDrag>* <RightRelease> yes extend no *<RightRelease>* Insert or Replace Mode: event position selection change action cursor window <LeftMouse> yes (cannot be active) yes <C-LeftMouse> yes (cannot be active) yes "CTRL-O^]" (2) <S-LeftMouse> yes (cannot be active) yes "CTRL-O*" (2) <LeftDrag> yes start or extend (1) no like CTRL-O (1) <LeftRelease> yes start or extend (1) no like CTRL-O (1) <MiddleMouse> no (cannot be active) no put register <RightMouse> yes start or extend yes like CTRL-O <A-RightMouse> yes start or extend blockw. yes <S-RightMouse> yes (cannot be active) yes "CTRL-O#" (2) <C-RightMouse> no (cannot be active) no "CTRL-O CTRL-T" In a help window: event position selection change action cursor window <2-LeftMouse> yes (cannot be active) no "^]" (jump to help tag) When 'mousemodel' is "popup", these are different: Normal Mode: event position selection change action cursor window <S-LeftMouse> yes start or extend (1) no <A-LeftMouse> yes start or extend blockw. no *<A-LeftMouse>* <RightMouse> no popup menu no Insert or Replace Mode: event position selection change action cursor window <S-LeftMouse> yes start or extend (1) no like CTRL-O (1) <A-LeftMouse> yes start or extend blockw. no <RightMouse> no popup menu no (1) only if mouse pointer moved since press (2) only if click is in same buffer Clicking the left mouse button causes the cursor to be positioned. If the click is in another window that window is made the active window. When editing the command-line the cursor can only be positioned on the command-line. When in Insert mode Vim remains in Insert mode. If 'scrolloff' is set, and the cursor is positioned within 'scrolloff' lines from the window border, the text is scrolled. A selection can be started by pressing the left mouse button on the first character, moving the mouse to the last character, then releasing the mouse button. You will not always see the selection until you release the button, only in some versions (GUI, MS-DOS, WIN32) will the dragging be shown immediately. Note that you can make the text scroll by moving the mouse at least one character in the first/last line in the window when 'scrolloff' is non-zero. In Normal, Visual and Select mode clicking the right mouse button causes the Visual area to be extended. When 'mousemodel' is "popup", the left button has to be used while keeping the shift key pressed. When clicking in a window which is editing another buffer, the Visual or Select mode is stopped. In Normal, Visual and Select mode clicking the right mouse button with the alt key pressed causes the Visual area to become blockwise. When 'mousemodel' is "popup" the left button has to be used with the alt key. Note that this won't work on systems where the window manager consumes the mouse events when the alt key is pressed (it may move the window). *double-click* Double, triple and quadruple clicks are supported when the GUI is active, for MS-DOS and Win32, and for an xterm (if the gettimeofday() function is available). For selecting text, extra clicks extend the selection: click select double word or % match *<2-LeftMouse>* triple line *<3-LeftMouse>* quadruple rectangular block *<4-LeftMouse>* Exception: In a Help window a double click jumps to help for the word that is clicked on. A double click on a word selects that word. 'iskeyword' is used to specify which characters are included in a word. A double click on a character that has a match selects until that match (like using "v%"). If the match is an #if/#else/#endif block, the selection becomes linewise. For MS-DOS and xterm the time for double clicking can be set with the 'mousetime' option. For the other systems this time is defined outside of Vim. An example, for using a double click to jump to the tag under the cursor: :map <2-LeftMouse> :exe "tag ". expand("<cword>")<CR> Dragging the mouse with a double click (button-down, button-up, button-down and then drag) will result in whole words to be selected. This continues until the button is released, at which point the selection is per character again. *gpm-mouse* The GPM mouse is only supported when the |+mouse_gpm| feature was enabled at compile time. The GPM mouse driver (Linux console) does not support quadruple clicks. In Insert mode, when a selection is started, Vim goes into Normal mode temporarily. When Visual or Select mode ends, it returns to Insert mode. This is like using CTRL-O in Insert mode. Select mode is used when the 'selectmode' option contains "mouse". *sysmouse* The sysmouse is only supported when the |+mouse_sysmouse| feature was enabled at compile time. The sysmouse driver (*BSD console) does not support keyboard modifiers. *drag-status-line* When working with several windows, the size of the windows can be changed by dragging the status line with the mouse. Point the mouse at a status line, press the left button, move the mouse to the new position of the status line, release the button. Just clicking the mouse in a status line makes that window the current window, without moving the cursor. If by selecting a window it will change position or size, the dragging of the status line will look confusing, but it will work (just try it). *<MiddleRelease>* *<MiddleDrag>* Mouse clicks can be mapped. The codes for mouse clicks are: code mouse button normal action <LeftMouse> left pressed set cursor position <LeftDrag> left moved while pressed extend selection <LeftRelease> left released set selection end <MiddleMouse> middle pressed paste text at cursor position <MiddleDrag> middle moved while pressed - <MiddleRelease> middle released - <RightMouse> right pressed extend selection <RightDrag> right moved while pressed extend selection <RightRelease> right released set selection end <X1Mouse> X1 button pressed - *X1Mouse* <X1Drag> X1 moved while pressed - *X1Drag* <X1Release> X1 button release - *X1Release* <X2Mouse> X2 button pressed - *X2Mouse* <X2Drag> X2 moved while pressed - *X2Drag* <X2Release> X2 button release - *X2Release* The X1 and X2 buttons refer to the extra buttons found on some mice. The 'Microsoft Explorer' mouse has these buttons available to the right thumb. Currently X1 and X2 only work on Win32 environments. Examples: :noremap <MiddleMouse> <LeftMouse><MiddleMouse> Paste at the position of the middle mouse button click (otherwise the paste would be done at the cursor position). :noremap <LeftRelease> <LeftRelease>y Immediately yank the selection, when using Visual mode. Note the use of ":noremap" instead of "map" to avoid a recursive mapping. :map <X1Mouse> <C-O> :map <X2Mouse> <C-I> Map the X1 and X2 buttons to go forwards and backwards in the jump list, see |CTRL-O| and |CTRL-I|. *mouse-swap-buttons* To swap the meaning of the left and right mouse buttons: :noremap <LeftMouse> <RightMouse> :noremap <LeftDrag> <RightDrag> :noremap <LeftRelease> <RightRelease> :noremap <RightMouse> <LeftMouse> :noremap <RightDrag> <LeftDrag> :noremap <RightRelease> <LeftRelease> :noremap g<LeftMouse> <C-RightMouse> :noremap g<RightMouse> <C-LeftMouse> :noremap! <LeftMouse> <RightMouse> :noremap! <LeftDrag> <RightDrag> :noremap! <LeftRelease> <RightRelease> :noremap! <RightMouse> <LeftMouse> :noremap! <RightDrag> <LeftDrag> :noremap! <RightRelease> <LeftRelease> top - main help file


Cotton
- Unlimited use
- No API key needed
- Completely connected topologies
- Superpeer topologies
- Best for < 10 players per room
libfabric is a JavaScript library for peer-to-peer browser game networking. It's free, easy to use, and ridiculously scalable. It was developed with the goal of leveling the playing field for indie developers and small game studios who are limited in labour and money. Click here to learn more about the technical details.
If you're using a bundler like webpack or Browserify,
npm install yousefamar/p2p-peer
otherwise you can simply include the library through a CDN
<script src="https://cdn.jsdelivr.net/gh/yousefamar/p2p-peer/pkg/dist-web/index.min.js"></script>
There are two layers of abstraction with which you can use libfabric. The first is to basically treat it as a server with "rooms" as namespaces through which you can broadcast events with arbitrary names and arbitrary objects that can be serialized into JSON.
import PeerNetwork from 'libfabric';
(async () => {
const peerNet = new PeerNetwork();
await peerNet.connect('https://libfabric.io'); // or https://sig.amar.io
peerNet.on('connection', peer => {
console.log('Peer', peer.uid, 'connected');
peer.on('greeting', msg => console.log('Peer', peer.uid + ':', msg));
peer.on('disconnect', () => console.log('Peer', peer.uid, 'disconnected'));
});
peerNet.on('uid', uid => {
console.log(uid);
let room = peerNet.join('test');
room.eventEmitter.on('.', console.log);
});
})();
The second is using room.syncedData
which is an object that will automatically propagate and sync across the network. Newer updates always take priority over older updates.
Since 80% of traffic for the majority of games is position updates, each of
peerNet.peers[].pos
can be used to set/get peer virtual positions. These coordinates are special as they affect the way topologies are computed, and have configurable, game-specific optimisations (such as prediction/interpolation) applied to them.
libfabric is absolutely free if you host your own signalling server. If you don't, it's still completely free if you're an indie developer or small game studio, if your game does not make any money, or if your game is open source. Otherwise, we divide usage into three plans:


Jurgen Klopp says Virgil Van Dijk is standout candidate above Lionel Messi for Ballon d’Or glory
by FSA EditorLiverpool boss Jurgen Klopp says his star defender Virgil van Dijk deserves the Ballon d’Or after his brilliant year for the Reds.
Liverpool boss Jurgen Klopp says Virgil van Dijk should beat Lionel Messi to Ballon d’Or glory next month.
Dutch defender Van Dijk has had a stunning year with Liverpool, helping the Reds win the Champions League in June.
They narrowly missed out on last season’s Premier League title but are heading the chase for domestic glory in England this term after an unbeaten start.
Klopp can see why Barcelona superstar Messi would be a popular choice for the individual honour, because of his career accomplishments.
But rather than give a sixth Ballon d’Or to Messi, Klopp believes there is a strong case for Liverpool’s defensive talisman to walk away with the trophy at the Paris ceremony on December 2.
Real Madrid’s Croatian playmaker Luka Modric was last year’s winner of the prize, which is awarded annually by France Football magazine.
Klopp said: “If you give the Ballon d’Or to the best player of this generation, then you can give it always to Lionel Messi, that’s how it is.
“But if you give it to the best player of last season, then it was Virgil van Dijk.
“So I don’t know exactly how it will work, but that’s how I see it.
“If it’s for the best player of all, then it’s Lionel. The best player of last season, it’s Virgil. We will see.”
Van Dijk also helped Netherlands to qualify for Euro 2020 this year, while Messi featured as Argentina finished third at the Copa America.


public class CarmelTopKTermPruningPolicy extends TermPruningPolicy
| For any OR query with r terms, the score of each of the top k results in the original index, should be "practically the same" as the score that document in the pruned index: the scores difference should not exceed r * ε . |
See the following paper for more details about this method: Static index pruning for information retrieval systems, D. Carmel at al, ACM SIGIR 2001 .
The claim of this pruning technique is, quoting from the above paper:
| Prune the index in such a way that a human "cannot distinguish the difference" between the results of a search engine whose index is pruned and one whose index is not pruned. |
For indexes with a large number of terms this policy might be too slow. In
such situations, the uniform pruning approach in
CarmelUniformTermPruningPolicy
will be faster, though it might
produce inferior search quality, as that policy does not pose a theoretical
guarantee on resulted search quality.
TODO implement also CarmelTermPruningDeltaTopPolicy
| Modifier and Type | Class and Description |
|---|---|
static class
|
CarmelTopKTermPruningPolicy.ByDocComparator
|
| Modifier and Type | Field and Description |
|---|---|
static float
|
DEFAULT_EPSILON
Default largest meaningless score difference
|
static int
|
DEFAULT_R
Default number of query terms
|
static int
|
DEFAULT_TOP_K
Default number of guaranteed top K scores
|
fieldFlags
,
in
DEL_ALL
,
DEL_PAYLOADS
,
DEL_POSTINGS
,
DEL_STORED
,
DEL_VECTOR
| Constructor and Description |
|---|
CarmelTopKTermPruningPolicy
(
IndexReader
in,
Map
<
String
,
Integer
> fieldFlags)
Constructor with default parameters
|
CarmelTopKTermPruningPolicy
(
IndexReader
in,
Map
<
String
,
Integer
> fieldFlags,
int k,
float epsilon,
int r,
Similarity
sim)
Constructor with specific settings
|
| Modifier and Type | Method and Description |
|---|---|
void
|
initPositionsTerm
(
TermPositions
tp,
Term
t)
Called when moving
TermPositions
to a new
Term
.
|
boolean
|
pruneAllPositions
(
TermPositions
termPositions,
Term
t)
Prune
all
postings per term (invoked once per term per doc)
|
int
|
pruneSomePositions
(int docNum,
int[] positions,
Term
curTerm)
Prune
some
postings per term (invoked once per term per doc).
|
boolean
|
pruneTermEnum
(
TermEnum
te)
Pruning of all postings for a term (invoked once per term).
|
int
|
pruneTermVectorTerms
(int docNumber,
String
field,
String
[] terms,
int[] freqs,
TermFreqVector
tfv)
Pruning of individual terms in term vectors.
|
pruneAllFieldPostings
,
prunePayload
,
pruneWholeTermVector
public static final int DEFAULT_TOP_K
public static final int DEFAULT_R
public static final float DEFAULT_EPSILON
public CarmelTopKTermPruningPolicy( IndexReader in, Map < String , Integer > fieldFlags)
public CarmelTopKTermPruningPolicy( IndexReader in, Map < String , Integer > fieldFlags, int k, float epsilon, int r, Similarity sim)
in
- reader for original index
k
- number of guaranteed top scores. Each top K results in the pruned
index is either also an original top K result or its original
score is indistinguishable from some original top K result.
epsilon
- largest meaningless score difference Results whose scores
difference is smaller or equal to epsilon are considered
indistinguishable.
r
- maximal number of terms in a query for which search quaility in
pruned index is guaranteed
sim
- similarity to use when selecting top docs fir each index term.
When null,
DefaultSimilarity
is used.
public boolean pruneTermEnum( TermEnum te) throws IOException
TermPruningPolicy
pruneTermEnum
in class
TermPruningPolicy
te
- positioned term enum.
IOException
public void initPositionsTerm( TermPositions tp, Term t) throws IOException
TermPruningPolicy
TermPositions
to a new
Term
.
initPositionsTerm
in class
TermPruningPolicy
tp
- input term positions
t
- current term
IOException
public boolean pruneAllPositions( TermPositions termPositions, Term t) throws IOException
TermPruningPolicy
pruneAllPositions
in class
TermPruningPolicy
termPositions
- positioned term positions. Implementations MUST NOT
advance this by calling
TermPositions
methods that advance either
the position pointer (next, skipTo) or term pointer (seek).
t
- current term
IOException
public int pruneTermVectorTerms(int docNumber, String field, String [] terms, int[] freqs, TermFreqVector tfv) throws IOException
TermPruningPolicy
pruneTermVectorTerms
in class
TermPruningPolicy
docNumber
- document number
field
- field name
terms
- array of terms
freqs
- array of term frequencies
tfv
- the original term frequency vector
IOException
public int pruneSomePositions(int docNum, int[] positions, Term curTerm)
TermPruningPolicy
pruneSomePositions
in class
TermPruningPolicy
docNum
- current document number
positions
- original term positions in the document (and indirectly
term frequency)
curTerm
- current term


Imagine an internet slightly different than what we have today. The internet of the future won't require logging in with passwords on every site you wish to access. It will just know who you are. An internet where you need to keep track of hundreds/thousands of passwords on hundreds/thousands of websites is fundamentally broken. But an internet with no privacy and where all your online activities are monitored and tracked is likewise broken.
Imagine if you had an internet where the people using it could create new services and communicate freely and privately - and where you didn't need a different account on every website in the network in order to use each website. Where you had your own space and could share anything you wanted with anybody you wanted, any time you wanted. Where the things you share in private stay private instead of being under constant surveillance from advertising corporations and government intelligence agencies.
Now open your eyes. We've done some amazing things with decentralisation technology over the last few years and have created a different kind of network. We call it the Red Matrix. Forget the old internet - it's hopelessly broken and increasingly being choked off in order to take your money and spy on you. We're building tomorrow's internet today. And we're doing things a bit differently than what you may be used to. We could wait for this new internet to be built, but we don't really trust the typical corporations and governmental bodies to do it right. So we're building it on top of the old internet. And we're building privacy into its DNA. And it's here now.
The Red Matrix is a decentralised network where the people using it are in charge and the size of your server farm and wealth do not offer any comparable advantage. Anybody may participate on a level playing field. Cloud storage, file sharing, communications, content creation and management belong to everybody and can be shared with anybody (or somebody, or nobody). This is only a representative sample of the services we plan to offer. In an internet where creativity is allowed to flourish and corporate overlords have no power, the door is open to entirely new forms of expression and applications. The Red Matrix software is free and open source; created by volunteers and distributed under the MIT license.
And the Red Matrix has Got Zot.
So what the heck is Zot? I'm glad you asked...
Zot is a revolutionary protocol which provides decentralised communications and identity management across the matrix. The resulting platform can provide web services comparable to those offered by large corporate providers, but without the large corporate provider and their associated privacy issues. Communications and social networking are an integral part of the matrix. Any channel (and any services provided by that channel) can make full use of feature-rich social communications on a global scale.
We use the full power of the matrix to offer friend suggestions and directory services. You can also perform other things which would typically only be possibly on a centralised provider - such as "wall to wall" posts and private/multiple profiles and web content which can be tailored to the viewer. You won't find these features at all on other decentralised communication services. The difference is that Zot also provides decentralised identity services. This is what separates the men from the boys, and what makes life in the matrix so awesome.
Zot's identity layer is unique. It's like OpenID on steroids. It provides invisible single sign-on across all sites in the matrix; as well as nomadic identity so that your communications with friends, family, and business partners won't be affected by the loss of your primary communication node - either temporarily or permanently. The important bits of your identity and relationships can be backed up to a thumb drive and may appear at any node in the matrix at any time - with all your friends and preferences intact. These nomadic instances are kept in sync so any instance can take over if another one is compromised or damaged. This protects you against not only major system failure, but also temporary site overloads and governmental manipulation. You cannot be silenced. You cannot be removed from the matrix.
As you browse the matrix viewing channels and their unique content, you are seamlessly authenticated as you go, even across completely different server hubs. No password dialogues. Nothing to type. You're just greeted by name on every new site you visit. How does Zot do that? We call it "magic-auth" because it really is technology that is so advanced as to be indistinguishable from magic. You login only once on your home hub (or any nomadic backup hub you have chosen). This allows you to access any authenticated services provided anywhere in the matrix - such as shopping and access to private information. This is just like the services offered by large corporate providers with huge user databases; however you can be a member of this community and a server on this network using a "plug computer" like a Rasberry Pi. Your password isn't stored on a thousand different sites where it can be stolen and used to clean out your bank accounts.
Zot's identity layer allows you to provide fine-grained permissions to any content you wish to publish - and these permissions extend across the Red Matrix. This is like having one super huge website made up of an army of small individual websites - and where each channel in the matrix can completely control their privacy and sharing preferences for any web resources they create.
Example: you want a photo to be visible to your family and three select friends, but not your work colleagues. In the matrix this is easy. Even if your family members, work colleagues, and friends all have accounts on different hubs.
Currently the matrix supports communications, photo albums, events, and files. This will be extended in the future to provide content management services (web pages) and cloud storage facilities such as WebDAV and multi-media libraries. Every object and how it is shared and with whom is completely under your control.
Again, this type of control is available on large corporate providers, because they own the user database. Within the matrix, there is no need for a huge user database on your machine - because the matrix is your user database and for all intents and purposes has infinite capacity and is spread amongst hundreds, and potentially millions of computers. Access can be granted or denied for any resource, to any channel or any group of channels; anywhere within the matrix. They do not need to have an account on your hub.
Your communications may be public or private - and we allow your private communications to be as private as you wish them to be. Private communications comprise not only fully encrypted transport, but also encrypted storage to help protect against accidental snooping and disclosure by rogue system administrators and internet service providers.
Want more? You can fully encrypt your messages "end to end" using your choice of encryption ciphers and using a passphrase that only you and the recipient(s) know - in addition to our standard multi-layer encryption.
Want more? Our end to end encryption is pluggable. You can define your own chain of multiple encryption steps with multiple keys, and include algorithms known only to you and the recipient. At some point even the US National Security Agency will have to throw up their hands. There won't be enough computational power available in the universe to decode your private message.
We also provide optional message expiration as a standard feature. When the expiration date/time passes, your message is removed from the network.


WebSocket Sample Application
Ready to connect...
WebSocket Server URL:
Connect
Message to send:
Send
Close Socket
Communication Log
From
To
Data


DBLock¶
Read Oracle documentation for better understanding.
The DBLock objects have no methods or attributes. They are just opaque handles to the lock in question.
They are managed via DBEnv methods.
Read Oracle documentation for better understanding.
The DBLock objects have no methods or attributes. They are just opaque handles to the lock in question.
They are managed via DBEnv methods.


Corroman is a superhero story about a pair of brothers who got accidentally exposed to a special radiation and gained the superpower of corroding and melting things. In this part of the storyboard, the two brothers, Fred and Max, are trying to get out of a warehouse to escape from chase of the guards.
In this part of the storyboard of Corroman, Fred is trying to rescue his little brother, Max, from the villain, Dr. Blake, who wants to take the superpower from them via evil experiments.
This animatic storyboard is about a public service announcement about plastic bags. It is inspired by the iconic feature movie "The Matrix".
It is normal to dream of becoming a hero and saving some beauty from monsters, but dreams is always easily interrupted by real life.
 This is about a man, who was about to commit suicide, helping a new-born bird find her wings. They then started an unusual journey.
Storyboard samples of "The Incredible Stationary Store" - the story is adapted from a fairy tale written by the Japanese author Naoko Awa.
"Secret"- this is an original story by me. With realistic style, I used several characters, whose connections with each other form a circle, to reflect the concept of "Peeping Tom" as the camera moves from one to another.


Room Name
Room Password (optional)
User Name
You have error...
Username
Room Password
Roles: Tap a player to kill, heal or discover and press OK.
Villagers: Press OK to continue.
The winner is:


Telerik Upload for ASP.NET MVC Key Features
- Asynchronous and synchronous (on form submit) file upload
- Multiple file selection
- Progress tracking *
- Drag and drop *
- Cancelling upload in progress *
- Removing uploaded files
- Seventeen built-in themes
- Client API and event handling
- Localization
- Standards based, no plug-ins required
* These features will be automatically turned on if available in the browser.
Consult the documentation for a list of supported browsers.


|
JUST2D Platformer
|
Class-container which contains information about objects on the Level. More...
#include <LevelStorage.h>
Public Attributes | |
| std::list< Lever * > | lever_list |
| list of pointers to Lever entity | |
| std::list< Timer * > | timer_list |
| list of pointers to Timer entity | |
| std::list< NonStaticObj * > | non_static_objects |
| list of all pointers to NonStaticObj entities | |
| std::list< PlayerSensor * > | players_sensors_list |
| list of pointers to sensors which attached to players | |
| std::list< NonStaticObj * > * | to_destroy_list |
| list containing pointers to objects that will be destroyed at the next level update iteration | |
| std::list< DangerObject * > | danger_list |
| list of all pointers to DangerObject entities | |
| Final * | final_list [2] |
| contains pointers to final sensor (for both players) | |
| std::list< Bonus * > | bonus_list |
| list of all pointers to Bonus entities | |
| std::map< std::string, ManualSwitchObj * > | future_observables |
| internal map which help to parse information about observables objects and pin them to the observer | |


{% extends "_layout" %} {% block content %}
1The Discovery Room Experience.
In this experience entire families view and interact with their FamilySearch data through engaging, interactive applications at the Puyallup Family History Center.
2Turn Our Hearts Experience.
In this experience a ward family history consultant will introduce your family to the Turn Our Hearts in Both Directions guide in your home.
3Family Learning Sessions.
When your family has chosen which “Ways to Turn Our Hearts in Both Directions” tasks you want to accomplish you will need to set up an appointment with your ward family history consultants or a staff member from the Puyallup Stake Family History Center. Either the ward family history consultants or the Family History Center worker will give your family more in-depth lessons.


{% extends "_layout.html" %} {% block meta_title %}Financial Aid – {{ block.super }}{% endblock %} {% block main %}
We want PyCon CZ to be as accessible as possible.
Financial Aid is meant for anyone who is not able to attend PyCon CZ because of their financial situation. It may cover ticket and/or accommodation and/or travel costs.
While we can’t cover all expenses for everyone, we try our best to help as much as our budget allows.
Financial aid applications open on 15 April and close on 26 April.
After that we will carefully examine each application and
inform all applicants privately before the end of April about the result.
Our primary goal is to make PyCon CZ accessible to everyone, irrespective of their financial situation. For this reason, we provide multiple tiers of ticket prices, Early-Bird, Educational, Individual and Company. This is based on the principle that those who can afford to pay for tickets subsidize those who cannot. This structure enables us to include major diversity and outreach programmes such as DjangoGirls, reward and encourage active participation in the PyCon CZ event organization, and fund PyCon CZ’s Financial Aid programme.
PyCon CZ’s financial aid programme aims to provide funds to help people attend PyCon CZ. Financial aid recipients have some part of their expenses (which may include travel, accommodation, or ticket registration) paid for by the PyCon CZ budget. We actively encourage people to apply for financial aid. While we can’t cover all expenses for everyone, we try our best to optimally allocate our budget. Optimal is, of course, an ambiguous property.
Since PyCon is a well positioned international Python conference in central Europe, it’s a meeting place for Python developers from all around the globe. Therefore, the process is designed to benefit people that we believe make PyCon CZ better, particularly speakers and workshop tutors, as well as notable open source contributors.
This way, the process attempts to promote a more diverse community event.
Finally, the process tries to help people with relatively lower incomes, be it because of their location (lower income countries or regions) or their profession (such as students, or the unemployed).
In short, we use the financial aid budget to help individuals who would otherwise not be able to attend the conference or whose presence will bring a justifiably positive impact for other attendees.
The financial aid programme supports the community by making it more accessible at PyCon CZ. It is true to the spirit of PyCon to make the information and interactions available to everyone.
PyCon CZ aims to be the largest annual gathering for the Python community in the Czech Republic, focused on honoring and supporting awesome people teaching, learning and innovating with Python in the Czech Republic and surrounding countries. The Python Software Foundation, the parent PyCon event organizer and sponsor, aims to promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers. We believe that the financial aid programme is perfectly aligned with these goals.
Note well that our Code of Conduct is strictly enforced during all official PyCon CZ event activities. All recipients of financial aid cited for a CoC violations will be immediately disqualified for all funding awards.
Please do not hesitate to email us at<EMAIL_ADDRESS>{% endblock %}


Apache Kylin is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Apache Kylin is distributed under the Apache License v2.0.


Programmer's Base
Add New Resource
Search
Total: [[${totalItems}]]
First
First
Prev
Prev
[[${i}]]
. . .
[[${i}]]
Next
Next
Last
Last


About Me
My name is Nardin Lachowski and I just started my journey into frontend and backend development. I am currently enrolled in UConn's fullstack coding bootcamp. I have attempted the self-learn route for a couple of years now so I am elated to be commiting the next 6 months to getting the next chapter of my career off the ground and I am sure I will be meeting some incredible people in the process.
I live south of Boston with my husband, and our dog and cat. I've been working from home since Morch of this year which has been a nice change for me. Afterall, replacing a commute with family time and time spent outdoors is always a plus.
I love collaborating with other developers to build incredible things. Don't be shy, say hello and let's make some magic happen!


January 11
But when he saw the wind boisterous, he was afraid; and beginning to sink, he cried, saying,
Lord, save me. And immediately Jesus stretched forth his hand, and caught him, and said unto him, O thou of little faith, wherefore didst thou doubt?
Matthew 14:30-31
If there's any way the devil can get your eyes away from the Word, he'll do it. He'll cause trouble. He'll make the circumstances around you pitch and roll like a rowboat in a hurricane. He'll do anything he can to get you to concentrate on the realm of the physical senses and the situation around you instead of on the promise of God-because he knows that if he doesn't, you'll take that promise and beat his brains out with it.
That's what he did to Peter. When Peter first jumped out of the boat that day in response to Jesus' word, what happened? He walked right across that water without a problem. His whole being was fastened on that word Jesus had spoken to him, "Come!"
But when he took his eyes off that word, he started looking at the storm. He started looking at the impossible thing he was doing. After all, he was a fisherman. All his training and experience told him when the waves were that high, you were going under. He started to focus on what he knew in the natural instead of what Jesus said. When he did that, his faith slipped out of gear and he started to sink.
Don't let that happen to you. Once you get a revelation from the Word of God, hang onto it. Don't focus on anything else.
The devil will do everything he can to get you to turn loose of it.  He'll try to get you into fear. He'll push every button he can from the past to get you back into your old way of thinking.
But don't let go. Keep your eyes on the Word of God until it's more real inside you than anything else. If you do, you'll be able to walk your way across the water just fine.
Scripture Reading: Matthew 14:22-33


Hello human!
Send me an encrypted message using http://{{host}}/send?msg=
for example: http://{{host}}/send?msg={{msg}}
Note: only I can decrypt the message (you don't have the key!)


** ** Status: canonical model. ** ** Given: ** date1,date2 double TT as a 2-part Julian Date (Note 1) ** ** Returned: ** dpsi,deps double nutation, luni-solar + planetary (Note 2) ** ** Notes: ** ** 1) The TT date date1+date2 is a Julian Date, apportioned in any ** convenient way between the two arguments. For example, ** JD(TT)=2450123.7 could be expressed in any of these ways, ** among others: ** ** date1 date2 ** ** 2450123.7 0.0 (JD method) ** 2451545.0 -1421.3 (J2000 method) ** 2400000.5 50123.2 (MJD method) ** 2450123.5 0.2 (date & time method) ** ** The JD method is the most natural and convenient to use in ** cases where the loss of several decimal digits of resolution ** is acceptable. The J2000 method is best matched to the way ** the argument is handled internally and will deliver the ** optimum resolution. The MJD method and the date & time methods ** are both good compromises between resolution and convenience. ** ** 2) The nutation components in longitude and obliquity are in radians ** and with respect to the equinox and ecliptic of date. The ** obliquity at J2000.0 is assumed to be the Lieske et al. (1977) ** value of 84381.448 arcsec. (The errors that result from using ** this function with the IAU 2006 value of 84381.406 arcsec can be ** neglected.) ** ** The nutation model consists only of luni-solar terms, but ** includes also a fixed offset which compensates for certain long- ** period planetary terms (Note 7). ** ** 3) This function is an implementation of the IAU 2000B abridged ** nutation model formally adopted by the IAU General Assembly in ** 2000. The function computes the MHB_2000_SHORT luni-solar ** nutation series (Luzum 2001), but without the associated ** corrections for the precession rate adjustments and the offset ** between the GCRS and J2000.0 mean poles. ** ** 4) The full IAU 2000A (MHB2000) nutation model contains nearly 1400 ** terms. The IAU 2000B model (McCarthy & Luzum 2003) contains only ** 77 terms, plus additional simplifications, yet still delivers ** results of 1 mas accuracy at present epochs. This combination of ** accuracy and size makes the IAU 2000B abridged nutation model ** suitable for most practical applications. ** ** The function delivers a pole accurate to 1 mas from 1900 to 2100 ** (usually better than 1 mas, very occasionally just outside ** 1 mas). The full IAU 2000A model, which is implemented in the ** function iauNut00a (q.v.), delivers considerably greater accuracy ** at current dates; however, to realize this improved accuracy, ** corrections for the essentially unpredictable free-core-nutation ** (FCN) must also be included. ** ** 5) The present function provides classical nutation. The ** MHB_2000_SHORT algorithm, from which it is adapted, deals also ** with (i) the offsets between the GCRS and mean poles and (ii) the ** adjustments in longitude and obliquity due to the changed ** precession rates. These additional functions, namely frame bias ** and precession adjustments, are supported by the SOFA functions ** iauBi00 and iauPr00. ** ** 6) The MHB_2000_SHORT algorithm also provides "total" nutations, ** comprising the arithmetic sum of the frame bias, precession ** adjustments, and nutation (luni-solar + planetary). These total ** nutations can be used in combination with an existing IAU 1976 ** precession implementation, such as iauPmat76, to deliver GCRS- ** to-true predictions of mas accuracy at current epochs. However, ** for symmetry with the iauNut00a function (q.v. for the reasons), ** the SOFA functions do not generate the "total nutations" ** directly. Should they be required, they could of course easily ** be generated by calling iauBi00, iauPr00 and the present function ** and adding the results. ** ** 7) The IAU 2000B model includes "planetary bias" terms that are ** fixed in size but compensate for long-period nutations. The ** amplitudes quoted in McCarthy & Luzum (2003), namely ** Dpsi = -1.5835 mas and Depsilon = +1.6339 mas, are optimized for ** the "total nutations" method described in Note 6. The Luzum ** (2001) values used in this SOFA implementation, namely -0.135 mas ** and +0.388 mas, are optimized for the "rigorous" method, where ** frame bias, precession and nutation are applied separately and in ** that order. During the interval 1995-2050, the SOFA ** implementation delivers a maximum error of 1.001 mas (not ** including FCN). ** ** References: ** ** Lieske, J.H., Lederle, T., Fricke, W., Morando, B., "Expressions ** for the precession quantities based upon the IAU /1976/ system of ** astronomical constants", Astron.Astrophys. 58, 1-2, 1-16. (1977) ** ** Luzum, B., private communication, 2001 (Fortran code ** MHB_2000_SHORT) ** ** McCarthy, D.D. & Luzum, B.J., "An abridged model of the ** precession-nutation of the celestial pole", Cel.Mech.Dyn.Astron. ** 85, 37-49 (2003) ** ** Simon, J.-L., Bretagnon, P., Chapront, J., Chapront-Touze, M., ** Francou, G., Laskar, J., Astron.Astrophys. 282, 663-683 (1994) ** ** This revision: 2010 September 4 ** ** Original version 2012-03-01 ** ** Copyright (C) 2013 Naoki Arita. See notes at end. */ { double t, el, elp, f, d, om, arg, dp, de, sarg, carg, dpsils, depsls, dpsipl, depspl; int i; /* Units of 0.1 microarcsecond to radians */ static const double U2R = DAS2R / 1e7; /* ---------------------------------------- */ /* Fixed offsets in lieu of planetary terms */ /* ---------------------------------------- */ static const double DPPLAN = -0.135 * DMAS2R; static const double DEPLAN = 0.388 * DMAS2R; /* --------------------------------------------------- */ /* Luni-solar nutation: argument and term coefficients */ /* --------------------------------------------------- */ /* The units for the sine and cosine coefficients are */ /* 0.1 microarcsec and the same per Julian century */ static const struct { int nl,nlp,nf,nd,nom; /* coefficients of l,l',F,D,Om */ double ps,pst,pc; /* longitude sin, t*sin, cos coefficients */ double ec,ect,es; /* obliquity cos, t*cos, sin coefficients */ } x[] = { /* 1-10 */ { 0, 0, 0, 0,1, -172064161.0, -174666.0, 33386.0, 92052331.0, 9086.0, 15377.0}, { 0, 0, 2,-2,2, -13170906.0, -1675.0, -13696.0, 5730336.0, -3015.0, -4587.0}, { 0, 0, 2, 0,2,-2276413.0,-234.0, 2796.0, 978459.0,-485.0,1374.0}, { 0, 0, 0, 0,2,2074554.0, 207.0, -698.0,-897492.0, 470.0,-291.0}, { 0, 1, 0, 0,0,1475877.0,-3633.0,11817.0, 73871.0,-184.0,-1924.0}, { 0, 1, 2,-2,2,-516821.0, 1226.0, -524.0, 224386.0,-677.0,-174.0}, { 1, 0, 0, 0,0, 711159.0, 73.0, -872.0, -6750.0, 0.0, 358.0}, { 0, 0, 2, 0,1,-387298.0, -367.0, 380.0, 200728.0, 18.0, 318.0}, { 1, 0, 2, 0,2,-301461.0, -36.0, 816.0, 129025.0, -63.0, 367.0}, { 0,-1, 2,-2,2, 215829.0, -494.0, 111.0, -95929.0, 299.0, 132.0}, /* 11-20 */ { 0, 0, 2,-2,1, 128227.0, 137.0, 181.0, -68982.0, -9.0, 39.0}, {-1, 0, 2, 0,2, 123457.0, 11.0, 19.0, -53311.0, 32.0, -4.0}, {-1, 0, 0, 2,0, 156994.0, 10.0, -168.0, -1235.0, 0.0, 82.0}, { 1, 0, 0, 0,1, 63110.0, 63.0, 27.0, -33228.0, 0.0, -9.0}, {-1, 0, 0, 0,1, -57976.0, -63.0, -189.0, 31429.0, 0.0, -75.0}, {-1, 0, 2, 2,2, -59641.0, -11.0, 149.0, 25543.0, -11.0, 66.0}, { 1, 0, 2, 0,1, -51613.0, -42.0, 129.0, 26366.0, 0.0, 78.0}, {-2, 0, 2, 0,1, 45893.0, 50.0, 31.0, -24236.0, -10.0, 20.0}, { 0, 0, 0, 2,0, 63384.0, 11.0, -150.0, -1220.0, 0.0, 29.0}, { 0, 0, 2, 2,2, -38571.0, -1.0, 158.0, 16452.0, -11.0, 68.0}, /* 21-30 */ { 0,-2, 2,-2,2, 32481.0, 0.0, 0.0, -13870.0, 0.0, 0.0}, {-2, 0, 0, 2,0, -47722.0, 0.0, -18.0, 477.0, 0.0, -25.0}, { 2, 0, 2, 0,2, -31046.0, -1.0, 131.0, 13238.0, -11.0, 59.0}, { 1, 0, 2,-2,2, 28593.0, 0.0, -1.0, -12338.0, 10.0, -3.0}, {-1, 0, 2, 0,1, 20441.0, 21.0, 10.0, -10758.0, 0.0, -3.0}, { 2, 0, 0, 0,0, 29243.0, 0.0, -74.0, -609.0, 0.0, 13.0}, { 0, 0, 2, 0,0, 25887.0, 0.0, -66.0, -550.0, 0.0, 11.0}, { 0, 1, 0, 0,1, -14053.0, -25.0, 79.0, 8551.0, -2.0, -45.0}, {-1, 0, 0, 2,1, 15164.0, 10.0, 11.0, -8001.0, 0.0, -1.0}, { 0, 2, 2,-2,2, -15794.0, 72.0, -16.0, 6850.0, -42.0, -5.0}, /* 31-40 */ { 0, 0,-2, 2,0, 21783.0, 0.0, 13.0, -167.0, 0.0, 13.0}, { 1, 0, 0,-2,1, -12873.0, -10.0, -37.0, 6953.0, 0.0, -14.0}, { 0,-1, 0, 0,1, -12654.0, 11.0, 63.0, 6415.0, 0.0, 26.0}, {-1, 0, 2, 2,1, -10204.0, 0.0, 25.0, 5222.0, 0.0, 15.0}, { 0, 2, 0, 0,0, 16707.0, -85.0, -10.0, 168.0, -1.0, 10.0}, { 1, 0, 2, 2,2, -7691.0, 0.0, 44.0, 3268.0, 0.0, 19.0}, {-2, 0, 2, 0,0, -11024.0, 0.0, -14.0, 104.0, 0.0, 2.0}, { 0, 1, 2, 0,2, 7566.0, -21.0, -11.0, -3250.0, 0.0, -5.0}, { 0, 0, 2, 2,1, -6637.0, -11.0, 25.0, 3353.0, 0.0, 14.0}, { 0,-1, 2, 0,2, -7141.0, 21.0, 8.0, 3070.0, 0.0, 4.0}, /* 41-50 */ { 0, 0, 0, 2,1, -6302.0, -11.0, 2.0, 3272.0, 0.0, 4.0}, { 1, 0, 2,-2,1, 5800.0, 10.0, 2.0, -3045.0, 0.0, -1.0}, { 2, 0, 2,-2,2, 6443.0, 0.0, -7.0, -2768.0, 0.0, -4.0}, {-2, 0, 0, 2,1, -5774.0, -11.0, -15.0, 3041.0, 0.0, -5.0}, { 2, 0, 2, 0,1, -5350.0, 0.0, 21.0, 2695.0, 0.0, 12.0}, { 0,-1, 2,-2,1, -4752.0, -11.0, -3.0, 2719.0, 0.0, -3.0}, { 0, 0, 0,-2,1, -4940.0, -11.0, -21.0, 2720.0, 0.0, -9.0}, {-1,-1, 0, 2,0, 7350.0, 0.0, -8.0, -51.0, 0.0, 4.0}, { 2, 0, 0,-2,1, 4065.0, 0.0, 6.0, -2206.0, 0.0, 1.0}, { 1, 0, 0, 2,0, 6579.0, 0.0, -24.0, -199.0, 0.0, 2.0}, /* 51-60 */ { 0, 1, 2,-2,1, 3579.0, 0.0, 5.0, -1900.0, 0.0, 1.0}, { 1,-1, 0, 0,0, 4725.0, 0.0, -6.0, -41.0, 0.0, 3.0}, {-2, 0, 2, 0,2, -3075.0, 0.0, -2.0, 1313.0, 0.0, -1.0}, { 3, 0, 2, 0,2, -2904.0, 0.0, 15.0, 1233.0, 0.0, 7.0}, { 0,-1, 0, 2,0, 4348.0, 0.0, -10.0, -81.0, 0.0, 2.0}, { 1,-1, 2, 0,2, -2878.0, 0.0, 8.0, 1232.0, 0.0, 4.0}, { 0, 0, 0, 1,0, -4230.0, 0.0, 5.0, -20.0, 0.0, -2.0}, {-1,-1, 2, 2,2, -2819.0, 0.0, 7.0, 1207.0, 0.0, 3.0}, {-1, 0, 2, 0,0, -4056.0, 0.0, 5.0, 40.0, 0.0, -2.0}, { 0,-1, 2, 2,2, -2647.0, 0.0, 11.0, 1129.0, 0.0, 5.0}, /* 61-70 */ {-2, 0, 0, 0,1, -2294.0, 0.0, -10.0, 1266.0, 0.0, -4.0}, { 1, 1, 2, 0,2, 2481.0, 0.0, -7.0, -1062.0, 0.0, -3.0}, { 2, 0, 0, 0,1, 2179.0, 0.0, -2.0, -1129.0, 0.0, -2.0}, {-1, 1, 0, 1,0, 3276.0, 0.0, 1.0, -9.0, 0.0, 0.0}, { 1, 1, 0, 0,0, -3389.0, 0.0, 5.0, 35.0, 0.0, -2.0}, { 1, 0, 2, 0,0, 3339.0, 0.0, -13.0, -107.0, 0.0, 1.0}, {-1, 0, 2,-2,1, -1987.0, 0.0, -6.0, 1073.0, 0.0, -2.0}, { 1, 0, 0, 0,2, -1981.0, 0.0, 0.0, 854.0, 0.0, 0.0}, {-1, 0, 0, 1,0, 4026.0, 0.0, -353.0, -553.0, 0.0,-139.0}, { 0, 0, 2, 1,2, 1660.0, 0.0, -5.0, -710.0, 0.0, -2.0}, /* 71-77 */ {-1, 0, 2, 4,2, -1521.0, 0.0, 9.0, 647.0, 0.0, 4.0}, {-1, 1, 0, 1,1, 1314.0, 0.0, 0.0, -700.0, 0.0, 0.0}, { 0,-2, 2,-2,1, -1283.0, 0.0, 0.0, 672.0, 0.0, 0.0}, { 1, 0, 2, 2,1, -1331.0, 0.0, 8.0, 663.0, 0.0, 4.0}, {-2, 0, 2, 2,2, 1383.0, 0.0, -2.0, -594.0, 0.0, -2.0}, {-1, 0, 0, 0,2, 1405.0, 0.0, 4.0, -610.0, 0.0, 2.0}, { 1, 1, 2,-2,2, 1290.0, 0.0, 0.0, -556.0, 0.0, 0.0} }; /* Number of terms in the series */ const int NLS = (int) (sizeof x / sizeof x[0]); /*--------------------------------------------------------------------*/ /* Interval between fundamental epoch J2000.0 and given date (JC). */ t = ((date1 - DJ00) + date2) / DJC; /* --------------------*/ /* LUNI-SOLAR NUTATION */ /* --------------------*/ /* Fundamental (Delaunay) arguments from Simon et al. (1994) */ /* Mean anomaly of the Moon. */ el = fmod(485868.249036 +<PHONE_NUMBER>.2178) * t, TURNAS) * DAS2R; /* Mean anomaly of the Sun. */ elp = fmod(1287104.79305 + (129596581.0481) * t, TURNAS) * DAS2R; /* Mean argument of the latitude of the Moon. */ f = fmod(335779.526232 +<PHONE_NUMBER>.8478) * t, TURNAS) * DAS2R; /* Mean elongation of the Moon from the Sun. */ d = fmod(1072260.70369 +<PHONE_NUMBER>.2090) * t, TURNAS) * DAS2R; /* Mean longitude of the ascending node of the Moon. */ om = fmod(450160.398036 + (-6962890.5431) * t, TURNAS) * DAS2R; /* Initialize the nutation values. */ dp = 0.0; de = 0.0; /* Summation of luni-solar nutation series (smallest terms first). */ for (i = NLS-1; i >= 0; i--) { /* Argument and functions. */ arg = fmod( (double)x[i].nl * el + (double)x[i].nlp * elp + (double)x[i].nf * f + (double)x[i].nd * d + (double)x[i].nom * om, D2PI ); sarg = sin(arg); carg = cos(arg); /* Term. */ dp += (x[i].ps + x[i].pst * t) * sarg + x[i].pc * carg; de += (x[i].ec + x[i].ect * t) * carg + x[i].es * sarg; } /* Convert from 0.1 microarcsec units to radians. */ dpsils = dp * U2R; depsls = de * U2R; /* ------------------------------*/ /* IN LIEU OF PLANETARY NUTATION */ /* ------------------------------*/ /* Fixed offset to correct for missing terms in truncated series. */ dpsipl = DPPLAN; depspl = DEPLAN; /* --------*/ /* RESULTS */ /* --------*/ /* Add luni-solar and planetary components. */ *dpsi = dpsils + dpsipl; *deps = depsls + depspl; return; /*---------------------------------------------------------------------- ** ** Celes is a wrapper of the SOFA Library for Ruby. ** ** This file is redistributed and relicensed in accordance with ** the SOFA Software License (http://www.iausofa.org/tandc.html). ** ** The original library is available from IAU Standards of ** Fundamental Astronomy (http://www.iausofa.org/). ** ** ** ** ** ** Copyright (C) 2013, Naoki Arita ** All rights reserved. ** ** Redistribution and use in source and binary forms, with or without ** modification, are permitted provided that the following conditions ** are met: ** ** 1 Redistributions of source code must retain the above copyright ** notice, this list of conditions and the following disclaimer. ** ** 2 Redistributions in binary form must reproduce the above copyright ** notice, this list of conditions and the following disclaimer in ** the documentation and/or other materials provided with the ** distribution. ** ** 3 Neither the name of the Standards Of Fundamental Astronomy Board, ** the International Astronomical Union nor the names of its ** contributors may be used to endorse or promote products derived ** from this software without specific prior written permission.   ** **--------------------------------------------------------------------*/ }


Folks,
I'm using emonbase using the latest emonhub that cames with SD - after the first boot, I login, configured everything and worked, however after the first reboot, I'm unable to make it work again - using the browser I got the follow message:
Can't connect to redis at localhost:6379 , it may be that redis-server is not installed or started see readme for redis installation
If I try to initialize the redis-server I got a error message and here is status message:
redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled)
Active: failed (Result: start-limit) since Mon 2016-01-25 07:44:53 GMT; 25s ago
Process: 1921 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=1/FA
Jan 25 07:44:52 emonpi systemd[1]: Failed to start Advanced key-value store.
Jan 25 07:44:52 emonpi systemd[1]: Unit redis-server.service entered failed state.
Jan 25 07:44:53 emonpi systemd[1]: redis-server.service holdoff time over, scheduling restart.
Jan 25 07:44:53 emonpi systemd[1]: Stopping Advanced key-value store...
Jan 25 07:44:53 emonpi systemd[1]: Starting Advanced key-value store...
Jan 25 07:44:53 emonpi systemd[1]: redis-server.service start request repeated too quickly, ref
Jan 25 07:44:53 emonpi systemd[1]: Failed to start Advanced key-value store.
Jan 25 07:44:53 emonpi systemd[1]: Unit redis-server.service entered failed state.
I already tried a fresh image and the same happen after the first reboot.
Any clue on what can be happening here?
Best Regards!
-BD
Re: Redis-server failing to start
I am experiencing the exact same thing. I received my new RFMPI card today. Installed it and rebooted and gone.
I am finding that the /var/lib directory is empty except for two directories (container and systemd). I have been trying to reload images over the last two hours with everything disconnected and still having no luck.
My next effort is to try the 17 Jun image and see if that helps.
Stuart
Re: Redis-server failing to start
I noted that there was a recent change (20 hours ago at the time of writing this comment) to the way that /var/lib is mounted. I am wondering if this has something to do with it? And I am guessing that during the first boot when the system automatically updates itself that it is picking up this change.
Stuart
Re: Redis-server failing to start
I think it's that. I had a working system. Did an update, rebooted and poof, this "error".
Edit - wrapped long line - Moderator, BT
Re: Redis-server failing to start
OK, so I found that if I went back to the 17 Jun image, all was fine but I prefer the new latest evrsion.
It is definetly related to the new change whereby the /var/lib is being mounted to tmpfs. You can see below the two lines with the - which were replaced with the one line with the +
To workaround, I have disabled the cron job to update every minute which stops this change from being updated to the /etc/fstab file and then edited the /etc/fstab file to reverse the changes made.
EmonCMS comes back to life, I figure that this will have to be done everytime you do an update until this issue is fixed.
tmpfs /tmp tmpfs nodev,nosuid,size=30M,mode=1777 0 0
tmpfs /var/log tmpfs nodev,nosuid,size=50M,mode=1777 0 0
-tmpfs /var/lib/dhcp tmpfs nodev,nosuid,size=1M,mode=1777 0 0
-tmpfs /var/lib/openhab tmpfs nodev,nosuid,size=40M,mode=1777 0 0
+tmpfs /var/lib tmpfs nodev,nosuid,size=150M,mode=1777 0 0
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /boot vfat defaults,noatime,nodiratime 0 2
/dev/mmcblk0p2 / ext4 defaults,ro,noatime,nodiratime,errors=remount-ro 0 1


On the Compiler | Java Compiler page, you can select the Java compiler to be used and specify associated options.


Facecode Systems - WIP
This website is currently being worked on. In the meanwhile, here is
the link to this site
.


Everfave is a social couponing app where users can earn rewards for their favorite stores and brands when they share them through social media. Our client asked us to conduct interviews and user testing in order to answer a few questions regarding this app:
1. Are users willing to complete the process of sharing stores and brands on their social media in order to get a coupon?
2. Does icon placement of the different sharing options affect which option users will choose?
3. Would users customize the sharing message with a picture if they could?
4. If the user were the one receiving the shared message from a friend, would it be more appealing if their friend had shared a picture?
5. Do they prefer to sign up before they see the coupon or after (but before they can redeem)?


Heating and Water
Our company carries out installation, service and repair of water and gas appliances
Quiet Operations
Our team uses only the best and particularly low-noise drive components
Wide Selection
We offer a wide range of high quality water heaters and conditioning supplies
Energy Efficiency
Our company offers the most efficient and the greenest options for home heating.
Chauffage & Climatisation
Services & Réparation
Time for a New System?
Call an Frigetec Maroc today for a quote on your
new home comfort system.
Comment nous pouvons vous aider ?
Services & Offres
Request a Quote
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempo labore et dolor.
High-Efficiency Systems
Frigetec Maroc Advantage
Energy Efficiency
Our company offers the most efficient and the greenest options for home heating.
Wide Selection
We offer a wide range of high quality water heaters and conditioning supplies
Quiet Operations
Our team uses only the best and particularly low-noise drive components
Heating and Water
Our company carries out installation, service and repair of water and gas appliances
Customer Reviews
Specials
News & Events
Latest News
Tips for Saving Money on Your Heating Bills
Sed ut perspiciatis, unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam eaque ipsa, quae ab illo...
Read MoreAir Conditioning Installation And Maintenance Guide
Sed ut perspiciatis, unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam eaque ipsa, quae ab illo...
Read MoreBuilding Performance Evaluations & Improvements
Sed ut perspiciatis, unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam eaque ipsa, quae ab illo...
Read More


This package contains the tests for all the classes in the com.compomics.util.math package.
@see com.compomics.util.math


2.3 Precompiled Binaries
Some Unix distributions include, or make available, precompiled
Squid packages. For Linux, you can easily find Squid RPMs. Often the
Squid RPM is included on Linux CD-ROMs you can buy. The
FreeBSD/NetBSD/OpenBSD distributions also contain Squid in their
ports and/or packages collections.
While RPMs and precompiled packages may initially save you some time,
they also have some drawbacks. As I already mentioned, certain
features must be enabled or disabled before you
start compiling Squid. The precompiled package that you install may
not have the particular feature you want. Furthermore,
Squid's ./configure script probes
your operating system for certain parameters. These parameters may be
configured differently on your machine on which Squid was compiled.
Finally, if you want to apply a patch to Squid,
you'll either have to wait for someone to build a
new RPM/package or get the source and do it yourself.
I strongly encourage you to compile Squid from the source, but the
decision is yours to make.
|


vdussault (Tue, 23 Apr 2019 17:32:53 GMT):
Has joined the channel.
vdussault (Sat, 08 Jun 2019 13:18:34 GMT):
La ville de Mtl cherche des solutions innovante pour le stationnement. Si on veut mettre en place un système de paiement basé sur API ouvert (et collecte de données bien entendu), vous avez des idées ou exemples d'approches ou de villes? @gabriel.plassat @leofrachet @F8Full @elsa
leofrachet (Sat, 08 Jun 2019 13:18:35 GMT):
Has joined the channel.
F8Full (Sat, 08 Jun 2019 13:18:35 GMT):
Has joined the channel.
gabriel.plassat (Sat, 08 Jun 2019 13:18:35 GMT):
Has joined the channel.
elsa (Sat, 08 Jun 2019 13:18:35 GMT):
Has joined the channel.
gabriel.plassat (Sat, 08 Jun 2019 18:47:01 GMT):
Il y a keyple solution de billetique open source. Sinon je peux demander à ex-parkeon mais pour ça il faudrait avoir le besoin exact de la ville .
vdussault (Sun, 09 Jun 2019 11:28:11 GMT):
[ ](https://chat.fabmob.io/channel/open_api?msg=Fv4ZqYCDxGN69eCbK) @gabriel.plassat J'ai trouvé ça: (j'ai ajouté l'acteur dans le wiki ) https://uk.news.yahoo.com/parking-woes-could-ended-data-230100926.html?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAAI3H8uOBOgyRMVnF18ItiplAYLFaJFYOiqQaTuX4Uu0JWGc5MPatkHGGxFWXkuhKnWu5r7dQd_pygVv8XXsYGyvwsaSyNpcR432dB_TYJLcVJXjURZGUrTWd6bahd5r1PyZBntMdDHlYyEf_17-rkBKgrbsWzalDW33AmVhuI75A
F8Full (Thu, 27 Jun 2019 14:54:25 GMT):
Pardon j'avais raté ce message. Possible de voir si la solution présentement en place peut etre adaptée ?
vdussault (Thu, 27 Jun 2019 15:31:28 GMT):
[ ](https://chat.fabmob.io/channel/open_api?msg=Nf85NsGNauo7fsTNH) @F8Full Non, mais en fonction du projet choisi par la ville, nous pourrons voir ce qu'il est possible de faire. :-)
F8Full (Thu, 27 Jun 2019 15:32:34 GMT):
[ ](https://chat.fabmob.io/channel/open_api?msg=6ZFWGkCRnH8o5zP9Q) @vdussault Oki. :) Malheureusement je n'ai pas d'info là dessus.
gabriel.plassat (Tue, 12 Nov 2019 16:03:46 GMT):
Le standard proposé par la ville de paris pour les données des trotinettes SIVU : https://github.com/CityOfParisInnovationData/service-interface-vehicle-use - Service interface for vehicle use (SIVU) is a data specification for free-floating vehicles providers REST API. SIVU must be used by all operators that signed the charter "vélo/2RM libre-service" of the city of Paris. cc @vdussault @juliendelabaca64
vdussault (Tue, 12 Nov 2019 22:06:49 GMT):
Si quelqu'un est en mesure de faire un comparatif avec le MDS, je serais acheteur. :-)
johan (Wed, 11 Dec 2019 16:08:04 GMT):
Has joined the channel.
Caubel (Tue, 10 Mar 2020 16:54:31 GMT):
Has joined the channel.
laura.foglia (Tue, 10 Mar 2020 17:10:10 GMT):
Has joined the channel.
Jean.ROBERT (Tue, 10 Mar 2020 17:59:42 GMT):
Has joined the channel.
vdussault (Wed, 11 Mar 2020 13:36:50 GMT):
discussion très intéressante sur le MDS @philippe.fortin @gabriel.plassat https://micromobility.io/podcast/62-the-latest-on-the-war-over-micromobility-data-a-conversation-with-david-zipper
philippe.fortin (Wed, 11 Mar 2020 13:36:51 GMT):
Has joined the channel.
gabriel.plassat (Wed, 11 Mar 2020 14:34:36 GMT):
d'ailleurs sur le sujet des API, avez vous connaissance d'une bonne formation pour faire comprendre l'intérêt des API ?
johan (Thu, 12 Mar 2020 11:39:17 GMT):
On peut éventuellement proposer ça, à voir en fonction des attentes car le sujet est vaste !
yann.tremeac (Thu, 12 Mar 2020 12:19:19 GMT):
Has joined the channel.
jerome-poyet (Mon, 16 Mar 2020 14:16:44 GMT):
Has joined the channel.
laurence.mechin (Mon, 16 Mar 2020 14:32:31 GMT):
Has joined the channel.
mireille (Mon, 16 Mar 2020 14:34:06 GMT):
Has joined the channel.
pierre.taillant (Mon, 16 Mar 2020 14:47:09 GMT):
Has joined the channel.
remy.leboennec (Mon, 16 Mar 2020 15:27:46 GMT):
Has joined the channel.
lara.hoelting (Tue, 17 Mar 2020 13:31:27 GMT):
Has joined the channel.
nicolas.lb (Fri, 20 Mar 2020 10:47:49 GMT):
Has joined the channel.
kmog (Fri, 20 Mar 2020 11:55:28 GMT):
Has joined the channel.
lea.chretien (Fri, 20 Mar 2020 15:19:07 GMT):
Has joined the channel.
paul_bridier (Fri, 20 Mar 2020 16:08:59 GMT):
Has joined the channel.
Yao (Fri, 20 Mar 2020 19:07:50 GMT):
Has joined the channel.
cecile.lavernhe (Mon, 23 Mar 2020 09:37:28 GMT):
Has joined the channel.
marc.cottignies (Mon, 23 Mar 2020 10:30:14 GMT):
Has joined the channel.
sandrine.carballes (Mon, 23 Mar 2020 10:50:22 GMT):
Has joined the channel.
Kiki (Mon, 23 Mar 2020 13:05:51 GMT):
Has joined the channel.
louise.kold-taylor (Mon, 23 Mar 2020 18:31:53 GMT):
Has joined the channel.
ClaraB (Sun, 29 Mar 2020 15:05:13 GMT):
Has joined the channel.
emmanuel.poisson-quinton (Mon, 30 Mar 2020 08:54:32 GMT):
Has joined the channel.
Cath (Mon, 30 Mar 2020 18:46:58 GMT):
Has joined the channel.
pony (Wed, 01 Apr 2020 09:23:40 GMT):
Has joined the channel.
salvatore.cimmino (Fri, 03 Apr 2020 13:51:37 GMT):
Has joined the channel.
karine (Sat, 04 Apr 2020 19:51:30 GMT):
Has joined the channel.
camillem (Sun, 05 Apr 2020 18:35:45 GMT):
Has joined the channel.
jonatan.cloutier (Tue, 07 Apr 2020 20:47:35 GMT):
Has joined the channel.
marie-pierre.gendron (Fri, 10 Apr 2020 14:42:05 GMT):
Has joined the channel.
Jesse (Fri, 10 Apr 2020 20:41:11 GMT):
Has joined the channel.
gontrand.dumont (Fri, 10 Apr 2020 20:55:01 GMT):
Has joined the channel.
xavier.massicotte (Fri, 10 Apr 2020 21:00:36 GMT):
Has joined the channel.
clem (Fri, 10 Apr 2020 21:28:11 GMT):
Has joined the channel.
marie.tack (Fri, 10 Apr 2020 21:52:00 GMT):
Has joined the channel.
Ysaia (Sat, 11 Apr 2020 01:32:32 GMT):
Has joined the channel.
ameliepb (Sat, 11 Apr 2020 14:18:09 GMT):
Has joined the channel.
laurent.lewis (Sun, 12 Apr 2020 16:22:41 GMT):
Has joined the channel.
Amelie (Sun, 12 Apr 2020 22:36:33 GMT):
Has joined the channel.
maude.lapointe (Mon, 13 Apr 2020 15:33:30 GMT):
Has joined the channel.
melissa.dlf (Mon, 13 Apr 2020 16:04:06 GMT):
Has joined the channel.
eva.murith (Mon, 13 Apr 2020 18:27:03 GMT):
Has joined the channel.
mathieu.couture (Mon, 13 Apr 2020 19:23:57 GMT):
Has joined the channel.
penelope.stuart (Mon, 13 Apr 2020 19:32:10 GMT):
Has joined the channel.
guillaume.fortin (Mon, 13 Apr 2020 19:34:23 GMT):
Has joined the channel.
chloe.fortier.devin (Mon, 13 Apr 2020 19:36:21 GMT):
Has joined the channel.
Romain_Gayet (Mon, 13 Apr 2020 19:37:26 GMT):
Has joined the channel.
nestel.jeremie (Tue, 14 Apr 2020 09:23:55 GMT):
Has joined the channel.
HeleneCauchoix (Tue, 14 Apr 2020 18:50:35 GMT):
Has joined the channel.
marie-helene.beaudry (Tue, 14 Apr 2020 22:35:30 GMT):
Has joined the channel.
mathieu.couture (Wed, 15 Apr 2020 14:12:16 GMT):
Has left the channel.
alexandre g (Fri, 17 Apr 2020 10:04:31 GMT):
Has joined the channel.
test_du_nouveau_bouton (Fri, 17 Apr 2020 13:01:05 GMT):
Has joined the channel.
ju.tav (Fri, 17 Apr 2020 16:34:00 GMT):
Has joined the channel.
Arthur (Fri, 17 Apr 2020 16:43:00 GMT):
Has joined the channel.
Pierre_Lagrandmaison (Mon, 20 Apr 2020 14:48:33 GMT):
Has joined the channel.
diana.borda (Wed, 22 Apr 2020 02:01:20 GMT):
Has joined the channel.
marie-reine.roy (Thu, 23 Apr 2020 13:00:41 GMT):
Has joined the channel.
ValerieM (Thu, 23 Apr 2020 16:47:02 GMT):
Has joined the channel.
melanie.marceau-d (Fri, 24 Apr 2020 15:33:27 GMT):
Has joined the channel.
cynthia.hamel-kropf (Sun, 26 Apr 2020 20:33:46 GMT):
Has joined the channel.
BENOIT_TROUVE (Mon, 27 Apr 2020 06:16:36 GMT):
Has joined the channel.
ali.saidi (Mon, 27 Apr 2020 20:08:17 GMT):
Has joined the channel.
AnneJulie_AB (Mon, 27 Apr 2020 22:22:55 GMT):
Has joined the channel.
alexandre.barreto (Tue, 28 Apr 2020 07:17:02 GMT):
Has joined the channel.
thierry.lachapelle (Tue, 28 Apr 2020 12:27:37 GMT):
Has joined the channel.
clement (Tue, 28 Apr 2020 17:37:13 GMT):
Has joined the channel.
helene.dimanche (Tue, 28 Apr 2020 20:28:58 GMT):
Has joined the channel.
Julie-Scheid (Wed, 29 Apr 2020 14:27:13 GMT):
Has joined the channel.
veloma (Wed, 29 Apr 2020 18:55:39 GMT):
Has joined the channel.
leandre (Wed, 29 Apr 2020 23:06:08 GMT):
Has joined the channel.
camille.jolain (Fri, 01 May 2020 01:54:00 GMT):
Has joined the channel.
johanne.belle-isle (Fri, 01 May 2020 17:07:03 GMT):
Has joined the channel.
RPP-Ysaia-Melanie-Chloe (Fri, 01 May 2020 18:53:45 GMT):
Has joined the channel.
damien.lhouillier (Mon, 04 May 2020 13:59:59 GMT):
Has joined the channel.
tqmn (Mon, 04 May 2020 16:12:37 GMT):
Has joined the channel.
gabriel.plassat (Sun, 06 Dec 2020 15:43:36 GMT):
@all je voudrai afficher le résultat de cette requete sur une page web
POST /v0/reports/9000000411 HTTP/1.1
Host: telraam-api.net
Content-Type: application/json
Content-Length: 134
{
"time_start": "2020-10-10 00:00:00Z",
"time_end": "2020-11-11 23:59:00Z",
"level": "segments",
"format":"per-hour"
}
gabriel.plassat (Sun, 06 Dec 2020 15:43:51 GMT):
quelqu'un sait faire ?


Survey Form
survey form by Certil and Misa
* Name:
* Email:
* Phone:
What do you think about microverse?
Select an option
great
not too great
It's sometghing
Prefer not to say
do you like coffe?
yes
no
What sports do you like?
soccer
Golf
What about you?
Send it!
Hello world! we are software developers!


tabula
Extract tables from PDF files.
More information: home page
- Extract all tables from a PDF to a CSV file:
tabula -o file.csv file.pdf
- Extract all tables from a PDF to a JSON file:
tabula --format JSON -o file.json file.pdf
- Extract tables from pages 1, 2, 3, and 6 of a PDF:
tabula --pages 1-3,6 file.pdf
- Extract tables from page 1 of a PDF, guessing which portion of the page to examine:
tabula --guess --pages 1 file.pdf
- Extract all tables from a PDF, using ruling lines to determine cell boundaries:
tabula --spreadsheet file.pdf
- Extract all tables from a PDF, using blank space to determine cell boundaries:
tabula --no-spreadsheet file.pdf


bigot
`Prev `__
B
`Next `__
--------------
**bigot**: n.
[common] A person who is religiously attached to a particular computer,
language, operating system, editor, or other tool (see `*religious
issues* <../R/religious-issues.html>`__). Usually found with a
specifier; thus, Cray bigot, ITS bigot, APL bigot, VMS bigot, Berkeley
bigot. Real bigots can be distinguished from mere partisans or zealots
by the fact that they refuse to learn alternatives even when the march
of time and/or technology is threatening to obsolete the favored tool.
It is truly said “You can tell a bigot, but you can't tell him much.”
Compare `*weenie* <../W/weenie.html>`__, `*Amiga Persecution
Complex* <../A/Amiga-Persecution-Complex.html>`__.
--------------
+---------------------------+----------------------------+---------------------------------+
| `Prev `__ | `Up <../B.html>`__ | `Next `__ |
+---------------------------+----------------------------+---------------------------------+
| bignum | `Home <../index.html>`__ | bikeshedding |
+---------------------------+----------------------------+---------------------------------+


Instructions :
- Use 'LEFT ARROW' key OR 'A' to move left.
- Use 'UP ARROW' key OR 'W' to move upwords.
- Use 'RIGHT ARROW' key OR 'D' to move right.
- Use 'DOWN ARROW' key OR 'S' to move downwords.
- Eat food to make your snake Grow.
- Eat bonus food to make your score high.
- SCORE : +2 | SCORE : +5
- Eat bonus before it disappears (within 3 sec).
- Use Space to PAUSE.