Vim documentation: quickfix
main help file*quickfix.txt* For Vim version 7.2. Last change: 2008 Mar 14 VIM REFERENCE MANUAL by Bram Moolenaar This subject is introduced in section |30.1| of the user manual. 1. Using QuickFix commands |quickfix| 2. The error window |quickfix-window| 3. Using more than one list of errors |quickfix-error-lists| 4. Using :make |:make_makeprg| 5. Using :grep |grep| 6. Selecting a compiler |compiler-select| 7. The error format |error-file-format| 8. The directory stack |quickfix-directory-stack| 9. Specific error file formats |errorformats| {Vi does not have any of these commands} The quickfix commands are not available when the |+quickfix| feature was disabled at compile time. ============================================================================= 1. Using QuickFix commands *quickfix* *Quickfix* *E42* Vim has a special mode to speedup the edit-compile-edit cycle. This is inspired by the quickfix option of the Manx's Aztec C compiler on the Amiga. The idea is to save the error messages from the compiler in a file and use Vim to jump to the errors one by one. You can examine each problem and fix it, without having to remember all the error messages. In Vim the quickfix commands are used more generally to find a list of positions in files. For example, |:vimgrep| finds pattern matches. You can use the positions in a script with the |getqflist()| function. Thus you can do a lot more than the edit/compile/fix cycle! If you are using Manx's Aztec C compiler on the Amiga look here for how to use it with Vim: |quickfix-manx|. If you are using another compiler you should save the error messages in a file and start Vim with "vim -q filename". An easy way to do this is with the |:make| command (see below). The 'errorformat' option should be set to match the error messages from your compiler (see |errorformat| below). *location-list* *E776* A location list is similar to a quickfix list and contains a list of positions in files. A location list is associated with a window and each window can have a separate location list. A location list can be associated with only one window. The location list is independent of the quickfix list. When a window with a location list is split, the new window gets a copy of the location list. When there are no references to a location list, the location list is destroyed. The following quickfix commands can be used. The location list commands are similar to the quickfix commands, replacing the 'c' prefix in the quickfix command with 'l'. *:cc* :cc[!] [nr] Display error [nr]. If [nr] is omitted, the same error is displayed again. Without [!] this doesn't work when jumping to another buffer, the current buffer has been changed, there is the only window for the buffer and both 'hidden' and 'autowrite' are off. When jumping to another buffer with [!] any changes to the current buffer are lost, unless 'hidden' is set or there is another window for this buffer. The 'switchbuf' settings are respected when jumping to a buffer. *:ll* :ll[!] [nr] Same as ":cc", except the location list for the current window is used instead of the quickfix list. *:cn* *:cnext* *E553* :[count]cn[ext][!] Display the [count] next error in the list that includes a file name. If there are no file names at all, go to the [count] next error. See |:cc| for [!] and 'switchbuf'. *:lne* *:lnext* :[count]lne[xt][!] Same as ":cnext", except the location list for the current window is used instead of the quickfix list. :[count]cN[ext][!] *:cp* *:cprevious* *:cN* *:cNext* :[count]cp[revious][!] Display the [count] previous error in the list that includes a file name. If there are no file names at all, go to the [count] previous error. See |:cc| for [!] and 'switchbuf'. :[count]lN[ext][!] *:lp* *:lprevious* *:lN* *:lNext* :[count]lp[revious][!] Same as ":cNext" and ":cprevious", except the location list for the current window is used instead of the quickfix list. *:cnf* *:cnfile* :[count]cnf[ile][!] Display the first error in the [count] next file in the list that includes a file name. If there are no file names at all or if there is no next file, go to the [count] next error. See |:cc| for [!] and 'switchbuf'. *:lnf* *:lnfile* :[count]lnf[ile][!] Same as ":cnfile", except the location list for the current window is used instead of the quickfix list. :[count]cNf[ile][!] *:cpf* *:cpfile* *:cNf* *:cNfile* :[count]cpf[ile][!] Display the last error in the [count] previous file in the list that includes a file name. If there are no file names at all or if there is no next file, go to the [count] previous error. See |:cc| for [!] and 'switchbuf'. :[count]lNf[ile][!] *:lpf* *:lpfile* *:lNf* *:lNfile* :[count]lpf[ile][!] Same as ":cNfile" and ":cpfile", except the location list for the current window is used instead of the quickfix list. *:crewind* *:cr* :cr[ewind][!] [nr] Display error [nr]. If [nr] is omitted, the FIRST error is displayed. See |:cc|. *:lrewind* *:lr* :lr[ewind][!] [nr] Same as ":crewind", except the location list for the current window is used instead of the quickfix list. *:cfirst* *:cfir* :cfir[st][!] [nr] Same as ":crewind". *:lfirst* *:lfir* :lfir[st][!] [nr] Same as ":lrewind". *:clast* *:cla* :cla[st][!] [nr] Display error [nr]. If [nr] is omitted, the LAST error is displayed. See |:cc|. *:llast* *:lla* :lla[st][!] [nr] Same as ":clast", except the location list for the current window is used instead of the quickfix list. *:cq* *:cquit* :cq[uit][!] Quit Vim with an error code, so that the compiler will not compile the same file again. WARNING: All changes in files are lost! Also when the [!] is not used. It works like ":qall!" |:qall|, except that Vim returns a non-zero exit code. *:cf* *:cfile* :cf[ile][!] [errorfile] Read the error file and jump to the first error. This is done automatically when Vim is started with the -q option. You can use this command when you keep Vim running while compiling. If you give the name of the errorfile, the 'errorfile' option will be set to [errorfile]. See |:cc| for [!]. *:lf* *:lfile* :lf[ile][!] [errorfile] Same as ":cfile", except the location list for the current window is used instead of the quickfix list. You can not use the -q command-line option to set the location list. :cg[etfile] [errorfile] *:cg* *:cgetfile* Read the error file. Just like ":cfile" but don't jump to the first error. :lg[etfile] [errorfile] *:lg* *:lgetfile* Same as ":cgetfile", except the location list for the current window is used instead of the quickfix list. *:caddf* *:caddfile* :caddf[ile] [errorfile] Read the error file and add the errors from the errorfile to the current quickfix list. If a quickfix list is not present, then a new list is created. *:laddf* *:laddfile* :laddf[ile] [errorfile] Same as ":caddfile", except the location list for the current window is used instead of the quickfix list. *:cb* *:cbuffer* *E681* :cb[uffer][!] [bufnr] Read the error list from the current buffer. When [bufnr] is given it must be the number of a loaded buffer. That buffer will then be used instead of the current buffer. A range can be specified for the lines to be used. Otherwise all lines in the buffer are used. See |:cc| for [!]. *:lb* *:lbuffer* :lb[uffer][!] [bufnr] Same as ":cbuffer", except the location list for the current window is used instead of the quickfix list. *:cgetb* *:cgetbuffer* :cgetb[uffer] [bufnr] Read the error list from the current buffer. Just like ":cbuffer" but don't jump to the first error. *:lgetb* *:lgetbuffer* :lgetb[uffer] [bufnr] Same as ":cgetbuffer", except the location list for the current window is used instead of the quickfix list. *:caddb* *:caddbuffer* :caddb[uffer] [bufnr] Read the error list from the current buffer and add the errors to the current quickfix list. If a quickfix list is not present, then a new list is created. Otherwise, same as ":cbuffer". *:laddb* *:laddbuffer* :laddb[uffer] [bufnr] Same as ":caddbuffer", except the location list for the current window is used instead of the quickfix list. *:cex* *:cexpr* *E777* :cex[pr][!] {expr} Create a quickfix list using the result of {expr} and jump to the first error. If {expr} is a String, then each new-line terminated line in the String is processed using 'errorformat' and the result is added to the quickfix list. If {expr} is a List, then each String item in the list is processed and added to the quickfix list. Non String items in the List are ignored. See |:cc| for [!]. Examples: :cexpr system('grep -n xyz *') :cexpr getline(1, '$') *:lex* *:lexpr* :lex[pr][!] {expr} Same as ":cexpr", except the location list for the current window is used instead of the quickfix list. *:cgete* *:cgetexpr* :cgete[xpr] {expr} Create a quickfix list using the result of {expr}. Just like ":cexpr", but don't jump to the first error. *:lgete* *:lgetexpr* :lgete[xpr] {expr} Same as ":cgetexpr", except the location list for the current window is used instead of the quickfix list. *:cad* *:caddexpr* :cad[dexpr] {expr} Evaluate {expr} and add the resulting lines to the current quickfix list. If a quickfix list is not present, then a new list is created. The current cursor position will not be changed. See |:cexpr| for more information. Example: :g/mypattern/caddexpr expand("%") . ":" . line(".") . ":" . getline(".") *:lad* *:laddexpr* :lad[dexpr] {expr} Same as ":caddexpr", except the location list for the current window is used instead of the quickfix list. *:cl* *:clist* :cl[ist] [from] [, [to]] List all errors that are valid |quickfix-valid|. If numbers [from] and/or [to] are given, the respective range of errors is listed. A negative number counts from the last error backwards, -1 being the last error. The 'switchbuf' settings are respected when jumping to a buffer. :cl[ist]! [from] [, [to]] List all errors. *:lli* *:llist* :lli[st] [from] [, [to]] Same as ":clist", except the location list for the current window is used instead of the quickfix list. :lli[st]! [from] [, [to]] List all the entries in the location list for the current window. If you insert or delete lines, mostly the correct error location is still found because hidden marks are used. Sometimes, when the mark has been deleted for some reason, the message "line changed" is shown to warn you that the error location may not be correct. If you quit Vim and start again the marks are lost and the error locations may not be correct anymore. If vim is built with |+autocmd| support, two autocommands are available for running commands before and after a quickfix command (':make', ':grep' and so on) is executed. See |QuickFixCmdPre| and |QuickFixCmdPost| for details. *QuickFixCmdPost-example* When 'encoding' differs from the locale, the error messages may have a different encoding from what Vim is using. To convert the messages you can use this code: function QfMakeConv() let qflist = getqflist() for i in qflist let i.text = iconv(i.text, "cp936", "utf-8") endfor call setqflist(qflist) endfunction au QuickfixCmdPost make call QfMakeConv() ============================================================================= 2. The error window *quickfix-window* *:cope* *:copen* :cope[n] [height] Open a window to show the current list of errors. When [height] is given, the window becomes that high (if there is room). Otherwise the window is made ten lines high. The window will contain a special buffer, with 'buftype' equal to "quickfix". Don't change this! If there already is a quickfix window, it will be made the current window. It is not possible to open a second quickfix window. *:lop* *:lopen* :lop[en] [height] Open a window to show the location list for the current window. Works only when the location list for the current window is present. You can have more than one location window opened at a time. Otherwise, it acts the same as ":copen". *:ccl* *:cclose* :ccl[ose] Close the quickfix window. *:lcl* *:lclose* :lcl[ose] Close the window showing the location list for the current window. *:cw* *:cwindow* :cw[indow] [height] Open the quickfix window when there are recognized errors. If the window is already open and there are no recognized errors, close the window. *:lw* *:lwindow* :lw[indow] [height] Same as ":cwindow", except use the window showing the location list for the current window. Normally the quickfix window is at the bottom of the screen. If there are vertical splits, it's at the bottom of the rightmost column of windows. To make it always occupy the full width: :botright cwindow You can move the window around with |window-moving| commands. For example, to move it to the top: CTRL-W K The 'winfixheight' option will be set, which means that the window will mostly keep its height, ignoring 'winheight' and 'equalalways'. You can change the height manually (e.g., by dragging the status line above it with the mouse). In the quickfix window, each line is one error. The line number is equal to the error number. You can use ":.cc" to jump to the error under the cursor. Hitting the <Enter> key or double-clicking the mouse on a line has the same effect. The file containing the error is opened in the window above the quickfix window. If there already is a window for that file, it is used instead. If the buffer in the used window has changed, and the error is in another file, jumping to the error will fail. You will first have to make sure the window contains a buffer which can be abandoned. *CTRL-W_<Enter>* *CTRL-W_<CR>* You can use CTRL-W <Enter> to open a new window and jump to the error there. When the quickfix window has been filled, two autocommand events are triggered. First the 'filetype' option is set to "qf", which triggers the FileType event. Then the BufReadPost event is triggered, using "quickfix" for the buffer name. This can be used to perform some action on the listed errors. Example: au BufReadPost quickfix setlocal modifiable \ | silent exe 'g/^/s//\=line(".")." "/' \ | setlocal nomodifiable This prepends the line number to each line. Note the use of "\=" in the substitute string of the ":s" command, which is used to evaluate an expression. The BufWinEnter event is also triggered, again using "quickfix" for the buffer name. Note: Making changes in the quickfix window has no effect on the list of errors. 'modifiable' is off to avoid making changes. If you delete or insert lines anyway, the relation between the text and the error number is messed up. If you really want to do this, you could write the contents of the quickfix window to a file and use ":cfile" to have it parsed and used as the new error list. *location-list-window* The location list window displays the entries in a location list. When you open a location list window, it is created below the current window and displays the location list for the current window. The location list window is similar to the quickfix window, except that you can have more than one location list window open at a time. When you use a location list command in this window, the displayed location list is used. When you select a file from the location list window, the following steps are used to find a window to edit the file: 1. If a window with the location list displayed in the location list window is present, then the file is opened in that window. 2. If the above step fails and if the file is already opened in another window, then that window is used. 3. If the above step fails then an existing window showing a buffer with 'buftype' not set is used. 4. If the above step fails, then the file is edited in a new window. In all of the above cases, if the location list for the selected window is not yet set, then it is set to the location list displayed in the location list window. ============================================================================= 3. Using more than one list of errors *quickfix-error-lists* So far has been assumed that there is only one list of errors. Actually the ten last used lists are remembered. When starting a new list, the previous ones are automatically kept. Two commands can be used to access older error lists. They set one of the existing error lists as the current one. *:colder* *:col* *E380* :col[der] [count] Go to older error list. When [count] is given, do this [count] times. When already at the oldest error list, an error message is given. *:lolder* *:lol* :lol[der] [count] Same as ":colder", except use the location list for the current window instead of the quickfix list. *:cnewer* *:cnew* *E381* :cnew[er] [count] Go to newer error list. When [count] is given, do this [count] times. When already at the newest error list, an error message is given. *:lnewer* *:lnew* :lnew[er] [count] Same as ":cnewer", except use the location list for the current window instead of the quickfix list. When adding a new error list, it becomes the current list. When ":colder" has been used and ":make" or ":grep" is used to add a new error list, one newer list is overwritten. This is especially useful if you are browsing with ":grep" |grep|. If you want to keep the more recent error lists, use ":cnewer 99" first. ============================================================================= 4. Using :make *:make_makeprg* *:mak* *:make* :mak[e][!] [arguments] 1. If vim was built with |+autocmd|, all relevant |QuickFixCmdPre| autocommands are executed. 2. If the 'autowrite' option is on, write any changed buffers 3. An errorfile name is made from 'makeef'. If 'makeef' doesn't contain "##", and a file with this name already exists, it is deleted. 4. The program given with the 'makeprg' option is started (default "make") with the optional [arguments] and the output is saved in the errorfile (for Unix it is also echoed on the screen). 5. The errorfile is read using 'errorformat'. 6. If vim was built with |+autocmd|, all relevant |QuickFixCmdPost| autocommands are executed. See example below. 7. If [!] is not given the first error is jumped to. 8. The errorfile is deleted. 9. You can now move through the errors with commands like |:cnext| and |:cprevious|, see above. This command does not accept a comment, any " characters are considered part of the arguments. *:lmak* *:lmake* :lmak[e][!] [arguments] Same as ":make", except the location list for the current window is used instead of the quickfix list. The ":make" command executes the command given with the 'makeprg' option. This is done by passing the command to the shell given with the 'shell' option. This works almost like typing ":!{makeprg} [arguments] {shellpipe} {errorfile}". {makeprg} is the string given with the 'makeprg' option. Any command can be used, not just "make". Characters '%' and '#' are expanded as usual on a command-line. You can use "%<" to insert the current file name without extension, or "#<" to insert the alternate file name without extension, for example: :set makeprg=make\ #<.o [arguments] is anything that is typed after ":make". {shellpipe} is the 'shellpipe' option. {errorfile} is the 'makeef' option, with ## replaced to make it unique. The placeholder "$*" can be used for the argument list in {makeprog} if the command needs some additional characters after its arguments. The $* is replaced then by all arguments. Example: :set makeprg=latex\ \\\\nonstopmode\ \\\\input\\{$*} or simpler :let &mp = 'latex \\nonstopmode \\input\{$*}' "$*" can be given multiple times, for example: :set makeprg=gcc\ -o\ $*\ $* The 'shellpipe' option defaults to ">" for the Amiga, MS-DOS and Win32. This means that the output of the compiler is saved in a file and not shown on the screen directly. For Unix "| tee" is used. The compiler output is shown on the screen and saved in a file the same time. Depending on the shell used "|& tee" or "2>&1| tee" is the default, so stderr output will be included. If 'shellpipe' is empty, the {errorfile} part will be omitted. This is useful for compilers that write to an errorfile themselves (e.g., Manx's Amiga C). Using QuickFixCmdPost to fix the encoding It may be that 'encoding' is set to an encoding that differs from the messages your build program produces. This example shows how to fix this after Vim has read the error messages: function QfMakeConv() let qflist = getqflist() for i in qflist let i.text = iconv(i.text, "cp936", "utf-8") endfor call setqflist(qflist) endfunction au QuickfixCmdPost make call QfMakeConv() (Example by Faque Cheng)
5. Using :vimgrep and :grep *grep* *lid* Vim has two ways to find matches for a pattern: Internal and external. The advantage of the internal grep is that it works on all systems and uses the powerful Vim search patterns. An external grep program can be used when the Vim grep does not do what you want. The internal method will be slower, because files are read into memory. The advantages are: - Line separators and encoding are automatically recognized, as if a file is being edited. - Uses Vim search patterns. Multi-line patterns can be used. - When plugins are enabled: compressed and remote files can be searched. |gzip| |netrw| To be able to do this Vim loads each file as if it is being edited. When there is no match in the file the associated buffer is wiped out again. The 'hidden' option is ignored here to avoid running out of memory or file descriptors when searching many files. However, when the |:hide| command modifier is used the buffers are kept loaded. This makes following searches in the same files a lot faster. 5.1 using Vim's internal grep *:vim* *:vimgrep* *E682* *E683* :vim[grep][!] /{pattern}/[g][j] {file} ... Search for {pattern} in the files {file} ... and set the error list to the matches. Without the 'g' flag each line is added only once. With 'g' every match is added. {pattern} is a Vim search pattern. Instead of enclosing it in / any non-ID character (see |'isident'|) can be used, so long as it does not appear in {pattern}. 'ignorecase' applies. To overrule it put |/\c| in the pattern to ignore case or |/\C| to match case. 'smartcase' is not used. When a number is put before the command this is used as the maximum number of matches to find. Use ":1vimgrep pattern file" to find only the first. Useful if you only want to check if there is a match and quit quickly when it's found. Without the 'j' flag Vim jumps to the first match. With 'j' only the quickfix list is updated. With the [!] any changes in the current buffer are abandoned. Every second or so the searched file name is displayed to give you an idea of the progress made. Examples: :vimgrep /an error/ *.c :vimgrep /\<FileName\>/ *.h include/* :vimgrep /myfunc/ **/*.c For the use of "**" see |starstar-wildcard|. :vim[grep][!] {pattern} {file} ... Like above, but instead of enclosing the pattern in a non-ID character use a white-separated pattern. The pattern must start with an ID character. Example: :vimgrep Error *.c *:lv* *:lvimgrep* :lv[imgrep][!] /{pattern}/[g][j] {file} ... :lv[imgrep][!] {pattern} {file} ... Same as ":vimgrep", except the location list for the current window is used instead of the quickfix list. *:vimgrepa* *:vimgrepadd* :vimgrepa[dd][!] /{pattern}/[g][j] {file} ... :vimgrepa[dd][!] {pattern} {file} ... Just like ":vimgrep", but instead of making a new list of errors the matches are appended to the current list. *:lvimgrepa* *:lvimgrepadd* :lvimgrepa[dd][!] /{pattern}/[g][j] {file} ... :lvimgrepa[dd][!] {pattern} {file} ... Same as ":vimgrepadd", except the location list for the current window is used instead of the quickfix list. 5.2 External grep Vim can interface with "grep" and grep-like programs (such as the GNU id-utils) in a similar way to its compiler integration (see |:make| above). [Unix trivia: The name for the Unix "grep" command comes from ":g/re/p", where "re" stands for Regular Expression.] *:gr* *:grep* :gr[ep][!] [arguments] Just like ":make", but use 'grepprg' instead of 'makeprg' and 'grepformat' instead of 'errorformat'. When 'grepprg' is "internal" this works like |:vimgrep|. Note that the pattern needs to be enclosed in separator characters then. *:lgr* *:lgrep* :lgr[ep][!] [arguments] Same as ":grep", except the location list for the current window is used instead of the quickfix list. *:grepa* *:grepadd* :grepa[dd][!] [arguments] Just like ":grep", but instead of making a new list of errors the matches are appended to the current list. Example: :grep nothing % :bufdo grepadd! something % The first command makes a new error list which is empty. The second command executes "grepadd" for each listed buffer. Note the use of ! to avoid that ":grepadd" jumps to the first error, which is not allowed with |:bufdo|. *:lgrepa* *:lgrepadd* :lgrepa[dd][!] [arguments] Same as ":grepadd", except the location list for the current window is used instead of the quickfix list. 5.3 Setting up external grep If you have a standard "grep" program installed, the :grep command may work well with the defaults. The syntax is very similar to the standard command: :grep foo *.c Will search all files with the .c extension for the substring "foo". The arguments to :grep are passed straight to the "grep" program, so you can use whatever options your "grep" supports. By default, :grep invokes grep with the -n option (show file and line numbers). You can change this with the 'grepprg' option. You will need to set 'grepprg' if: a) You are using a program that isn't called "grep" b) You have to call grep with a full path c) You want to pass other options automatically (e.g. case insensitive search.) Once "grep" has executed, Vim parses the results using the 'grepformat' option. This option works in the same way as the 'errorformat' option - see that for details. You may need to change 'grepformat' from the default if your grep outputs in a non-standard format, or you are using some other program with a special format. Once the results are parsed, Vim loads the first file containing a match and jumps to the appropriate line, in the same way that it jumps to a compiler error in |quickfix| mode. You can then use the |:cnext|, |:clist|, etc. commands to see the other matches. 5.4 Using :grep with id-utils You can set up :grep to work with the GNU id-utils like this: :set grepprg=lid\ -Rgrep\ -s :set grepformat=%f:%l:%m then :grep (regexp) works just as you'd expect. (provided you remembered to mkid first :) 5.5 Browsing source code with :vimgrep or :grep Using the stack of error lists that Vim keeps, you can browse your files to look for functions and the functions they call. For example, suppose that you have to add an argument to the read_file() function. You enter this command: :vimgrep /\<read_file\>/ *.c You use ":cn" to go along the list of matches and add the argument. At one place you have to get the new argument from a higher level function msg(), and need to change that one too. Thus you use: :vimgrep /\<msg\>/ *.c While changing the msg() functions, you find another function that needs to get the argument from a higher level. You can again use ":vimgrep" to find these functions. Once you are finished with one function, you can use :colder to go back to the previous one. This works like browsing a tree: ":vimgrep" goes one level deeper, creating a list of branches. ":colder" goes back to the previous level. You can mix this use of ":vimgrep" and "colder" to browse all the locations in a tree-like way. If you do this consistently, you will find all locations without the need to write down a "todo" list. ============================================================================= 6. Selecting a compiler *compiler-select* *:comp* *:compiler* *E666* :comp[iler][!] {name} Set options to work with compiler {name}. Without the "!" options are set for the current buffer. With "!" global options are set. If you use ":compiler foo" in "file.foo" and then ":compiler! bar" in another buffer, Vim will keep on using "foo" in "file.foo". {not available when compiled without the |+eval| feature} The Vim plugins in the "compiler" directory will set options to use the selected compiler. For ":compiler" local options are set, for ":compiler!" global options. *current_compiler* To support older Vim versions, the plugins always use "current_compiler" and not "b:current_compiler". What the command actually does is the following: - Delete the "current_compiler" and "b:current_compiler" variables. - Define the "CompilerSet" user command. With "!" it does ":set", without "!" it does ":setlocal". - Execute ":runtime! compiler/{name}.vim". The plugins are expected to set options with "CompilerSet" and set the "current_compiler" variable to the name of the compiler. - Delete the "CompilerSet" user command. - Set "b:current_compiler" to the value of "current_compiler". - Without "!" the old value of "current_compiler" is restored. For writing a compiler plugin, see |write-compiler-plugin|. GCC *quickfix-gcc* *compiler-gcc* There's one variable you can set for the GCC compiler: g:compiler_gcc_ignore_unmatched_lines Ignore lines that don't match any patterns defined for GCC. Useful if output from commands run from make are generating false positives. MANX AZTEC C *quickfix-manx* *compiler-manx* To use Vim with Manx's Aztec C compiler on the Amiga you should do the following: - Set the CCEDIT environment variable with the command: mset "CCEDIT=vim -q" - Compile with the -qf option. If the compiler finds any errors, Vim is started and the cursor is positioned on the first error. The error message will be displayed on the last line. You can go to other errors with the commands mentioned above. You can fix the errors and write the file(s). - If you exit Vim normally the compiler will re-compile the same file. If you exit with the :cq command, the compiler will terminate. Do this if you cannot fix the error, or if another file needs to be compiled first. There are some restrictions to the Quickfix mode on the Amiga. The compiler only writes the first 25 errors to the errorfile (Manx's documentation does not say how to get more). If you want to find the others, you will have to fix a few errors and exit the editor. After recompiling, up to 25 remaining errors will be found. If Vim was started from the compiler, the :sh and some :! commands will not work, because Vim is then running in the same process as the compiler and stdin (standard input) will not be interactive. PERL *quickfix-perl* *compiler-perl* The Perl compiler plugin doesn't actually compile, but invokes Perl's internal syntax checking feature and parses the output for possible errors so you can correct them in quick-fix mode. Warnings are forced regardless of "no warnings" or "$^W = 0" within the file being checked. To disable this set g:perl_compiler_force_warnings to a zero value. For example: let g:perl_compiler_force_warnings = 0 PYUNIT COMPILER *compiler-pyunit* This is not actually a compiler, but a unit testing framework for the Python language. It is included into standard Python distribution starting from version 2.0. For older versions, you can get it from http://pyunit.sourceforge.net. When you run your tests with the help of the framework, possible errors are parsed by Vim and presented for you in quick-fix mode. Unfortunately, there is no standard way to run the tests. The alltests.py script seems to be used quite often, that's all. Useful values for the 'makeprg' options therefore are: setlocal makeprg=./alltests.py " Run a testsuite setlocal makeprg=python % " Run a single testcase Also see http://vim.sourceforge.net/tip_view.php?tip_id=280. TEX COMPILER *compiler-tex* Included in the distribution compiler for TeX ($VIMRUNTIME/compiler/tex.vim) uses make command if possible. If the compiler finds a file named "Makefile" or "makefile" in the current directory, it supposes that you want to process your *TeX files with make, and the makefile does the right work. In this case compiler sets 'errorformat' for *TeX output and leaves 'makeprg' untouched. If neither "Makefile" nor "makefile" is found, the compiler will not use make. You can force the compiler to ignore makefiles by defining b:tex_ignore_makefile or g:tex_ignore_makefile variable (they are checked for existence only). If the compiler chose not to use make, it need to choose a right program for processing your input. If b:tex_flavor or g:tex_flavor (in this precedence) variable exists, it defines TeX flavor for :make (actually, this is the name of executed command), and if both variables do not exist, it defaults to "latex". For example, while editing chapter2.tex \input-ed from mypaper.tex written in AMS-TeX: :let b:tex_flavor = 'amstex' :compiler tex [editing...] :make mypaper Note that you must specify a name of the file to process as an argument (to process the right file when editing \input-ed or \include-ed file; portable solution for substituting % for no arguments is welcome). This is not in the semantics of make, where you specify a target, not source, but you may specify filename without extension ".tex" and mean this as "make filename.dvi or filename.pdf or filename.some_result_extension according to compiler". Note: tex command line syntax is set to usable both for MikTeX (suggestion by Srinath Avadhanula) and teTeX (checked by Artem Chuprina). Suggestion from |errorformat-LaTeX| is too complex to keep it working for different shells and OSes and also does not allow to use other available TeX options, if any. If your TeX doesn't support "-interaction=nonstopmode", please report it with different means to express \nonstopmode from the command line. ============================================================================= 7. The error format *error-file-format* *errorformat* *E372* *E373* *E374* *E375* *E376* *E377* *E378* The 'errorformat' option specifies a list of formats that are recognized. The first format that matches with an error message is used. You can add several formats for different messages your compiler produces, or even entries for multiple compilers. See |efm-entries|. Each entry in 'errorformat' is a scanf-like string that describes the format. First, you need to know how scanf works. Look in the documentation of your C compiler. Below you find the % items that Vim understands. Others are invalid. Special characters in 'errorformat' are comma and backslash. See |efm-entries| for how to deal with them. Note that a literal "%" is matched by "%%", thus it is not escaped with a backslash. Note: By default the difference between upper and lowercase is ignored. If you want to match case, add "\C" to the pattern |/\C|. Basic items %f file name (finds a string) %l line number (finds a number) %c column number (finds a number representing character column of the error, (1 <tab> == 1 character column)) %v virtual column number (finds a number representing screen column of the error (1 <tab> == 8 screen columns)) %t error type (finds a single character) %n error number (finds a number) %m error message (finds a string) %r matches the "rest" of a single-line file message %O/P/Q %p pointer line (finds a sequence of '-', '.' or '' '' and uses the length for the column number) %*{conv} any scanf non-assignable conversion %% the single '%' character %s search text (finds a string) The "%f" conversion may depend on the current 'isfname' setting. "~/" is expanded to the home directory and environment variables are expanded. The "%f" and "%m" conversions have to detect the end of the string. This normally happens by matching following characters and items. When nothing is following the rest of the line is matched. If "%f" is followed by a '%' or a backslash, it will look for a sequence of 'isfname' characters. On MS-DOS, MS-Windows and OS/2 a leading "C:" will be included in "%f", even when using "%f:". This means that a file name which is a single alphabetical letter will not be detected. The "%p" conversion is normally followed by a "^". It's used for compilers that output a line like: ^ or ---------^ to indicate the column of the error. This is to be used in a multi-line error message. See |errorformat-javac| for a useful example. The "%s" conversion specifies the text to search for to locate the error line. The text is used as a literal string. The anchors "^" and "$" are added to the text to locate the error line exactly matching the search text and the text is prefixed with the "\V" atom to make it "very nomagic". The "%s" conversion can be used to locate lines without a line number in the error output. Like the output of the "grep" shell command. When the pattern is present the line number will not be used. Changing directory The following uppercase conversion characters specify the type of special format strings. At most one of them may be given as a prefix at the begin of a single comma-separated format pattern. Some compilers produce messages that consist of directory names that have to be prepended to each file name read by %f (example: GNU make). The following codes can be used to scan these directory names; they will be stored in an internal directory stack. *E379* %D "enter directory" format string; expects a following %f that finds the directory name %X "leave directory" format string; expects following %f When defining an "enter directory" or "leave directory" format, the "%D" or "%X" has to be given at the start of that substring. Vim tracks the directory changes and prepends the current directory to each erroneous file found with a relative path. See |quickfix-directory-stack| for details, tips and limitations. Multi-line messages *errorformat-multi-line* It is possible to read the output of programs that produce multi-line messages, i.e. error strings that consume more than one line. Possible prefixes are: %E start of a multi-line error message %W start of a multi-line warning message %I start of a multi-line informational message %A start of a multi-line message (unspecified type) %> for next line start with current pattern again |efm-%>| %C continuation of a multi-line message %Z end of a multi-line message These can be used with '+' and '-', see |efm-ignore| below. Using "\n" in the pattern won't work to match multi-line messages. Example: Your compiler happens to write out errors in the following format (leading line numbers not being part of the actual output): 1 Error 275 2 line 42 3 column 3 4 ' ' expected after '--' The appropriate error format string has to look like this: :set efm=%EError\ %n,%Cline\ %l,%Ccolumn\ %c,%Z%m And the |:clist| error message generated for this error is: 1:42 col 3 error 275: '' '' expected after '--' Another example: Think of a Python interpreter that produces the following error message (line numbers are not part of the actual output): 1 ============================================================== 2 FAIL: testGetTypeIdCachesResult (dbfacadeTest.DjsDBFacadeTest) 3 -------------------------------------------------------------- 4 Traceback (most recent call last): 5 File "unittests/dbfacadeTest.py", line 89, in testFoo 6 self.assertEquals(34, dtid) 7 File "/usr/lib/python2.2/unittest.py", line 286, in 8 failUnlessEqual 9 raise self.failureException, \ 10 AssertionError: 34 != 33 11 12 -------------------------------------------------------------- 13 Ran 27 tests in 0.063s Say you want |:clist| write the relevant information of this message only, namely: 5 unittests/dbfacadeTest.py:89: AssertionError: 34 != 33 Then the error format string could be defined as follows: :set efm=%C\ %.%#,%A\ \ File\ \"%f\"\\,\ line\ %l%.%#,%Z%[%^\ ]%\\@=%m Note that the %C string is given before the %A here: since the expression '' %.%#' (which stands for the regular expression '' .*') matches every line starting with a space, followed by any characters to the end of the line, it also hides line 7 which would trigger a separate error message otherwise. Error format strings are always parsed pattern by pattern until the first match occurs. *efm-%>* The %> item can be used to avoid trying patterns that appear earlier in 'errorformat'. This is useful for patterns that match just about anything. For example, if the error looks like this: Error in line 123 of foo.c: unknown variable "i" This can be found with: :set efm=xxx,%E%>Error in line %l of %f:,%Z%m Where "xxx" has a pattern that would also match the second line. Important: There is no memory of what part of the errorformat matched before; every line in the error file gets a complete new run through the error format lines. For example, if one has: setlocal efm=aa,bb,cc,dd,ee Where aa, bb, etc. are error format strings. Each line of the error file will be matched to the pattern aa, then bb, then cc, etc. Just because cc matched the previous error line does _not_ mean that dd will be tried first on the current line, even if cc and dd are multi-line errorformat strings. Separate file name *errorformat-separate-filename* These prefixes are useful if the file name is given once and multiple messages follow that refer to this file name. %O single-line file message: overread the matched part %P single-line file message: push file %f onto the stack %Q single-line file message: pop the last file from stack Example: Given a compiler that produces the following error logfile (without leading line numbers): 1 [a1.tt] 2 (1,17) error: ';' missing 3 (21,2) warning: variable 'z' not defined 4 (67,3) error: end of file found before string ended 5 6 [a2.tt] 7 8 [a3.tt] 9 NEW compiler v1.1 10 (2,2) warning: variable 'x' not defined 11 (67,3) warning: 's' already defined This logfile lists several messages for each file enclosed in [...] which are properly parsed by an error format like this: :set efm=%+P[%f],(%l\\,%c)%*[\ ]%t%*[^:]:\ %m,%-Q A call of |:clist| writes them accordingly with their correct filenames: 2 a1.tt:1 col 17 error: ';' missing 3 a1.tt:21 col 2 warning: variable 'z' not defined 4 a1.tt:67 col 3 error: end of file found before string ended 8 a3.tt:2 col 2 warning: variable 'x' not defined 9 a3.tt:67 col 3 warning: 's' already defined Unlike the other prefixes that all match against whole lines, %P, %Q and %O can be used to match several patterns in the same line. Thus it is possible to parse even nested files like in the following line: {"file1" {"file2" error1} error2 {"file3" error3 {"file4" error4 error5}}} The %O then parses over strings that do not contain any push/pop file name information. See |errorformat-LaTeX| for an extended example. Ignoring and using whole messages *efm-ignore* The codes '+' or '-' can be combined with the uppercase codes above; in that case they have to precede the letter, e.g. '%+A' or '%-G': %- do not include the matching multi-line in any output %+ include the whole matching line in the %m error string One prefix is only useful in combination with '+' or '-', namely %G. It parses over lines containing general information like compiler version strings or other headers that can be skipped. %-G ignore this message %+G general message Pattern matching The scanf()-like "%*[]" notation is supported for backward-compatibility with previous versions of Vim. However, it is also possible to specify (nearly) any Vim supported regular expression in format strings. Since meta characters of the regular expression language can be part of ordinary matching strings or file names (and therefore internally have to be escaped), meta symbols have to be written with leading '%': %\ The single '\' character. Note that this has to be escaped ("%\\") in ":set errorformat=" definitions. %. The single '.' character. %# The single '*'(!) character. %^ The single '^' character. Note that this is not useful, the pattern already matches start of line. %$ The single '$' character. Note that this is not useful, the pattern already matches end of line. %[ The single '[' character for a [] character range. %~ The single '~' character. When using character classes in expressions (see |/\i| for an overview), terms containing the "\+" quantifier can be written in the scanf() "%*" notation. Example: "%\\d%\\+" ("\d\+", "any number") is equivalent to "%*\\d". Important note: The \(...\) grouping of sub-matches can not be used in format specifications because it is reserved for internal conversions. Multiple entries in 'errorformat' *efm-entries* To be able to detect output from several compilers, several format patterns may be put in 'errorformat', separated by commas (note: blanks after the comma are ignored). The first pattern that has a complete match is used. If no match is found, matching parts from the last one will be used, although the file name is removed and the error message is set to the whole message. If there is a pattern that may match output from several compilers (but not in a right way), put it after one that is more restrictive. To include a comma in a pattern precede it with a backslash (you have to type two in a ":set" command). To include a backslash itself give two backslashes (you have to type four in a ":set" command). You also need to put a backslash before a space for ":set". Valid matches *quickfix-valid* If a line does not completely match one of the entries in 'errorformat', the whole line is put in the error message and the entry is marked "not valid" These lines are skipped with the ":cn" and ":cp" commands (unless there is no valid line at all). You can use ":cl!" to display all the error messages. If the error format does not contain a file name Vim cannot switch to the correct file. You will have to do this by hand. Examples The format of the file from the Amiga Aztec compiler is: filename>linenumber:columnnumber:errortype:errornumber:errormessage filename name of the file in which the error was detected linenumber line number where the error was detected columnnumber column number where the error was detected errortype type of the error, normally a single 'E' or 'W' errornumber number of the error (for lookup in the manual) errormessage description of the error This can be matched with this 'errorformat' entry: %f>%l:%c:%t:%n:%m Some examples for C compilers that produce single-line error outputs: %f:%l:\ %t%*[^0123456789]%n:\ %m for Manx/Aztec C error messages (scanf() doesn't understand [0-9]) %f\ %l\ %t%*[^0-9]%n:\ %m for SAS C \"%f\"\\,%*[^0-9]%l:\ %m for generic C compilers %f:%l:\ %m for GCC %f:%l:\ %m,%Dgmake[%*\\d]:\ Entering\ directory\ `%f', %Dgmake[%*\\d]:\ Leaving\ directory\ `%f' for GCC with gmake (concat the lines!) %f(%l)\ :\ %*[^:]:\ %m old SCO C compiler (pre-OS5) %f(%l)\ :\ %t%*[^0-9]%n:\ %m idem, with error type and number %f:%l:\ %m,In\ file\ included\ from\ %f:%l:,\^I\^Ifrom\ %f:%l%m for GCC, with some extras Extended examples for the handling of multi-line messages are given below, see |errorformat-Jikes| and |errorformat-LaTeX|. Note the backslash in front of a space and double quote. It is required for the :set command. There are two backslashes in front of a comma, one for the :set command and one to avoid recognizing the comma as a separator of error formats. Filtering messages If you have a compiler that produces error messages that do not fit in the format string, you could write a program that translates the error messages into this format. You can use this program with the ":make" command by changing the 'makeprg' option. For example: :set mp=make\ \\\|&\ error_filter The backslashes before the pipe character are required to avoid it to be recognized as a command separator. The backslash before each space is required for the set command. ============================================================================= 8. The directory stack *quickfix-directory-stack* Quickfix maintains a stack for saving all used directories parsed from the make output. For GNU-make this is rather simple, as it always prints the absolute path of all directories it enters and leaves. Regardless if this is done via a 'cd' command in the makefile or with the parameter "-C dir" (change to directory before reading the makefile). It may be useful to use the switch "-w" to force GNU-make to print out the working directory before and after processing. Maintaining the correct directory is more complicated if you don't use GNU-make. AIX-make for example doesn't print any information about its working directory. Then you need to enhance the makefile. In the makefile of LessTif there is a command which echoes "Making {target} in {dir}". The special problem here is that it doesn't print informations on leaving the directory and that it doesn't print the absolute path. To solve the problem with relative paths and missing "leave directory" messages Vim uses following algorithm: 1) Check if the given directory is a subdirectory of the current directory. If this is true, store it as the current directory. 2) If it is not a subdir of the current directory, try if this is a subdirectory of one of the upper directories. 3) If the directory still isn't found, it is assumed to be a subdirectory of Vim's current directory. Additionally it is checked for every file, if it really exists in the identified directory. If not, it is searched in all other directories of the directory stack (NOT the directory subtree!). If it is still not found, it is assumed that it is in Vim's current directory. There are limitation in this algorithm. This examples assume that make just prints information about entering a directory in the form "Making all in dir". 1) Assume you have following directories and files: ./dir1 ./dir1/file1.c ./file1.c If make processes the directory "./dir1" before the current directory and there is an error in the file "./file1.c", you will end up with the file "./dir1/file.c" loaded by Vim. This can only be solved with a "leave directory" message. 2) Assume you have following directories and files: ./dir1 ./dir1/dir2 ./dir2 You get the following: Make output Directory interpreted by Vim ------------------------ ---------------------------- Making all in dir1 ./dir1 Making all in dir2 ./dir1/dir2 Making all in dir2 ./dir1/dir2 This can be solved by printing absolute directories in the "enter directory" message or by printing "leave directory" messages.. To avoid this problems, ensure to print absolute directory names and "leave directory" messages. Examples for Makefiles: Unix: libs: for dn in $(LIBDIRS); do \ (cd $$dn; echo "Entering dir '$$(pwd)'"'; make); \ echo "Leaving dir"; \ done Add %DEntering\ dir\ '%f',%XLeaving\ dir to your 'errorformat' to handle the above output. Note that Vim doesn't check if the directory name in a "leave directory" messages is the current directory. This is why you could just use the message "Leaving dir". ============================================================================= 9. Specific error file formats *errorformats* *errorformat-Jikes* Jikes(TM), a source-to-bytecode Java compiler published by IBM Research, produces simple multi-line error messages. An 'errorformat' string matching the produced messages is shown below. The following lines can be placed in the user's |vimrc| to overwrite Vim's recognized default formats, or see |:set+=| how to install this format additionally to the default. :set efm=%A%f:%l:%c:%*\\d:%*\\d:, \%C%*\\s%trror:%m, \%+C%*[^:]%trror:%m, \%C%*\\s%tarning:%m, \%C%m Jikes(TM) produces a single-line error message when invoked with the option "+E", and can be matched with the following: :setl efm=%f:%l:%v:%*\\d:%*\\d:%*\\s%m *errorformat-javac* This 'errorformat' has been reported to work well for javac, which outputs a line with "^" to indicate the column of the error: :setl efm=%A%f:%l:\ %m,%-Z%p^,%-C%.%# or: :setl efm=%A%f:%l:\ %m,%+Z%p^,%+C%.%#,%-G%.%# Here is an alternative from Michael F. Lamb for Unix that filters the errors first: :setl errorformat=%Z%f:%l:\ %m,%A%p^,%-G%*[^sl]%.%# :setl makeprg=javac\ %\ 2>&1\ \\\|\ vim-javac-filter You need to put the following in "vim-javac-filter" somewhere in your path (e.g., in ~/bin) and make it executable: #!/bin/sed -f /\^$/s/\t/\ /g;/:[0-9]\+:/{h;d};/^[ \t]*\^/G; In English, that sed script: - Changes single tabs to single spaces and - Moves the line with the filename, line number, error message to just after the pointer line. That way, the unused error text between doesn't break vim's notion of a "multi-line message" and also doesn't force us to include it as a "continuation of a multi-line message." *errorformat-ant* For ant http://jakarta.apache.org/ the above errorformat has to be modified to honour the leading [javac] in front of each javac output line: :set efm=%A\ %#[javac]\ %f:%l:\ %m,%-Z\ %#[javac]\ %p^,%-C%.%# The 'errorformat' can also be configured to handle ant together with either javac or jikes. If you're using jikes, you should tell ant to use jikes' +E command line switch which forces jikes to generate one-line error messages. This is what the second line (of a build.xml file) below does: <property name = "build.compiler" value = "jikes"/> <property name = "build.compiler.emacs" value = "true"/> The 'errorformat' which handles ant with both javac and jikes is: :set efm=\ %#[javac]\ %#%f:%l:%c:%*\\d:%*\\d:\ %t%[%^:]%#:%m, \%A\ %#[javac]\ %f:%l:\ %m,%-Z\ %#[javac]\ %p^,%-C%.%# *errorformat-jade* parsing jade see http://www.jclark.com/ errors is simple: :set efm=jade:%f:%l:%c:%t:%m *errorformat-LaTeX* The following is an example how an 'errorformat' string can be specified for the (La)TeX typesetting system which displays error messages over multiple lines. The output of ":clist" and ":cc" etc. commands displays multi-lines in a single line, leading white space is removed. It should be easy to adopt the above LaTeX errorformat to any compiler output consisting of multi-line errors. The commands can be placed in a |vimrc| file or some other Vim script file, e.g. a script containing LaTeX related stuff which is loaded only when editing LaTeX sources. Make sure to copy all lines of the example (in the given order), afterwards remove the comment lines. For the '\' notation at the start of some lines see |line-continuation|. First prepare 'makeprg' such that LaTeX will report multiple errors; do not stop when the first error has occurred: :set makeprg=latex\ \\\\nonstopmode\ \\\\input\\{$*} Start of multi-line error messages: :set efm=%E!\ LaTeX\ %trror:\ %m, \%E!\ %m, Start of multi-line warning messages; the first two also include the line number. Meaning of some regular expressions: - "%.%#" (".*") matches a (possibly empty) string - "%*\\d" ("\d\+") matches a number \%+WLaTeX\ %.%#Warning:\ %.%#line\ %l%.%#, \%+W%.%#\ at\ lines\ %l--%*\\d, \%WLaTeX\ %.%#Warning:\ %m, Possible continuations of error/warning messages; the first one also includes the line number: \%Cl.%l\ %m, \%+C\ \ %m., \%+C%.%#-%.%#, \%+C%.%#[]%.%#, \%+C[]%.%#, \%+C%.%#%[{}\\]%.%#, \%+C<%.%#>%.%#, \%C\ \ %m, Lines that match the following patterns do not contain any important information; do not include them in messages: \%-GSee\ the\ LaTeX%m, \%-GType\ \ H\ <return>%m, \%-G\ ...%.%#, \%-G%.%#\ (C)\ %.%#, \%-G(see\ the\ transcript%.%#), Generally exclude any empty or whitespace-only line from being displayed: \%-G\\s%#, The LaTeX output log does not specify the names of erroneous source files per line; rather they are given globally, enclosed in parentheses. The following patterns try to match these names and store them in an internal stack. The patterns possibly scan over the same input line (one after another), the trailing "%r" conversion indicates the "rest" of the line that will be parsed in the next go until the end of line is reached. Overread a file name enclosed in '('...')'; do not push it on a stack since the file apparently does not contain any error: \%+O(%f)%r, Push a file name onto the stack. The name is given after '(': \%+P(%f%r, \%+P\ %\\=(%f%r, \%+P%*[^()](%f%r, \%+P[%\\d%[^()]%#(%f%r, Pop the last stored file name when a ')' is scanned: \%+Q)%r, \%+Q%*[^()])%r, \%+Q[%\\d%*[^()])%r Note that in some cases file names in the LaTeX output log cannot be parsed properly. The parser might have been messed up by unbalanced parentheses then. The above example tries to catch the most relevant cases only. You can customize the given setting to suit your own purposes, for example, all the annoying "Overfull ..." warnings could be excluded from being recognized as an error. Alternatively to filtering the LaTeX compiler output, it is also possible to directly read the *.log file that is produced by the [La]TeX compiler. This contains even more useful information about possible error causes. However, to properly parse such a complex file, an external filter should be used. See the description further above how to make such a filter known by Vim. *errorformat-Perl* In $VIMRUNTIME/tools you can find the efm_perl.pl script, which filters Perl error messages into a format that quickfix mode will understand. See the start of the file about how to use it. (This script is deprecated, see |compiler-perl|.) top - main help file


| Figure 1 |
Locations of the 12 collection sites in West Bengal, India, ... |
| Figure 2 |
Graphical outline of Experiment 1 showing the origin of the ... |
| Figure 3 |
Graphical outline of Experiment 2 showing the origin of the ... |
| Figure 4 |
The effect of laboratory acclimation and short- and long-ter ... |
| Figure 5 |
The relationship between site/acclimation temperature and ( ... |
| Figure 6 |
The relationship between thermal tolerance (CT max) and cond ... |


--- title: "Rounded Progress Bars" description: |
By adding the rounded modifier on an evo_c-progress-bar component, you get a rounded progress bar.
rounded
evo_c-progress-bar


{% load static %}
Website Home
Zoo Home
All Zoos
All Animals
Employee's
Shows
Shops
{{editZoo.zooName}}
Located in: {{editZoo.zooLocation}}
{% csrf_token %}
Zoo Name:
Zoo Location:
Save Edits
Delete Zoo
Add Shops to the zoo:
{% csrf_token %}
Chose the Shop:
{% for shop in shops %}
{{shop.shopName}}
{% endfor %}
Add Shop


My Travels
Spain
- I've been to Spain a couple of times when I was younger.The
first time we stayed in a place called Tarragona,a port city located
in northeast Spain on the Costa Daurada by the Mediterranean Sea.There was a lot of
historical monuments,including Circ Romà Ruins of a Roman chariot track,
Tarragona Amphitheatre,National Archaeological Museum of Tarragona and
Balcó del Mediterrani.The beaches there were also beautiful,along with
the weather.
- I also went to Barcelona.We visited all the shops and of course the famous football stadium
Camp Nou.We watched a match there too between Barcelona and Real Madrid.I got to see my favourite player Ronaldo
play.
France
- I visited France a few times throughout my lifetime.I've an unlce who lives there
so it was handy for somewhere to stay.It's a nice Country and there is lovely pastries to eat.
We visited Paris aswel.We went to see the eiffel tower.I was awestruck by the sightings.We
also walked down the Champs-Elysees,which was beautiful.There were many other things we saw
such as Louvre Museum,Arc de Triomphe,Sacre-Coeur and Montmartre.
Portugal
- I went to Portugal twice in my life.The first time we went and stayed in the Algarve.
It was a beautiful place and the people there were very nice.The weather was also amazing.
We went to the pool or beach everyday.The second time we stayed in the Porto.
Porto is a coastal city in northwest Portugal known for its stately bridges and port wine production.
In the medieval district, narrow cobbled streets houses and cafes.
Sao Francisco Church is known for its amazing interior with gilded carvings.


Previous | Contents | Index | Next
- Description of them, and their format.
- One use is for flipping - see section below.
- Also used by the replication subsystem.
- Also for merging a small "recent changes" database with a large "archive" database.
- Also for building a collection of databases for remote searching


You have successfully registered to AmzFlip pre launching event.
YOU ARE NOW ON THE VIP WAITLIST FOR OUR UPCOMING COURSE
We'll get into touch with you in 24 hours.
Keep your eyes peeled for an email/phone call from us, as we will be opening the course on the 28th of December 2018.
For any other inquiries or help please contact support@amzflip.com


--- layout: post status: publish published: true title: New MC++ FAQ author: display_name: Tomas Restrepo login: tomasr email<EMAIL_ADDRESS>url: http://winterdom.com/ author_login: tomasr author_email<EMAIL_ADDRESS>author_url: http://winterdom.com/ wordpress_id: 761 wordpress_url: http://winterdom.com/2002/06/newmcfaq date: '2002-06-30 16:08:53 +0000' date_gmt: '2002-06-30 16:08:53 +0000' categories: - ".NET" tags: [] comments: [] ---
So, I've finally gone ahead and started a new Managed C++ FAQ site.  OTOH, the benefits are categorization (not done... yet), and auto-generated RSS feeds (as if anyone cared).
Please note I'm just getting started, so there's not much in yet. However, if anyone feels like they want contribute, I'd really appreciate it! Just let me know, and I'll set you up with an MT user so you can post directly to the FAQ!


Creates a named variable and assigns a value to it. If the variable already exists, the old value is overwritten.
0
The above example creates a variable named counter, with an initial value of zero.
$object->getLogEntries()
forceType - one of {hash, arrray}. If the method called doesn't return a reference, use forceType to transform the return value into
a reference of the specified type.


Build Eco Lab with AQUA=1
. In the models directory, an
``application bundle'' is created for each model, for example
ecolab.app
, using the utility script mkmacapp.
If you try to run Eco Lab scripts in the usual way, you will get an
error message:
SetFrontProcess failed,-606Instead, you must invoke Eco Lab in a rather cumbersome way:
ecolab.app/Contents/MacOS/ecolab ecolab.tclTo make it a little easier, the
macrun
script is
provided to do this for you -- try
macrun jellyfish.tcl lakes/OTM


Class: ActiveSupport::Testing::Parallelization::Server
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Instance Chain:
self,
DRb::DRbUndumped
|
|
| Inherits: | Object |
| Defined in: | activesupport/lib/active_support/testing/parallelization/server.rb |
Class Method Summary
- .new ⇒ Server constructor
Instance Attribute Summary
- #active_workers? ⇒ Boolean readonly
Instance Method Summary
Constructor Details
.new ⇒ Server
# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 12
def initialize @queue = Queue.new @active_workers = Concurrent::Map.new @in_flight = Concurrent::Map.new end
Instance Attribute Details
#active_workers? ⇒ Boolean
(readonly)
[ GitHub ]
# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 48
def active_workers? @active_workers.size > 0 end
Instance Method Details
#<<(o)
[ GitHub ]# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 28
def <<(o) o[2] = DRbObject.new(o[2]) if o @queue << o end
#interrupt
[ GitHub ]# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 52
def interrupt @queue.clear end
#pop
[ GitHub ]# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 33
def pop if test = @queue.pop @in_flight[[test[0].to_s, test[1]]] = test test end end
#record(reporter, result)
# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 18
def record(reporter, result) raise DRb::DRbConnError if result.is_a?(DRb::DRbUnknown) @in_flight.delete([result.klass, result.name]) reporter.synchronize do reporter.record(result) end end
#shutdown
[ GitHub ]# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 56
def shutdown # Wait for initial queue to drain while @queue.length != 0 sleep 0.1 end @queue.close # Wait until all workers have finished while active_workers? sleep 0.1 end @in_flight.values.each do |(klass, name, reporter)| result = Minitest::Result.from(klass.new(name)) error = RuntimeError.new("result not reported") error.set_backtrace([""]) result.failures << Minitest::UnexpectedError.new(error) reporter.synchronize do reporter.record(result) end end end
#start_worker(worker_id)
[ GitHub ]# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 40
def start_worker(worker_id) @active_workers[worker_id] = true end
#stop_worker(worker_id)
[ GitHub ]# File 'activesupport/lib/active_support/testing/parallelization/server.rb', line 44
def stop_worker(worker_id) @active_workers.delete(worker_id) end


Access Lift
Alien Containment
Elerium Generator
Fission Generator
Foundry
Genetics Lab
Gollop Chamber
Hyperwave Relay
Laboratory
Officer Training School
Psionic Labs
Repair Bay
Satellite Nexus
Satellite Uplink
Thermo Generator
Workshop
Name
Required to Build:
Summary


El-Rufai for Ajasin colloquium - The Nation Newspaper
By Damisi Ojo, Akure
The Kaduna State governor, Mallam Nasir El-Rufai, will on Thursday November 28 deliver the 2019 Ajasin Foundation Colloquium at the International Event Centre Akure, the Ondo State capital.
The programme in honour of the first executive governor of Ondo State, Chief Adekunle Ajasin, was initiated in 1999.
Addressing reporters at the weekend, the Non- Executive Secretary of the Foundation, who spoke on behalf of the Board of Trustees (BoT), Mrs Jumoke Anifowose, said the current year’s activities which began few weeks ago with the secondary schools debate will end on November 27.
She said: “On November 26, there will be the annual presentation to Ajasin Scholars at Owo High School initiated by Dr. ‘Bode Ogunleye, an old student of Owo High School who is currently based in the United States of America.
“The scholarship programme was instituted as his contribution in support of academic excellence in his alma mater. It involves the award of financial reward for the overall best student in each year, from JS 1 – SS 3.
Anifowose, who is the daughter of the late Afenifere leader, said Governor Oluwarotimi Akeredolu is the chief host to be supported by his colleagues in the South west states.


Mixture Density Network¶
The Mixture Density Network (MDN) [BISHOP1994] combines a conventional neural network (in our implementation specified as \(estimator\)) with a mixture density model for modeling conditional probability distributions \(p(t|x)\). Given a sufficiently flexible network and considering a parametric mixture model, the parameters of the distribution \(t\) can be determined by the outputs of the neural network provided the input to the network is \(x\) (in our implementation specified as X_ph (placeholder) and X). This approach therefore constitutes as a framework capable of approximating arbitrary conditional distributions.
The following example develops a model for Gaussian components with isotropic component covariances, while \(K\) being the number of components of a single mixture (our model currently allows to choose an arbitrary number of (global) mixture components, see parameter L below) and \(\pi(x)\) denoting the mixing coefficients:
It is both feasible to replace the components by components of other distributions and extending the MDN to arbitrary covariance matrices. Although the later is generally much more difficult, it has been shown by [TANSEY2016] that, for example one can have the MDN output the lower triangular entries in the Cholesky decomposition.
Using \(x\) as input, the mixing coefficients \(\pi_{k}(x)\), the means \(\mu_{k}(x)\), and the variances \(\sigma_{k}^2(x)\) can be governed by the outputs of neural network. Assuming the mixture model has L mixture components (in our implementation specified as n_centers), the total number of network outputs is given by \((K+2)L\).
The mixing coefficients are computed as a set of \(L\) softmax outputs, where \(a_k^{\pi}\) determine the mixing coefficients emitted by the network:
ensuring the constraint that \(\pi_k(x)\) over \(K\) must sum to 1. Similarly, the variances must me larger or equal to zero. Due to isotropy we have \(L\) kernel widths \(\sigma_k(x)\) which are determined by the network output \(a_k^{\sigma}\) and can be represented as exponentials:
For the \(K \times L\) means we directly use the network outputs: \(\mu_k(x) = a_{kj}^{\sigma}\).
The weights and biases \(w\) of the neural network are learned by minimizing the negative logarithm of the likelihood (maximum likelihood) over \(N\) data points:
This can be executed via the standard backpropagation algorithm, given that suitable expressions for the derivations can be obtained.
-
class
cde.density_estimator.
MixtureDensityNetwork
(name, ndim_x, ndim_y, n_centers=10, hidden_sizes=(16, 16), hidden_nonlinearity=<function tanh>, n_training_epochs=1000, x_noise_std=None, y_noise_std=None, entropy_reg_coef=0.0, weight_decay=0.0, weight_normalization=True, data_normalization=True, dropout=0.0, random_seed=None)[source]¶ Mixture Density Network Estimator
See “Mixture Density networks”, Bishop 1994
- Parameters
name – (str) name space of MDN (should be unique in code, otherwise tensorflow namespace collitions may arise)
ndim_x – (int) dimensionality of x variable
ndim_y – (int) dimensionality of y variable
n_centers – Number of Gaussian mixture components
hidden_sizes – (tuple of int) sizes of the hidden layers of the neural network
hidden_nonlinearity – (tf function) nonlinearity of the hidden layers
n_training_epochs – Number of epochs for training
x_noise_std – (optional) standard deviation of Gaussian noise over the the training data X -> regularization through noise
y_noise_std – (optional) standard deviation of Gaussian noise over the the training data Y -> regularization through noise
entropy_reg_coef – (optional) scalar float coefficient for shannon entropy penalty on the mixture component weight distribution
weight_decay – (float) the amount of decoupled (http://arxiv.org/abs/1711.05101) weight decay to apply
weight_normalization – (boolean) whether weight normalization shall be used
data_normalization – (boolean) whether to normalize the data (X and Y) to exhibit zero-mean and std
dropout – (float) the probability of switching off nodes during training
random_seed – (optional) seed (int) of the random number generators used
-
cdf
(X, Y)¶ Predicts the conditional cumulative probability p(Y<=y|X=x). Requires the model to be fitted.
- Parameters
X – numpy array to be conditioned on - shape: (n_samples, n_dim_x)
Y – numpy array of y targets - shape: (n_samples, n_dim_y)
- Returns
conditional cumulative probability p(Y<=y|X=x) - numpy array of shape (n_query_samples, )
-
conditional_value_at_risk
(x_cond, alpha=0.01, n_samples=10000000)¶ Computes the Conditional Value-at-Risk (CVaR) / Expected Shortfall of a GMM. Only if ndim_y = 1
Based on formulas from section 2.3.2 in “Expected shortfall for distributions in finance”, Simon A. Broda, Marc S. Paolella, 2011
- Parameters
x_cond – different x values to condition on - numpy array of shape (n_values, ndim_x)
alpha – quantile percentage of the distribution
- Returns
CVaR values for each x to condition on - numpy array of shape (n_values)
-
covariance
(x_cond, n_samples=None)¶ Covariance of the fitted distribution conditioned on x_cond
- Parameters
x_cond – different x values to condition on - numpy array of shape (n_values, ndim_x)
- Returns
Covariances Cov[y|x] corresponding to x_cond - numpy array of shape (n_values, ndim_y, ndim_y)
-
eval_by_cv
(X, Y, n_splits=5, verbose=True)¶ Fits the conditional density model with cross-validation by using the score function of the BaseDensityEstimator for scoring the various splits.
- Parameters
X – numpy array to be conditioned on - shape: (n_samples, n_dim_x)
Y – numpy array of y targets - shape: (n_samples, n_dim_y)
n_splits – number of cross-validation folds (positive integer)
verbose – the verbosity level
-
fit
(X, Y, random_seed=None, verbose=True, eval_set=None, **kwargs)[source]¶ Fits the conditional density model with provided data
- Parameters
X – numpy array to be conditioned on - shape: (n_samples, n_dim_x)
Y – numpy array of y targets - shape: (n_samples, n_dim_y)
eval_set – (tuple) eval/test set - tuple (X_test, Y_test)
verbose – (boolean) controls the verbosity (console output)
-
fit_by_cv
(X, Y, n_folds=3, param_grid=None, random_state=None, verbose=True, n_jobs=-1)¶ Fits the conditional density model with hyperparameter search and cross-validation.
Determines the best hyperparameter configuration from a pre-defined set using cross-validation. Thereby, the conditional log-likelihood is used for simulation_eval.
Fits the model with the previously selected hyperparameter configuration
- Parameters
X – numpy array to be conditioned on - shape: (n_samples, n_dim_x)
Y – numpy array of y targets - shape: (n_samples, n_dim_y)
n_folds – number of cross-validation folds (positive integer)
param_grid –
(optional) a dictionary with the hyperparameters of the model as key and and a list of respective parametrizations as value. The hyperparameter search is performed over the cartesian product of the provided lists. Example:
{"n_centers": [20, 50, 100, 200], "center_sampling_method": ["agglomerative", "k_means", "random"], "keep_edges": [True, False] }
random_state – (int) seed used by the random number generator for shuffeling the data
-
get_configuration
(deep=True)¶ Get parameter configuration for this estimator.
- Parameters
deep – boolean, optional If True, will return the parameters for this estimator and contained subobjects that are estimators.
- Returns
params - mapping of string to any Parameter names mapped to their values.
-
get_params
(deep=True)¶ Get parameters for this estimator.
- Parameters
deep (boolean, optional) – If True, will return the parameters for this estimator and contained subobjects that are estimators.
- Returns
params – Parameter names mapped to their values.
- Return type
mapping of string to any
-
get_params_internal
(**tags)¶ Internal method to be implemented which does not perform caching
-
kurtosis
(x_cond, n_samples=1000000)¶ Kurtosis of the fitted distribution conditioned on x_cond
- Parameters
x_cond – different x values to condition on - numpy array of shape (n_values, ndim_x)
- Returns
Kurtosis Kurt[y|x] corresponding to x_cond - numpy array of shape (n_values, ndim_y, ndim_y)
-
log_pdf
(X, Y)¶ Predicts the conditional log-probability log p(y|x). Requires the model to be fitted.
- Parameters
X – numpy array to be conditioned on - shape: (n_samples, n_dim_x)
Y – numpy array of y targets - shape: (n_samples, n_dim_y)
- Returns
onditional log-probability log p(y|x) - numpy array of shape (n_query_samples, )
-
mean_
(x_cond, n_samples=None)¶ Mean of the fitted distribution conditioned on x_cond :param x_cond: different x values to condition on - numpy array of shape (n_values, ndim_x)
- Returns
Means E[y|x] corresponding to x_cond - numpy array of shape (n_values, ndim_y)
-
mean_std
(x_cond, n_samples=None)¶ - Computes Mean and Covariance of the fitted distribution conditioned on x_cond.
Computationally more efficient than calling mean and covariance computatio separately
- Parameters
x_cond – different x values to condition on - numpy array of shape (n_values, ndim_x)
- Returns
Means E[y|x] and Covariances Cov[y|x]
-
pdf
(X, Y)¶ Predicts the conditional probability p(y|x). Requires the model to be fitted.
- Parameters
X – numpy array to be conditioned on - shape: (n_samples, n_dim_x)
Y – numpy array of y targets - shape: (n_samples, n_dim_y)
- Returns
conditional probability p(y|x) - numpy array of shape (n_query_samples, )
-
plot2d
(x_cond=[0, 1, 2], ylim=(-8, 8), resolution=100, mode='pdf', show=True, prefix='', numpyfig=False)¶ Generates a 3d surface plot of the fitted conditional distribution if x and y are 1-dimensional each
- Parameters
xlim – 2-tuple specifying the x axis limits
ylim – 2-tuple specifying the y axis limits
resolution – integer specifying the resolution of plot
-
plot3d
(xlim=(-5, 5), ylim=(-8, 8), resolution=100, show=False, numpyfig=False)¶ Generates a 3d surface plot of the fitted conditional distribution if x and y are 1-dimensional each
- Parameters
xlim – 2-tuple specifying the x axis limits
ylim – 2-tuple specifying the y axis limits
resolution – integer specifying the resolution of plot
-
predict_density
(X, Y=None, resolution=100)¶ Computes conditional density p(y|x) over a predefined grid of y target values
- Parameters
X – values/vectors to be conditioned on - shape: (n_instances, n_dim_x)
Y – (optional) y values to be evaluated from p(y|x) - if not set, Y will be a grid with with specified resolution
resolution –
integer specifying the resolution of simulation_eval grid
- Returns: tuple (P, Y)
P - density p(y|x) - shape (n_instances, resolution**n_dim_y)
Y - grid with with specified resolution - shape (resolution**n_dim_y, n_dim_y) or a copy of Y in case it was provided as argument
-
reset_fit
()¶ resets all tensorflow objects and :return:
-
sample
(X)¶ sample from the conditional mixture distributions - requires the model to be fitted
- Parameters
X – values to be conditioned on when sampling - numpy array of shape (n_instances, n_dim_x)
- Returns: tuple (X, Y)
X - the values to conditioned on that were provided as argument - numpy array of shape (n_samples, ndim_x)
Y - conditional samples from the model p(y|x) - numpy array of shape (n_samples, ndim_y)
-
score
(X, Y)¶ Computes the mean conditional log-likelihood of the provided data (X, Y)
- Parameters
X – numpy array to be conditioned on - shape: (n_query_samples, n_dim_x)
Y – numpy array of y targets - shape: (n_query_samples, n_dim_y)
- Returns
average log likelihood of data
-
set_params
(**params)¶ Set the parameters of this estimator.
The method works on simple estimators as well as on nested objects (such as pipelines). The latter have parameters of the form
<component>__<parameter>
so that it’s possible to update each component of a nested object.- Returns
- Return type
self
-
skewness
(x_cond, n_samples=1000000)¶ Skewness of the fitted distribution conditioned on x_cond
- Parameters
x_cond – different x values to condition on - numpy array of shape (n_values, ndim_x)
- Returns
Skewness Skew[y|x] corresponding to x_cond - numpy array of shape (n_values, ndim_y, ndim_y)
-
std_
(x_cond, n_samples=1000000)¶ Standard deviation of the fitted distribution conditioned on x_cond
- Parameters
x_cond – different x values to condition on - numpy array of shape (n_values, ndim_x)
- Returns
Standard deviations sqrt(Var[y|x]) corresponding to x_cond - numpy array of shape (n_values, ndim_y)
-
tail_risk_measures
(x_cond, alpha=0.01, n_samples=10000000)¶ Computes the Value-at-Risk (VaR) and Conditional Value-at-Risk (CVaR)
- Parameters
x_cond – different x values to condition on - numpy array of shape (n_values, ndim_x)
alpha – quantile percentage of the distribution
n_samples – number of samples for monte carlo model_fitting
- Returns
VaR values for each x to condition on - numpy array of shape (n_values)
CVaR values for each x to condition on - numpy array of shape (n_values)
-
value_at_risk
(x_cond, alpha=0.01, n_samples=1000000)¶ Computes the Value-at-Risk (VaR) of the fitted distribution. Only if ndim_y = 1
- Parameters
x_cond – different x values to condition on - numpy array of shape (n_values, ndim_x)
alpha – quantile percentage of the distribution
- Returns
VaR values for each x to condition on - numpy array of shape (n_values)
- BISHOP1994
Bishop (1994). Mixture Density Networks, Technical Report, Aston University (http://publications.aston.ac.uk/373/)
- TANSEY2016
Tansey et al. (2016). Better Conditional Density Estimation for Neural Networks (https://arxiv.org/abs/1606.02321)


Top notch experience
Medicenter is a responsive template perfect for all screen sizes
Emergency Case
If you need a doctor ungently outside of medicenter opening house, call emergency appointment mi,ber for emergency.
Read moreDoctor Timetable
Hero at medicenter we have individual doctor'f1 oasl. Click read some below to see services and occurrent timesable for our doctors.
Read moreOpening Hours
Monday-Friday
8:00-17:00
Saturday
9:30-17:30
Sunday
9:30-15:00


JavaScript Form Validation
Full Name:
Username(6-8 characters):
Email:
State:
Please Choose
America
Australia
Sweden
Africa
Address:
Zip Code:


RESTful API to be used for the IxD@UQ Project Repository website. System was designed and developed for a client, introducing professional processes such as client communication, expectation management and formal meetings.
External teams were creating dependent systems parallel to our API, introducing realistic and unique challenges, such as communicating back-end processed in a simplistic but meaningful way.
I was personally responsible for developing the Node.js API back-end. This was my first exposure to Node, having to independently learn its structure by using the official documentation.
When designing and developing the API, database coverage, efficient route structure and data security were heavily and constantly considered. The system employs a public facing Nginx server to reverse proxy the Node API server.
One of the most difficult challenges I faced was the implementation of the API key system. The system has four distinct user groups, with each request needing to be checked and determine if they met the minimum privilege level. This has exposed me to security best-practises, such as safe storage of private keys, and developed my interest in cryptography.


read_ndjson.Rd
Read data from a file in newline-delimited JavaScript Object Notation (NDJSON) format.
read_ndjson(file, mmap = FALSE, simplify = TRUE, text = NULL)
| file | the name of the file which the data are to be read from,
or a connection (unless |
|---|---|
| mmap | whether to memory-map the file instead of reading all of its data into memory simultaneously. See the ‘Memory mapping’ section. |
| simplify | whether to attempt to simplify the type of the return
value. For example, if each line of the file stores an integer,
if |
| text | a character vector of string fields to interpret as
|
This function is the recommended means of reading data for processing by the corpus package.
When the text
argument is non-NULL
string data
fields with names indicated by this argument are decoded as
text
values, not as character
values.
When you specify mmap = TRUE
, the function memory-maps the file
instead of reading it into memory directly. In this case, the file
argument must be a character string giving the path to the file, not
a connection object. When you memory-map the file, the operating
system reads data into memory only when it is needed, enabling
you to transparently process large data sets that do not fit into
memory.
In terms of memory usage, enabling mmap = TRUE
reduces the
footprint for corpus_json
and corpus_text
objects;
native R objects (character
, integer
, list
,
logical
, and numeric
) get fully deserialized to
memory and produce identical results regardless of whether
mmap
is TRUE
or FALSE
. To process a large
text corpus with a text field named "text"
, you should set
text = "text"
and mmap = TRUE
. Or, to reduce the memory
footprint even further, set simplify = FALSE
and
mmap = TRUE
.
One danger in memory-mapping is that if you delete the file
after calling read_ndjson
but before processing the data, then
the results will be undefined, and your computer may crash. (On
POSIX-compliant systems like Mac OS and Linux, there should be no
ill effects to deleting the file. On recent versions of Windows,
the system will not allow you to delete the file as long as the data
is active.)
Another danger in memory-mapping is that if you serialize a
corpus_json
object or derived corpus_text
object using
saveRDS
or another similar function, and then you
deserialize the object, R will attempt create a new memory-map
using the file
argument passed to the original read_ndjson
call. If file
is a relative path, then your working directory
at the time of deserialization must agree with your working directory
at the time of the read_ndjson
call. You can avoid this
situation by specifying an absolute path as the file
argument
(the normalizePath
function will convert a relative
to an absolute path).
In the default usage, with argument simplify = TRUE
, when
the lines of the file are records (JSON object literals), the
return value from read_ndjson
is a data frame with class
c("corpus_frame", "data.frame")
. With simplify = FALSE
,
the result is a corpus_json
object.
as_corpus_text
, as_utf8
.
# Memory mapping lines <- c('{ "a": 1, "b": true }', '{ "b": false, "nested": { "c": 100, "d": false }}', '{ "a": 3.14, "nested": { "d": true }}') file <- tempfile() writeLines(lines, file) (data <- read_ndjson(file, mmap = TRUE))#> a b nested.c nested.d #> 1 1.00 TRUE NA NA #> 2 NA FALSE 100 FALSE #> 3 3.14 NA NA TRUEdata$a#> [1] 1.00 NA 3.14data$b#> [1] TRUE FALSE NAdata$nested.c#> [1] NA 100 NAdata$nested.d#> [1] NA FALSE TRUErm("data") invisible(gc()) # force the garbage collector to release the memory-map file.remove(file)#> [1] TRUE


The Sticker Store
Find things you'll love. Support independent sellers.
Daydream Sticker
$3.99
Hurt Sticker
$3.99
Angry Sticker
$3.99
Happy Sticker
$3.99
Confused Sticker
$3.99
Sleepy Sticker
$3.99
Surprised Sticker
$3.99
Nervous Sticker
$3.99
Sad Sticker
$3.99
Love Sticker
$3.99


This visualization shows the results of running NLTK's sentiment analyzer on every line of dialog in The Office for the six characters shown.
Each line plotted shows the sentiment--positive or negative--for the dialog, and the lines are plotted in sequence for all of each character's dialog over each season of the show.
The visualization was created using D3.js. You can move your mouse over the lines to see the dialog spoken, as well as some other data from the analysis.


{#
#}
{# #}
{#
#}
Successfully logged out.
{% extends "base_main.html" %} {% load static %} {% block html_class %}class="fullscreen-bg"{% endblock html_class %} {% block main_content %}
Successfully logged out.
Diminishing Inventory Shrinkage


The video was great. I had a ton of ideas flowing through my head. I love the re-evaluation of education that is happening at DBC and elsewhere. I am thrilled about the focus on accountability and internal motivation. So much so that I wrote a ton on the subject.
Then I deleted it.
On accident of course. I was working late, failed to commit changes to git, and then renamed a file and wrote over all my work. Sublime figured I knew what I was doing. Oops.
I wrote it for me.
My reflections are my own and I don't plan to rewrite them. I explored my feelings and motivations; the point of the exercise. One of the things I have learned is that I am here to learn, not earn a grade. I can spend another 45 minutes rewritting my feelings or I can move on to learn something else. When I put those two on a scale, the answer seems obvious.


The protection of privacy, a challenge these days:
What are we doing today to preserve our privacy in this new digital world? We read social networks such as Facebook
or Google+ more without moderation.
And we are posting our moods and other stuff without worrying about what will happen to our data, in the near future
but also in the more distant future!
Also, it appears that our practices on social networks pose security challenges of tomorrow:
I invite you to watch this video or a security expert (Mikko Hyppönen at USI – OCTO Technology), explains these issues. Take a few minutes to look at is quite edifying!
There was a time where all electronic devices did not exist! How we were doing then? We went to the cafe, or in a public place to meet people, our friends, our acquaintances.
Today the situation has completely changed! With the proliferation of electronic applications on media such as telephone or tablets but also personal computers, without extent, we are posting our moods if we had a good night, or if we butt itch!
Everything is an artifact to post, and we are so happy to share such important things in the whole world! But in the pre digital age, would we have done that? I think not! Today when we post publicly on Facebook, we ask if we would be willing to go to the village square, and with a megaphone, say we had a bad night for example.
Some facts:
The first thing appears: the Internet of the majors are now building an IT model, whose ultimate goal is to collect our data. To shape our person, and thus sell tailored advertising. You think I'm paranoid? So let's look at this a little closer:
Google built "data center" on the planet.
Facebook buys WhatsApp for $ 22 million, with the ultimate goal to correlate your Facebook profile with a phone
number. Facebook has not purchased the application, they bought the data, that is to say, our phone number.
Twitter, Facebook Google still without the triumvirate of these practices, but they are not alone!
The statements are the first to hack our private data, all in order to protect us of course.
I think businesses are there to make money it is their goal. They can not survive without money, and thus repay us our wages. So when she can do so without pain for us, they do! All because of the “I Agree syndrome”.
Who takes the time to read the Terms and Conditions applications? Nobody actually somehow you have already paid for the software, and especially for those that are free. You no longer have a choice!
I think there is no fate, and that alternatives may exist and even I would have to exist. So I invite you to join forces with mine for and b ready for change!
With IT professional for over 15 years, other models may exist. Take for example peer-to-peer model: a long time ago used to share music film also often hacked!
Why not put it to good use model for our data exchanges on social networks? After all our private data do not necessarily have to pass on third-party servers. scattered in the cloud, and we don't know where they are !Google Facebook and other know where our data, we involuntary these clients profiling practices.


Basic example with SELECT element and hovering caption
Basic SELECT (
before
|
after
)
Very poor
Not that bad
Average
Good
Perfect


A sweet, edible fruit produced by an apple tree (Malus pumila).
A fruit of the citrus species Citrus × sinensis in the family Rutaceae.
A fruit – botanically a berry – produced by several kinds of large herbaceous flowering plants in the genus Musa.


Home
About
Contact
FREE SHIPPING ON ALL DOMESTIC ORDERS!
Mug
$18.00
- 4.2 oz
- Traditional Ceramic Mugs in Seventeen Spectacular Colors
- Smooth Molded Ceramic Composite
- Glossy Color Exterior with Matching Color Interior
- Easy Comfort Grip C-curved Handle


WriteStringFormat()
语法
Result = WriteStringFormat(#File, Format)概要
Writes a BOM (Byte Order Mark) at the current position in the file.
参数
#File The file to write to. Format The format for which the mark should be written. 它可以是下列值之一︰ #PB_Ascii : Writes no BOM at all (this is usually interpreted as an plain Ascii file.) #PB_UTF8 : UTF-8 BOM #PB_Unicode: UTF-16 (little endian) BOM #PB_UTF16BE: UTF-16 (big endian) BOM #PB_UTF32 : UTF-32 (little endian) BOM #PB_UTF32BE: UTF-32 (big endian) BOMThe #PB_Ascii, #PB_UTF8 and #PB_Unicode correspond to the flags supported by WriteString() and WriteStringN(). After placing such a BOM, the strings which follow should all be written with this flag. The other formats represent string formats that can not be written directly with the PureBasic string functions. They are included only for completeness.
返回值
Returns nonzero if the operation was successful and zero if it failed.
备注
Because of file buffering, this function may return successful even if there is not enough space left on the output device for the write operation. The file must be opened using a write-capable function (i.e. not with ReadFile()).
The Byte Order Mark is a commonly used method with which to indicate the encoding of a textfile. It is usually placed at the beginning of the file. It is however not a standard, just a commonly used practice. So if no BOM is detected at the start of a file, it does not necessarily mean that it is a plain text file. It could also just mean that the program that created the file did not use this practice. ReadStringFormat() may be used detect a BOM within a file.
For more information, see this Wikipedia Article.
More information about using unicode in PureBasic program can also be found here.
参阅
ReadStringFormat(), WriteString(), WriteStringN(), CreateFile(), OpenFile()
已支持操作系统
所有


--- layout: post title: "The Business of Ed-Tech: February 2018 Funding Data" date: 2018-02-28 13:30:00 +0000 tags: image: https://s3.amazonaws.com/hackedu/2017-03-01-money.jpg imagecredits: https://www.flickr.com/photos/chrisdlugosz/3403776466 ---
Here is the latest data on “the business of education” for February 2018:
It’s too early to say much about “what’s trending” in education, but I will note that tutoring companies have raised over $170 million so far this year – roughly a third of all the venture capital raised so far this year.
The companies that have raised the most money in 2018 (not including the venture capital firms that have raised new funds):
As part of this project, you can review information from the last few years who’s received funding, who’s been acquired, who’s IPO’d, which startups have closed, and who’s investing in the stories that Edsurge tells you about the shape of the education technology industry.
I have created separate GitHub repositories for all areas of funding that I monitor:
These sites include human- and machine-readable versions of this funding data. For more ed-tech data sets, visit Hack Education Data on GitHub.
If you see an error or omission, please file a GitHub issue. You’re welcome to fork or download the repositories too, of course.


Installation and Requirements¶
Hint
You can easy_install or pip_install pyspeckit:
pip install pyspeckit
easy_install pyspeckit
PySpecKit requires at least the basic scientific packages:
- numpy
- matplotlib
- mpfit is included
- scipy is optional. It is only required for RADEX grid interpolation and certain types of optimization
- python2.7 or ordereddict for model parameter storage
You’ll most likely want at least one of the following packages to enable file reading
- astrop >=0.1
- pyfits >=2.4
- atpy (which depends on asciitable [github link] )
- hdf5
If you have pip (see http://pypi.python.org/pypi/pyspeckit), you can install with:
pip install pyspeckit
Or the most recent version:
pip install https://bitbucket.org/pyspeckit/pyspeckit.bitbucket.org/get/tip.tar.gz
You can acquire the code with this clone command:
hg clone https://bitbucket.org/pyspeckit/pyspeckit.bitbucket.org pyspeckit
cd pyspeckit
python setup.py install
or if you use git:
git clone git://github.com/keflavich/pyspeckit.git pyspeckit
cd pyspeckit
python setup.py install
Or you can Download the latest tarball version, then extract and install using the standard python method:
wget https://bitbucket.org/pyspeckit/pyspeckit.bitbucket.org/get/tip.tar.gz
tar -xzf pyspeckit-pyspeckit.bitbucket.org-tip.tar.gz
cd pyspeckit-pyspeckit.bitbucket.org-tip
python setup.py install
You can also check out the source code
Note
If you use easy_install pyspeckit with the Enthought Python Distribution, you will most likely get a SandboxViolation error. You can get around this by using python setup.py install or pip install pyspeckit.


{% block extraHead %}{% endblock%}
music
now playing
library
music
settings
controls
play/pause
next
{% block content %}{% endblock %}
music server by
edmund fung


Page number is object that showing current page number in format you defined. There is only one rule for page number use this symbol "{P}" without quotes. For example: if FormatValue is something like this: "Page -{P}-" then in generated PDF file the actual text is: "Page -1-" for the first page.
To create Page number, select it from object toolbar like shown in picture below, and place it inside desired container (Static or Dynamic balloon)
To set specific properties for the Page number item, select it on the page like shown in picture below.
Specific properties of the Page number are:
ForeColor, is color used to draw text.
Font, is font used to draw text.
FormatValue, is formatting use to place actual page number in you custom formatted text. (Symbol "{P}" is replaces with current page number)


This is a tasty salmon dish filled with lots of Asian flavours. The salmon remains lovely and moist as you finish off the cooking in the oven. You can alter the heat of the dish by adding more chilli or if you prefer, you can omit the chilli altogether if you are not a fan.
Ingredients
800gm salmon, evenly sliced into fillets (approx. 4-5 pieces)
2 tbsp soy sauce
1 1/2 tbsp honey
1 fresh chilli, finely chopped
1 tbsp vinegar
1 clove garlic, finely chopped
1 cm knob ginger, finely grated
1/2 tsp fish sauce
1tsp sesame seeds
1/4 tsp sesame oil
2 tbsp oil for cooking
Instructions
Mix all ingredients except salmon, sesame seeds and cooking oil, in a jug and let stand. If possible make ahead of time, as this will allow the flavours to better infuse.
Meanwhile, heat heavy based oven proof pan over medium-high heat. Pour in oil and coat the base of the pan evenly. Add in salmon and sear for 1 minute each side. Pour over sauce and sprinkle the salmon fillets with sesame seeds.
Place pan in pre-heated oven @ 200℃ for 7 minutes. If you prefer your salmon pink in the middle cook for approximate 4-5 minutes.
Once cooked, serve over steamed rice or steamed vegetables. Spoon over some of the sauce from the pan.


What We Do
We help customers around the world become competitive – and stay competitive.
We combine best-in-class software engineering with digital strategy and experience design, business consulting and technology innovation services.
Our Work
We've helped over 120 Fortune 1000 companies in the following industries solve their most complex technology challenges.
Now see what we can do for you.
-
Heading
Volunteering UX Expertise to Increase Online Donations by 650% for the Hungarian Red Cross
-
Heading
Social Storefront Extension for SAP Hybris
-
Heading
Solving Complex Omnichannel Commerce Challenges in Grocery with SAP Hybris
-
Heading
EPAM SharePoint Connector: Building Spotfire Functionality into SharePoint to Enable Real-Time Project Status Updates
-
Heading
Implement IoT Tech to Innovate & Transform Your Business
-
Heading
Replatforming NewEraCap.com with SAP Hybris to Drive D2C Sales in Just Five Months


Chemical spill shuts down Spanish Town water treatment plant -- NWC
The National Water Commission (NWC) says an “apparent chemical spill” in the Rio Cobre river valley has forced the shutdown of the Spanish Town Treatment Plant in St Catherine.
The plant supplies approximately three million gallons of water a day to the Spanish Town area.
The NWC says in order to ease the shortfall in the affected communities, the service areas for the Chung’s Well and Angel’s facilities will be extended to provide relief water supply to residents.
"The temporary measures now being implemented may not realise near normal water pressure, but should provide some relief against the significant shortfall caused by the loss of production,” the utility company said in a statement.
In the meantime, the NWC says it continues to closely monitor the situation that has impacted the raw water source to the Spanish Town Treatment Plant, and will restart operations once it is verified as safe to do so.
The affected areas include Spanish Town, Hampton Green, Lakemore Gardens, McCoy's Land, Mayfair Mews, Brunswick Avenue, Job's Lane, White Water Meadows, Hartlands, McCooks Pen, Leiba Gardens, Sydenham Gardens, Wedge Wood Gardens, Willowdene Housing Scheme and Hopedale Housing Scheme.
The NWC says every effort is being made to restore full water supply at the earliest possible time.