vim-latex-cvs Mailing List for Vim-Latex (Page 19)
Brought to you by:
srinathava,
tmaas
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(82) |
Dec
(124) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(104) |
Feb
(3) |
Mar
(6) |
Apr
(48) |
May
(34) |
Jun
(62) |
Jul
(33) |
Aug
(24) |
Sep
(32) |
Oct
(16) |
Nov
(36) |
Dec
(39) |
2004 |
Jan
|
Feb
(3) |
Mar
(8) |
Apr
|
May
(29) |
Jun
(13) |
Jul
(4) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
(6) |
Dec
(9) |
2006 |
Jan
(9) |
Feb
(2) |
Mar
(16) |
Apr
(5) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(22) |
Jun
(1) |
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
(17) |
Sep
(3) |
Oct
(4) |
Nov
(1) |
Dec
(3) |
2010 |
Jan
(25) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(8) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(10) |
Oct
(1) |
Nov
|
Dec
(1) |
2012 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
|
2013 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(15) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
From: <sri...@us...> - 2003-07-02 09:49:19
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/tex In directory sc8-pr-cvs1:/tmp/cvs-serv29309 Added Files: Tag: latex-multi-compile latexm.vim Log Message: - multiple calls to the latex compiler to get the cross-references right, run bibtex as necessary etc. NOTE: This commit is on a branch. I will confer with the group before making any main trunk commits. --- NEW FILE: latexm.vim --- python <<EOF import vim import re def isPresentInFile(regexp, filename): fp = open(filename) try: fcontents = ''.join(fp.readlines()) if re.search(regexp, fcontents): return 1 else: return None except: return None def compileLatex(): mainFileName_full = vim.eval("Tex_GetMainFileName(':p:r')") mainFileName_root = vim.eval("Tex_GetMainFileName(':p:r:r')") if not mainFileName_root: mainFileName_full = vim.eval('expand("%:p")') mainFileName_root = vim.eval('expand("%:p:r")') # first run latex once. vim.command('silent! call RunLaTeX()') auxFileName = mainFileName_root + '.aux' # now check if there are any .bib files used. auxFile = open(auxFileName, 'r') auxData = ''.join(auxFile.readlines()) auxFile.close() if isPresentInFile(r'\\bibdata', mainFileName_root + '.aux'): bibFileName = mainFileName_root + '.bbl' try: bibFile = open(bibFileName) biblinesBefore = ''.join(bibFile.readlines()) bibFile.close() except: biblinesBefore = '' try: vim.command('echomsg "running bibtex..."') vim.command('silent! !bibtex %s' % mainFileName_root) bibFile = open(bibFileName) biblinesAfter = ''.join(bibFile.readlines()) bibFile.close() # if the .bbl file changed with this bibtex command, then we need # to rerun latex to refresh the bibliography if biblinesAfter != biblinesBefore: vim.command("echomsg 'running latex a second time because bibliography file changed...'") vim.command('silent! call RunLaTeX()') except: vim.command('echomsg "unable to read %s, quitting to next stage..."' % bibFileName) # check if latex asks us to rerun if isPresentInFile('Rerun to get cross-references right', mainFileName_root + '.log'): vim.command('echomsg "running latex a third time to get cross-references right..."') vim.command('silent! call RunLaTeX()') EOF " vim:fdm=marker:nowrap:noet:ff=unix:ts=4:sw=4 |
From: Srinath A. <sr...@ee...> - 2003-07-01 00:27:15
|
On Tue, 1 Jul 2003, Mikolaj Machowski wrote: > > Modified Files: > > remoteOpen.vim > > Log Message: > > Change: Previously, if a file was not opened in any other session, then it > > would open it in a new session. But for projects with lots of > > files, this can become painful. Therefore, instead of opening in > > new sessions each time, open files in the same session we used the > > first time we had to create a session. > > Why in plugin directory? It means it will be sourced everytime Vim run, > not only with LaTeX files. > Because if you double-click on a dvi file when gvim is not already open, it will not work with this file being an ftplugin... basically a command like gvim -c ":RemoteOpen something" something will succeed only if :RemoteOpen is available as soon as vim starts up. Srinath |
From: Mikolaj M. <mi...@wp...> - 2003-06-30 23:09:29
|
On Fri, Jun 13, 2003 at 09:43:09PM -0700, sri...@us... wrote: > Update of /cvsroot/vim-latex/vimfiles/plugin > In directory sc8-pr-cvs1:/tmp/cvs-serv13376 > Modified Files: > remoteOpen.vim > Log Message: > Change: Previously, if a file was not opened in any other session, then it > would open it in a new session. But for projects with lots of > files, this can become painful. Therefore, instead of opening in > new sessions each time, open files in the same session we used the > first time we had to create a session. Why in plugin directory? It means it will be sourced everytime Vim run, not only with LaTeX files. m. |
From: Mikolaj M. <mi...@wp...> - 2003-06-30 23:07:41
|
On Mon, Jun 16, 2003 at 07:07:49PM -0700, sri...@us... wrote: > Update of /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite > In directory sc8-pr-cvs1:/tmp/cvs-serv9769 > Modified Files: > packages.vim > Log Message: > Change: Instead of using very complicated logic to find out the locations > of package files, just use vim's native :find command. This easily > avoids problems of not being able to search more than 1 level deep > etc. Ofcourse, this means that the users have to specify > g:Tex_TEXINPUTS in the format given in :help file-searching, but > that seems a very acceptable thing to do. > Why was globpath() and all that used previously? I didn't know well :find command and assumed (wrongly) it depends on some external program like :grep. After problems with texviewer I was trying to avoid external tools. m. |
From: <sri...@us...> - 2003-06-30 01:33:38
|
Update of /cvsroot/vim-latex/vimfiles/indent In directory sc8-pr-cvs1:/tmp/cvs-serv1603 Modified Files: tex.vim Log Message: do not change indentation of commented lines Index: tex.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/indent/tex.vim,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** tex.vim 30 Apr 2002 00:03:25 -0000 1.1.1.1 --- tex.vim 30 Jun 2003 01:33:34 -0000 1.2 *************** *** 80,83 **** --- 80,87 ---- let cline = getline(v:lnum) " current line + " Do not change indentation of commented lines. + if line =~ '^\s*%' + return ind + endif " Add a 'shiftwidth' after beginning of environments. |
From: <sri...@us...> - 2003-06-30 01:28:43
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite In directory sc8-pr-cvs1:/tmp/cvs-serv916 Modified Files: texrc Log Message: default g:Tex_RememberCiteSearch to zero. This means that the \cite list is renewed every time as documented in the manual. Index: texrc =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/texrc,v retrieving revision 1.29 retrieving revision 1.30 diff -C2 -d -r1.29 -r1.30 *** texrc 18 Jun 2003 01:03:42 -0000 1.29 --- texrc 30 Jun 2003 01:28:39 -0000 1.30 *************** *** 437,441 **** " whether or not searches for \cite's are cached. ! TexLet g:Tex_RememberCiteSearch = 1 " Paths to the bibliography files and custom packages. TexLet g:Tex_BIBINPUTS = '' --- 437,441 ---- " whether or not searches for \cite's are cached. ! TexLet g:Tex_RememberCiteSearch = 0 " Paths to the bibliography files and custom packages. TexLet g:Tex_BIBINPUTS = '' |
From: <sri...@us...> - 2003-06-30 01:27:22
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/tex In directory sc8-pr-cvs1:/tmp/cvs-serv459 Modified Files: texviewer.vim Log Message: Corrected an obvious syntax error. I dont know what was being attempted here though. Mikolaj: Please document this file better! It would be really nice if you could send out an email to the vim-latex-devel list outlining the feature you are going to implement and how you plant to do it before actually doing it. This way we all have a say in whats going on... Also better documentation is a must! There is no mention anywhere what this "plugintype" thing is supposed to be. Index: texviewer.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/tex/texviewer.vim,v retrieving revision 1.29 retrieving revision 1.30 diff -C2 -d -r1.29 -r1.30 *** texviewer.vim 29 Jun 2003 08:31:04 -0000 1.29 --- texviewer.vim 30 Jun 2003 01:27:19 -0000 1.30 *************** *** 145,149 **** call <SID>Tex_explore_window("input") ! elseif exists("g:Tex_completion_{s:type}") call <SID>CompleteName('plugin_'.s:type) --- 145,149 ---- call <SID>Tex_explore_window("input") ! elseif exists("g:Tex_completion_".s:type) call <SID>CompleteName('plugin_'.s:type) |
From: <sri...@us...> - 2003-06-30 01:21:40
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv32590 Modified Files: Makefile.in Log Message: include targets for quickstart guide. Also use the --prefix argument for the latest db2vim to avoid conflics between tags in various help files. Index: Makefile.in =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/Makefile.in,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** Makefile.in 18 Jun 2003 05:12:38 -0000 1.1 --- Makefile.in 30 Jun 2003 01:21:38 -0000 1.2 *************** *** 1,2 **** --- 1,3 ---- + # Manual files ls-flat: java com.icl.saxon.StyleSheet latex-suite.xml latex-suite.xsl > latex-suite.html *************** *** 9,13 **** ls-txt: ! db2vim latex-suite.xml > latex-suite.txt # vim:nowrap --- 10,27 ---- ls-txt: ! db2vim --prefix=ls_ latex-suite.xml > latex-suite.txt ! ! # Quickstart files ! lsq-flat: ! java com.icl.saxon.StyleSheet latex-suite-quickstart.xml latex-suite.xsl > latex-suite-quickstart.html ! ! lsq-chunk: ! ( \ ! cd latex-suite-quickstart && \ ! java com.icl.saxon.StyleSheet ../latex-suite-quickstart.xml ../latex-suite-chunk.xsl \ ! ) ! ! lsq-txt: ! db2vim --prefix=lq_ latex-suite-quickstart.xml > latex-suite.txt # vim:nowrap |
From: <sri...@us...> - 2003-06-30 01:20:03
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv32439 Modified Files: imaps.txt Log Message: Index: imaps.txt =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/imaps.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** imaps.txt 31 Dec 2002 10:04:24 -0000 1.1 --- imaps.txt 30 Jun 2003 01:20:00 -0000 1.2 *************** *** 1,80 **** ! *imaps.txt* A Fluid Replacement for the imap command ! For Vim version 6.0 and above ! Last Change: Tue Dec 31 02:00 AM 2002 PST ! ! By Srinath Avadhanula <sr...@fa...>, ! Benji Fisher <be...@me...> ! ! ! =========================================================================== ! MOTIVATION *imap-plugin-motivation* {{{ ! ! This plugin provides a function IMAP() which emulates vims |:imap| function. ! The motivation for providing this plugin is that |:imap| sufffers from ! problems which get increasingly annoying with a large number of mappings. ! ! Consider an example. If you do ! ! imap lhs something ! ! then a mapping is set up. However, there will be the following problems: ! 1. the 'ttimeout' option will generally limit how easily you can type the ! lhs. if you type the left hand side too slowly, then the mapping will not ! be activated. ! 2. if you mistype one of the letters of the lhs, then the mapping is ! deactivated as soon as you backspace to correct the mistake. ! 3. The characters in lhs are shown on top of each other. This is fairly ! distracting. This becomes a real annoyance when a lot of characters ! initiate mappings. ! ! This script provides a function IMAP() which does not suffer from these ! problems. ! ! }}} ! =========================================================================== ! USAGE *imap-plugin-usage* {{{ ! ! Each call to IMAP is made using the sytax: ! > ! call IMAP (lhs, rhs, ft [, phs, phe]) ! ! This is equivalent to having <lhs> map to <rhs> for all files of type <ft>. ! ! Some characters in the <rhs> have special meaning which help in cursor ! placement as described in |imaps-placeholders|. The optional arguments define ! these special characters. ! ! Example One: ! > ! call IMAP ("bit`", "\\begin{itemize}\<cr>\\item <++>\<cr>\\end{itemize}<++>", "tex") ! ! This effectively sets up the map for "bit`" whenever you edit a latex file. ! When you type in this sequence of letters, the following text is inserted: ! > ! \begin{itemize} ! \item * ! \end{itemize}<++> ! ! where * shows the cursor position. The cursor position after inserting the ! text is decided by the position of the first "place-holder". Place holders ! are special characters which decide cursor placement and movement. In the ! example above, the place holder characters are <+ and +>. After you have typed ! in the item, press <C-j> and you will be taken to the next set of <++>'s. ! Therefore by placing the <++> characters appropriately, you can minimize the ! use of movement keys. ! ! NOTE: Set g:Imap_UsePlaceHolders to 0 to disable placeholders altogether. ! Set ! g:Imap_PlaceHolderStart and g:Imap_PlaceHolderEnd ! to something else if you want different place holder characters. ! Also, b:Imap_PlaceHolderStart and b:Imap_PlaceHolderEnd override the values ! of g:Imap_PlaceHolderStart and g:Imap_PlaceHolderEnd respectively. This is ! useful for setting buffer specific place hoders. ! ! Example Two: ! You can use the <C-r> command to insert dynamic elements such as dates. ! call IMAP ('date`', "\<c-r>=strftime('%b %d %Y')\<cr>", '') ! ! sets up the map for date` to insert the current date. ! ! vim:tw=78:et:ts=4:ft=help:norl:fo+=2:fdm=marker --- 1,116 ---- ! IMAP -- A fluid replacement for :imap ! *imaps.txt* ! Srinath Avadhanula <srinath AT fastmail DOT fm> ! ! ! ! Abstract ! ======== ! This plugin provides a function IMAP() which emulates vims |:imap| function. The ! motivation for providing this plugin is that |:imap| sufffers from problems ! which get increasingly annoying with a large number of mappings. ! ! Consider an example. If you do > ! imap lhs something ! ! ! then a mapping is set up. However, there will be the following problems: ! 1. The 'ttimeout' option will generally limit how easily you can type the lhs. ! if you type the left hand side too slowly, then the mapping will not be ! activated. ! ! 2. If you mistype one of the letters of the lhs, then the mapping is deactivated ! as soon as you backspace to correct the mistake. ! ! 3. The characters in lhs are shown on top of each other. This is fairly ! distracting. This becomes a real annoyance when a lot of characters initiate ! mappings. ! ! This script provides a function IMAP() which does not suffer from these ! problems. ! ! ! ! *imaps.txt-toc* ! |im_1| Using IMAP ! ! ================================================================================ ! Viewing this file ! ! This file can be viewed with all the sections and subsections folded to ease ! navigation. By default, vim does not fold help documents. To create the folds, ! press za now. The folds are created via a foldexpr which can be seen in the ! last section of this file. ! ! See |usr_28.txt| for an introduction to folding and |fold-commands| for key ! sequences and commands to work with folds. ! ! ================================================================================ ! Using IMAP *im_1* *imaps-usage* ! ! ! ! Each call to IMAP is made using the sytax: > ! call IMAP (lhs, rhs, ft [, phs, phe]) ! ! ! This is equivalent to having <lhs> map to <rhs> for all files of type <ft>. ! ! Some characters in the <rhs> have special meaning which help in cursor placement ! as described in |imaps-placeholders|. The optional arguments define these ! special characters. ! ! Example One: > ! call IMAP ("bit`", "\\begin{itemize}\<cr>\\item <++>\<cr>\\end{itemize}<++>", "tex") ! ! ! This effectively sets up the map for "bit`" whenever you edit a latex file. When ! you type in this sequence of letters, the following text is inserted: > ! \begin{itemize} ! \item * ! \end{itemize}<++> ! ! where * shows the cursor position. The cursor position after inserting the text ! is decided by the position of the first "place-holder". Place holders are ! special characters which decide cursor placement and movement. In the example ! above, the place holder characters are <+ and +>. After you have typed in the ! item, press <C-j> and you will be taken to the next set of <++>'s. Therefore by ! placing the <++> characters appropriately, you can minimize the use of movement ! keys. ! ! Set g:Imap_UsePlaceHolders to 0 to disable placeholders altogether. ! ! Set g:Imap_PlaceHolderStart and g:Imap_PlaceHolderEnd to something else if you ! want different place holder characters. Also, b:Imap_PlaceHolderStart and ! b:Imap_PlaceHolderEnd override the values of g:Imap_PlaceHolderStart and ! g:Imap_PlaceHolderEnd respectively. This is useful for setting buffer specific ! place hoders. ! ! Example Two: You can use the <C-r> command to insert dynamic elements such as ! dates. > ! call IMAP ('date`', "\<c-r>=strftime('%b %d %Y')\<cr>", '') ! ! ! ! With this mapping, typing date` will insert the present date into the file. ! ! ================================================================================ ! About this file ! ! This file was created automatically from its XML variant using db2vim. db2vim is ! a python script which understands a very limited subset of the Docbook XML 4.2 ! DTD and outputs a plain text file in vim help format. ! ! db2vim can be obtained via anonymous CVS from sourceforge.net. Use ! ! cvs -d:pserver:ano...@cv...:/cvsroot/vim-latex co db2vim ! ! Or you can visit the web-interface to sourceforge CVS at: ! http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vim-latex/db2vim/ ! ! The following modelines should nicely fold up this help manual. ! ! vim:ft=help:fdm=expr:nowrap ! vim:foldexpr=getline(v\:lnum-1)=~'-\\{80}'?'>2'\:getline(v\:lnum-1)=~'=\\{80}'?'>1'\:getline(v\:lnum)=~'=\\{80}'?'0'\:getline(v\:lnum)=~'-\\{80}'?'1'\:'=' ! vim:foldtext=substitute(v\:folddashes.substitute(getline(v\:foldstart),'\\s*\\*.*',"",""),'^--','--\ \ \ \ ','') ! ================================================================================ |
From: <sri...@us...> - 2003-06-30 01:18:54
|
Update of /cvsroot/vim-latex/vimfiles/plugin In directory sc8-pr-cvs1:/tmp/cvs-serv32164 Modified Files: explorer.vim Log Message: First attempt at trying to make explorer.vim not conflict with the default explorer.vim which ships with vim. It would have been _really_ nice to have first discussed the implementation of this feature so I could have avoided this problem beforehand. :( Index: explorer.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/plugin/explorer.vim,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** explorer.vim 2 May 2003 20:00:45 -0000 1.3 --- explorer.vim 30 Jun 2003 01:18:52 -0000 1.4 *************** *** 31,38 **** " Has this already been loaded? ! if exists("loaded_explorer") finish endif ! let loaded_explorer=1 " Line continuation used here --- 31,38 ---- " Has this already been loaded? ! if exists("loaded_tex_explorer") finish endif ! let loaded_tex_explorer=1 " Line continuation used here *************** *** 1342,1358 **** endwhile endfunction - - "--- - " Set up the autocommand to allow directories to be edited - " - augroup fileExplorer - au! - " Fill the window when entering the buffer; ":edit dir". - au BufEnter * call s:EditDir() - " Set the window variables after a split; ":split". - au WinEnter * if !exists("w:sortdirection") | call s:EditDir() | endif - " Fill the windows after Vim has started up. - au VimEnter * call s:EditAll() - augroup end " restore 'cpo' --- 1342,1345 ---- |
From: <sri...@us...> - 2003-06-29 08:39:35
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/tex In directory sc8-pr-cvs1:/tmp/cvs-serv27044 Modified Files: texviewer.vim Log Message: Bug: Using completion in the following situation: \cite{something,<F9> does not work properly because "something" is considered the prefix. Fix: change the s:prefix variable when we have a \cite command to support multiple citations seperated by commas (SA) Index: texviewer.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/tex/texviewer.vim,v retrieving revision 1.28 retrieving revision 1.29 diff -C2 -d -r1.28 -r1.29 *** texviewer.vim 29 Jun 2003 06:15:44 -0000 1.28 --- texviewer.vim 29 Jun 2003 08:31:04 -0000 1.29 *************** *** 106,109 **** --- 106,110 ---- " TODO: Is there a way to clear the search-history w/o making a " useless, inefficient search? + let s:prefix = matchstr(s:prefix, '\([^,]\+,\)\+\zs\([^,]\+\)\ze$') silent! grep! ____HIGHLY_IMPROBABLE___ % if g:Tex_RememberCiteSearch && exists('s:citeSearchHistory') |
From: <sri...@us...> - 2003-06-29 06:15:50
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/tex In directory sc8-pr-cvs1:/tmp/cvs-serv14775 Modified Files: texviewer.vim Log Message: Bug: \bibitems were not being scanned properly. Why: Used grepadd \\bibitem{ instead of just grepadd \bibitem{ Fix: Use 'grep \bibitem{' Index: texviewer.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/tex/texviewer.vim,v retrieving revision 1.27 retrieving revision 1.28 diff -C2 -d -r1.27 -r1.28 *** texviewer.vim 22 Jun 2003 17:57:16 -0000 1.27 --- texviewer.vim 29 Jun 2003 06:15:44 -0000 1.28 *************** *** 518,522 **** call Tex_Debug('finding .bbl file ['.bufname('.').']', 'bib') lcd %:p:h ! exec 'silent! grepadd \\bibitem{'.a:prefix.' %' endif endif --- 518,522 ---- call Tex_Debug('finding .bbl file ['.bufname('.').']', 'bib') lcd %:p:h ! exec 'silent! grepadd \bibitem{'.a:prefix.' %' endif endif *************** *** 542,546 **** split lcd %:p:h ! exec 'silent! grepadd \\bibitem{'.a:prefix.' %' q --- 542,546 ---- split lcd %:p:h ! exec 'silent! grepadd \bibitem{'.a:prefix.' %' q |
From: <sri...@us...> - 2003-06-29 02:18:46
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite In directory sc8-pr-cvs1:/tmp/cvs-serv28054 Modified Files: ChangeLog Log Message: Index: ChangeLog =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/ChangeLog,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** ChangeLog 14 Jun 2003 05:09:10 -0000 1.7 --- ChangeLog 29 Jun 2003 02:18:39 -0000 1.8 *************** *** 1,2 **** --- 1,84 ---- + 28 Jun 2003 + Features + * latex-suite.txt: + vastly improved the latex-suite documentation. Now all documentation + is first written in docbook xml and then converted into html and + vim-help using saxon and db2vim respectively. + * bib_latexSuite.vim: + A new ftplugin file to trigger the bibtex mappings. (SA) + + Changes + * compiler.vim: + change the behavior of the part compilation and viewing as documented. + Remove the "part view" feature because it does not make sense. (SA) + * packages.vim: + change the behavior of finding custom packages. Use vim's native :find + command instead of some complicated parsing of $TEXINPUTS. Introduce a + new g:Tex_TEXINPUTS variable which should be set in the same format as + vim's 'path' setting. (SA) + * texviewer.vim: + Change the way <F9> works for \cite completion. Change the way + g:Tex_BIBINPUTS variable has to be set. The new \cite completion + method is described in detail in the manual. + * envmacros.vim: + changed ETR to insert a more complete template using Tex_SpecialMacros + (Mathieu CLABAUT) + + Bugfixes: + * packages.vim: + Bug: When a \usepackage{} line is inside a fold, then we go into an + infinite loop. (Lin-bo Zhang) + Solution: A temporary hack of first opening up all folds before scanning + and then closing them. This needs to be robustified in the future + using mkview.vim (SA) + * envmacros.vim: + Bug: <F5> did not work for inserting environments which latex-suite + does not recognize. (bug introduced in version 1.32) + Solution: make <F5> insert at least a minimal environment template if + all other methods fail. (SA) + * texviewer.vim: + Bug: Pressing <F9> at the end of a line like + This is a \ref{eqn:something} and this is a comp + would cause errors. + Why: The substitute() command returns the original string if the pattern + does not match causing us to wrongly infer a match. + Fix: Therefore first check if there is a match. + + Bug: Once we complete an equation, we can never complete a word. + Why: s:type is never unlet + Fix: unlet! s:type if there is no match on current line to any known + command. + + Bug: Pressing <CR> during word completion does not take us to the location + of the match, as claimed. + Why: <CR> does "cc <num> | pclose! | cclose!". Because the preview window + with the match is open, therefore cc will take us to the match in + the preview window, after which pclose closes it up! + Fix: Do 'pclose! cc <num> | cclose' instead... + * compiler.vim: + Bug: If we used :TTarget ps, then the compiler would be called as: + dvips -o file.tex.ps file.tex.dvi + instead of + dvips -o file.ps file.dvi + Why: In a recent change, we made RunLaTeX() use filenames with extension. + However, some compilation rules might require filenames w/o extensions + (such as Tex_CompileRule_ps which is 'dvips -o $*.ps $*.dvi') + Fix: Try to guess if the &makeprg requires files w/o extensions by seeing + if it matches '\$\*\.\w\+'. If so, use file-name w/o extension. + Otherwise, retain extension in 'make '.fname + * imaps.vim: + Bug: IMAP_Jumpfunc() and VEnclose() do not work with &selection = + 'exclusive' (Jannie Hofmeyr, Pierre Antoine Champin) + Fix: Select one more character in 'exclusive' mode. (suggested by Pierre + Antoine Champin). + * texviewer.vim: + Bug: On windows gvim +cygwin, \cite completion does not work when the bib + file is in a completeley different location. + Cause: gvim calls grep as "grep -nH @.*{ /path/to/file" + which does not work because grep thinks / corresponds to something + like c:/cygwin, so it looks for the file in the wrong place. + Fix: Always lcd to the current directory of the bib file being searched. + This avoids any path issues. + 13 Jun 2003 Features |
From: <sri...@us...> - 2003-06-28 01:46:37
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv29657 Modified Files: latex-suite.xml latex-suite.txt Log Message: Index: latex-suite.xml =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** latex-suite.xml 23 Jun 2003 09:13:51 -0000 1.6 --- latex-suite.xml 28 Jun 2003 01:46:34 -0000 1.7 *************** *** 85,89 **** In addition, the following settings could go in your ~/.vim/ftplugin/tex.vim file: ! <programlisting>" this is mostly a matter of taste. but LaTeX looks good with just a bit " of indentation. set sw=2 --- 85,89 ---- In addition, the following settings could go in your ~/.vim/ftplugin/tex.vim file: ! <programlisting>" this is mostly a matter of taste. but LaTeX looks good with just a bit " of indentation. [...979 lines suppressed...] ! Note the use of <literal>startskip</literal> and ! <literal>endskip</literal> to allow nesting. ! </para> ! </note> ! </section> </section> <section id="latex-suite-commands-maps"> *************** *** 2592,2596 **** <entry> <literal>'footnote,cite,pageref,label'</literal> ! </entry> </row> </tbody> --- 2792,2796 ---- <entry> <literal>'footnote,cite,pageref,label'</literal> ! </entry> </row> </tbody> Index: latex-suite.txt =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.txt,v retrieving revision 1.30 retrieving revision 1.31 diff -C2 -d -r1.30 -r1.31 *** latex-suite.txt 23 Jun 2003 09:13:51 -0000 1.30 --- latex-suite.txt 28 Jun 2003 01:46:34 -0000 1.31 *************** *** 12,16 **** macros to speed up editing LaTeX documents to functions for forward searching .dvi documents. Latex-suite has been possible because of the contributions of ! many people. Please see latex-suite-credits [|ls_a_dk|] for a list of people who have helped. --- 12,16 ---- macros to speed up editing LaTeX documents to functions for forward searching .dvi documents. Latex-suite has been possible because of the contributions of ! many people. Please see latex-suite-credits [|ls_a_dn|] for a list of people who have helped. [...1959 lines suppressed...] --- 2546,2550 ---- ================================================================================ ! Credits *ls_11* *ls_a_dn* *latex-suite-credits* *************** *** 2462,2466 **** out who has done what. ! *latex-suite-maintainer* *ls_a_dN* The current maintainer(s) of latex-suite is(are) --- 2600,2604 ---- out who has done what. ! *latex-suite-maintainer* *ls_a_dQ* The current maintainer(s) of latex-suite is(are) |
From: <sri...@us...> - 2003-06-27 22:20:19
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite In directory sc8-pr-cvs1:/tmp/cvs-serv4288 Modified Files: envmacros.vim Log Message: - changed ETR to insert a more complete template using Tex_SpecialMacros (Mathieu CLABAUT) Index: envmacros.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/envmacros.vim,v retrieving revision 1.33 retrieving revision 1.34 diff -C2 -d -r1.33 -r1.34 *** envmacros.vim 17 Jun 2003 02:00:13 -0000 1.33 --- envmacros.vim 27 Jun 2003 22:20:16 -0000 1.34 *************** *** 26,29 **** --- 26,31 ---- let s:description ="\\begin{description}\<cr>\\item[<+label+>]<++>\<cr>\\end{description}<++>" let s:document = "\\documentclass[<+options+>]{<+class+>}\<cr>\<cr>\\begin{document}\<cr><++>\<cr>\\end{document}" + let s:tabular = "\\begin{tabular}[<+hbtp+>]{<+format+>}\<cr><++>\<cr>\\end{tabular}" + let s:tabular_star = "\\begin{tabular*}[<+hbtp+>]{<+format+>}\<cr><++>\<cr>\\end{tabular*}" " }}} *************** *** 214,219 **** call s:Tex_EnvMacros('', '&Tables.', 'table*') call s:Tex_EnvMacros('', '&Tables.', 'table2') ! call s:Tex_EnvMacros('ETR', '&Tables.', 'tabular') ! call s:Tex_EnvMacros('', '&Tables.', 'tabular*') " }}} " Math {{{ --- 216,221 ---- call s:Tex_EnvMacros('', '&Tables.', 'table*') call s:Tex_EnvMacros('', '&Tables.', 'table2') ! call s:Tex_SpecialMacros('ETR', '&Tables.', 'tabular', s:tabular) ! call s:Tex_SpecialMacros('', '&Tables.', 'tabular*', s:tabular_star) " }}} " Math {{{ |
From: <sri...@us...> - 2003-06-23 09:13:54
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv23766 Modified Files: latex-suite.xml latex-suite.txt Log Message: Index: latex-suite.xml =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** latex-suite.xml 21 Jun 2003 22:13:07 -0000 1.5 --- latex-suite.xml 23 Jun 2003 09:13:51 -0000 1.6 *************** *** 54,58 **** </articleinfo> <section id="recommended-settings"> ! <title>Recommended Settings</title> <para> Make sure that you create a few necessary settings in your --- 54,65 ---- </articleinfo> <section id="recommended-settings"> ! <title>Installation and recommended Settings</title> ! <para> ! If you are reading this, it most probably means that you have already ! installed &ls; and the help files. If this is not the case, follow the ! detailed instructions on <ulink ! url="http://vim-latex.sourceforge.net/index.php?subject=download">&ls;'s ! download page</ulink>. ! </para> <para> Make sure that you create a few necessary settings in your *************** *** 148,151 **** --- 155,159 ---- </para> </note> + <anchor id="place-holder" /> <note id="place-holders"> <title>Place Holders</title> *************** *** 238,242 **** <listitem> All environment mappings begin with <literal>E</literal> ! </listitem> <listitem> If the environment can be broken up into 2 distinct words, --- 246,250 ---- <listitem> All environment mappings begin with <literal>E</literal> ! </listitem> <listitem> If the environment can be broken up into 2 distinct words, *************** *** 295,299 **** line \end{center}</programlisting> ! </para> </section> <section id="normal-mode-environment-mappings"> --- 303,318 ---- line \end{center}</programlisting> ! </para> ! <anchor id="ls-vmap-f5" /> ! <para> ! You can also select a portion of text visually and press ! <literal><F5></literal> while still in visual mode. This will ! prompt you with a list of environments. (This list can be customized ! via the <link ! linkend="Tex_PromptedEnvironments">g:Tex_PromptedEnvironments</link> ! setting). You can either choose from this list or type in a new ! environment name. Once the selection is done, &ls; encloses the ! visually selected portion in the chosen environment. ! </para> </section> <section id="normal-mode-environment-mappings"> *************** *** 329,332 **** --- 348,352 ---- <title>&latex; command maps</title> <anchor id="ls-imap-f7" /> + <anchor id="ls-imap-s-f7" /> <para> &ls; provides two simple mappings <literal><F7></literal> and *************** *** 347,350 **** --- 367,381 ---- with a list of commands to change it to. </para> + <anchor id="ls-vmap-f7" /> + <para> + You can also select a portion of text visually and press + <literal><F7></literal> while still in visual mode. This will + prompt you with a list of commands. (This list can be customized + via the <link + linkend="Tex_PromptedCommands">g:Tex_PromptedCommands</link> + setting). You can either choose from this list or type in a new + command name. Once the selection is done, &ls; encloses the + visually selected portion in the chosen command. + </para> </section> <section id="font-maps"> *************** *** 1059,1075 **** <para> This module provides an easy way to insert references to labels and ! bibliographic entries. ! </para> ! <para> ! Consider the situation where you are editing a file with two equations ! labelled <literal>eqn:euler</literal> and <literal>eqn:einstein</literal>. ! Now you want to insert a reference to one of these equations. To do this, ! you type the <literal>\ref{eqn:}</literal> command and with the cursor ! placed after <literal>eqn:</literal>, press <literal><F9></literal>. ! This will bring up two new windows beneath the main window you were working ! in as shown in the figure below. </para> ! <programlisting> ! 7 8 These are a couple of equations: 9 +-- 4 lines: eqnarray (eqn:euler) : e^{j\pi} + 1 &=& 0--------------- --- 1090,1142 ---- <para> This module provides an easy way to insert references to labels and ! bibliographic entries. Although the completion capabilites are very ! diverse, &ls; only uses a single key (<literal><F9></literal> by ! default) to do all of it. Pressing the <literal><F9></literal> key ! does different things based on where you are located. &ls; tries to ! guess what you might be trying to complete at the location where you ! pressed <literal><F9></literal>. For example, pressing ! <literal><F9></literal> when you are within a ! <literal>\ref</literal> command will try to list the ! <literal>\label</literal>'s in the present directory. Pressing it when ! you are in a <literal>\cite</literal> command will list bibliography ! keys. &ls; also recognizes commands which need a file name argument and ! will put up an explorer window for you to choose a filename. </para> ! <note id="ls-set-grepprg"> ! <title>Before you start with &ls;'s completion function...</title> ! <para> ! All of &ls;'s completion capabilities depend on a external program ! being available on your system which can search through a number of ! files for a reg-exp pattern. On *nix systems, the pre-installed ! <literal>grep</literal> utility is more than adequate. Most windows ! systems come with a utility <literal>findstr</literal>, but that has ! proven to be very inadequate (for one, it does not have an option to ! force the file name to be displayed when searching through a single ! file). Your best bet is to install <ulink ! url="http://www.cygwin.com">cygwin</ulink>, but if you think thats ! overkill, you can <ulink ! url="http://www.google.com/search?q=windows%20gnu%20grep">search ! for</ulink> a windows implementation of GNU grep. (&ls; testing on ! windows has been done with cygwin's port of GNU grep). ! </para> ! <para> ! Once you have a <literal>grep</literal> program installed, you need to ! set the <literal>'grepprg'</literal> option for vim. Make sure you use a ! setting which forces the program to display file names even when you are ! searching through a single file. For GNU grep, the syntax is ! <programlisting>set grepprg=grep\ -nH\ $*</programlisting> ! </para> ! </note> ! <section id="ls-completion-usage"> ! <title id="ls-completion-usage.title">&ls; completion example</title> ! <para> ! Consider the situation where you are editing a file with two equations ! labelled <literal>eqn:euler</literal> and <literal>eqn:einstein</literal>. ! Now you want to insert a reference to one of these equations. To do this, ! you type the <literal>\ref{eqn:}</literal> command and with the cursor ! placed after <literal>eqn:</literal>, press <literal><F9></literal>. ! This will bring up two new windows beneath the main window you were working ! in as shown in the figure below. ! <programlisting> 8 These are a couple of equations: 9 +-- 4 lines: eqnarray (eqn:euler) : e^{j\pi} + 1 &=& 0--------------- *************** *** 1088,1101 **** ~ ~ - ~ - ~ - ~ - ~ newfile.tex 34,32 Bot newfile.tex|11| \label{eqn:euler} newfile.tex|15| \label{eqn:einstein} ~ - ~ - ~ [Error List] 1,1 All 7 --- 1155,1162 ---- *************** *** 1111,1220 **** newfile.tex [Preview] 11,3 21% </programlisting> ! <para> ! The first window (shown as <literal>[Error List]</literal> above) is a ! <literal>|cwindow|</literal> containing a list of possible matches for the ! reference. The cursor will be located in the first line of this window. The ! bottom window is a <literal>preview-window</literal> showing the context of ! the <literal>\label</literal>. Moving around in the ! <literal>[Error List]</literal> window automatically scrolls the ! preview window so as to always keep showing the context of the ! <literal>\label</literal> being viewed in the ! <literal>[Error List]</literal> window. You can also press ! <literal>J</literal> and <literal>K</literal> in the ! <literal>[ErrorList]</literal> window to scroll the preview window up and ! down. ! </para> ! <para> ! To insert one of the labels, simply position the cursor in the correct line ! in the <literal>[Error List]</literal> window and press ! <literal><enter></literal>. This will immediately close the two newly ! opened windows, get back to the correct location in the original file being ! edited and insert the label into the <literal>\ref</literal> command. ! </para> ! <para> ! If you notice carefully in the example above, the ! <literal>[Error List]</literal> window only showed the matches for the ! equations and did not list any of the figure labels. This is because we ! pressed <literal><F9></literal> after <literal>\ref{eqn:</literal> ! instead of simply after <literal>\ref{</literal>. This caused &ls; to ! search only for those labels which started with the string ! <literal>eqn:</literal>. If you had pressed ! <literal><F9></literal> after a <literal>\ref{</literal>, you would ! have been shown matches from <emphasis>all</emphasis> labels, not just ! those starting with <literal>eqn:</literal>. ! </para> ! <para> ! Thus prefixing all your labels with <literal>eqn:</literal>, ! <literal>fig:</literal>, <literal>tab:</literal> etc. depending on what you ! are labelling will lead to an easier time completing references. ! </para> ! <para> ! The same mechanism also works with citations by pressing <F9> ! after typing "\cite{". In the case of citations, Latex-suite ! automatically displays a list of bibliographic entries found in various ! files in the present directory. ! </para> ! <para> ! This mechanism in fact works with all commands with "ref" or "cite" in them. ! Thus you will get completion with \citen, \citenum or \pageref. If you want ! to create your own command which uses cite or ref mechanism make sure proper ! word is inside it. Example: ! <programlisting>\newcommand{\pref}[1]{~(p.~\pageref{#1})}</programlisting> ! </para> ! <para> ! F9> works also with normal words. You can use it as: "Its name is tetr<F9>". ! Now Latex-suite will look in all .tex files in directory of edited file word ! which is beginning with "tetr". Note: <cr> has here different behavior. It ! does not try to complete word but moves you to location chosen in cwindow. ! </para> ! <para> ! Under MS-Windows you may need to make additional configuration of 'grepgrg' ! option. If you have grep program default value "grep -n" doesn't show file ! names if there is only one matching file. Place ! <programlisting>set grepprg=grep\ -Hn</programlisting> ! in your _vimrc. ! </para> ! <para> ! The functionality in this module is also available via three command-line ! utilities: |TLook|, |TLookBib| and |TLookAll|. ! </para> ! <para> ! You can use the <link ! linkend="Tex_ViewerCwindowHeight">g:Tex_ViewerCwindowHeight</link> and ! <link linkend="Tex_ViewerPreviewHeight">g:Tex_ViewerPreviewHeight</link> ! options in texrc to configure the heights of the "[Error List]" and preview ! window. ! </para> ! <para> ! Latex-suite is distributed with slightly changed explorer.vim. This ! modification allows to perform custom operations in explorer buffer. ! </para> ! <para> ! After \includegraphics{<F9> Latex-suite will open explorer buffer with current ! directory or directory defined with g:Tex_ImageDir variable. When you choose ! graphic file with <cr> its name will be inserted into file as bib key or ! label. If g:Tex_ImageDir is set Latex-suite assume you also defined ! \graphicspath{} command and will insert just file name (without extension). If ! g:Tex_ImageDir is empty (default) it will put relative path to graphic file. ! </para> ! <para> ! After \bibliography{<F9> Latex-suite will open explorer buffer with current ! directory. After <cr> name of relative path to chosen file (without extension) ! will be inserted. ! </para> ! <para> ! In both cases explorer window will open with basic filter. You should not see ! uninteresting in current context files. ! </para> ! <para> ! You can regulate height of explorer window with g:Tex_ExplorerHeight variable ! (default 10). ! </para> <section id="latex-completion-cite"> <title>&ls; <literal>\cite</literal> completion</title> <para> ! When you press <literal><F9></literal> in insert mode after a ! <literal>\cite{</literal>, &ls; will try to complete it with ! bibliographic entries. </para> <para> --- 1172,1268 ---- newfile.tex [Preview] 11,3 21% </programlisting> ! </para> ! <para> ! The first window (shown as <literal>[Error List]</literal> above) is a ! <literal>|cwindow|</literal> containing a list of possible matches for the ! reference. The cursor will be located in the first line of this window. The ! bottom window is a <literal>preview-window</literal> showing the context of ! the <literal>\label</literal>. Moving around in the ! <literal>[Error List]</literal> window automatically scrolls the ! preview window so as to always keep showing the context of the ! <literal>\label</literal> being viewed in the ! <literal>[Error List]</literal> window. You can also press ! <literal>J</literal> and <literal>K</literal> in the ! <literal>[ErrorList]</literal> window to scroll the preview window up and ! down. ! </para> ! <para> ! To insert one of the labels, simply position the cursor in the correct line ! in the <literal>[Error List]</literal> window and press ! <literal><enter></literal>. This will immediately close the two newly ! opened windows, get back to the correct location in the original file being ! edited and insert the label into the <literal>\ref</literal> command. ! </para> ! <para> ! If you notice carefully in the example above, the ! <literal>[Error List]</literal> window only showed the matches for the ! equations and did not list any of the figure labels. This is because we ! pressed <literal><F9></literal> after <literal>\ref{eqn:</literal> ! instead of simply after <literal>\ref{</literal>. This caused &ls; to ! search only for those labels which started with the string ! <literal>eqn:</literal>. If you had pressed ! <literal><F9></literal> after a <literal>\ref{</literal>, you would ! have been shown matches from <emphasis>all</emphasis> labels, not just ! those starting with <literal>eqn:</literal>. ! </para> ! <para> ! Thus prefixing all your labels with <literal>eqn:</literal>, ! <literal>fig:</literal>, <literal>tab:</literal> etc. depending on what you ! are labelling will lead to an easier time completing references. ! </para> ! </section> ! <section id="ls-completion-ref"> ! <title>&ls; \ref completion</title> ! <para> ! To complete a <literal>|\ref|</literal> command, position yourself ! between the curly braces of a <literal>\ref</literal> command and press ! <literal><F9></literal>. For example, you can press ! <literal><F9></literal> just after <literal>\ref{</literal> or ! after <literal>\ref{eqn:</literal>. &ls; will search for ! <literal>\label</literal>'s in all tex files in the current directory ! and display the results in two windows as desribed in section <link ! linkend="ls-completion-usage" ! endterm="ls-completion-usage.title"></link>. ! </para> ! <para> ! Any command which contains the pattern <literal>ref</literal> in it is ! treated as if it is a way to call <literal>\ref</literal> indirectly. ! Thus pressing <literal><F9></literal> after something like ! <literal>\pref{</literal> will also search for ! <literal>\label</literal>'s. ! </para> ! <para> ! When you press <literal><F9></literal> after typing ! <literal>\ref{eqn:</literal> then &ls; will only list ! <literal>\label</literal>'s which begin with <literal>eqn:</literal> ! If you press <literal><F9></literal> after a simple ! <literal>\ref{</literal>, then &ls; will list all ! <literal>\label</literal>'s in all the tex files in the present ! directory. ! </para> ! <note> ! <title>HINT</title> ! <para> ! By prefixing your labels with eqn:, fig: etc, you can easily filter ! out a lot of undesirable results. ! </para> ! </note> ! </section> <section id="latex-completion-cite"> <title>&ls; <literal>\cite</literal> completion</title> <para> ! When you press <literal><F9></literal> in insert mode after ! <literal>\cite{pre</literal>, &ls; will present a list of valid ! bibliographic keys starting with <literal>"pre"</literal> and ask you ! to choose from one of them. ("pre" can be left empty in which case all ! valid bibliographic keys will be listed). The window setup is as ! described in section <link linkend="ls-completion-usage" ! endterm="ls-completion-usage.title"></link>. ! </para> ! <para> ! <literal><F9></literal> will also work in a similar way after any ! command which contains the word <literal>cite</literal> in it. For ! example, pressing <literal><F9></literal> will also work with ! <literal>\citenum</literal> etc. </para> <para> *************** *** 1294,1297 **** --- 1342,1398 ---- </section> </section> + <section id="ls-filename-completion"> + <title>&ls; filename completion</title> + <para> + When you press <literal><F9></literal> at a location where &ls; + guesses a filename needs to be typed, then a new explorer window will + open up with the list of files. You can use this window to change + directories etc. Pressing <literal><enter></literal> on a filename + in the explorer window will automatically close the explorer window, + return to the location where you pressed <literal><F9></literal> + from and insert the filename into that position. + </para> + <para> + &ls; also tries to guess what kinds of files you might not want to + insert and hides those accordingly. For example, if you press + <literal><F9></literal> when you are located at + <literal>\includegraphics{</literal>, then &ls; knows that you will not + want to insert <literal>.tex</literal> files. Therefore, the explorer + window will automatically hide these files. + </para> + <para> + As of now, &ls; recognizes the following commands for filename + completion. Along with the commands, this table also lists the + files which &ls; will not show for completing each command. + </para> + <informaltable frame="all"> + <tgroup cols="2"> + <thead> + <row> + <entry>command</entry> + <entry>hide pattern</entry> + </row> + </thead> + <tbody> + <row> + <entry><literal>\bibliography</literal></entry> + <entry><literal>'^\.,\.[^b]..$'</literal></entry> + </row> + <row> + <entry><literal>\include</literal> <literal>\includeonly</literal></entry> + <entry><literal>'^\.,\.[^t]..$'</literal></entry> + </row> + <row> + <entry><literal>\includegraphics</literal> <literal>\psfig</literal></entry> + <entry><literal>'^\.,\.tex$,\.bib$,\.bbl$,\.zip$,\.gz$'</literal></entry> + </row> + <row> + <entry><literal>\input</literal></entry> + <entry><literal>''</literal></entry> + </row> + </tbody> + </tgroup> + </informaltable> + </section> </section> <section id="latex-compiling"> *************** *** 1595,1599 **** meaningful fold-text, otherwise the second line of the environment is displayed along with the name of the environment. In other words, the following - </para> <programlisting>\begin{figure}[h] \centerline{\psfig{figure=slidercrank.eps,height=6cm}} --- 1696,1699 ---- *************** *** 1605,1614 **** \sin(\pi) = 0 \end{eqnarray}</programlisting> <para> will be shown as: - </para> <programlisting>+--- 5 lines: figure (fig:slidercrank) : The Slider Crank Mechanism. ----- % a LaTeX comment. +--- 3 lines: eqnarray () : \sin(\pi) = 0 --------------------------------</programlisting> <section id="default-folding"> <title>Default Folding Scheme in &ls;</title> --- 1705,1715 ---- \sin(\pi) = 0 \end{eqnarray}</programlisting> + </para> <para> will be shown as: <programlisting>+--- 5 lines: figure (fig:slidercrank) : The Slider Crank Mechanism. ----- % a LaTeX comment. +--- 3 lines: eqnarray () : \sin(\pi) = 0 --------------------------------</programlisting> + </para> <section id="default-folding"> <title>Default Folding Scheme in &ls;</title> *************** *** 2118,2124 **** don't have to enclose argument in "". <cr> takes you to location. Other keys work as described in |latex-viewer|. - Note: TLookBib uses :grep command and is using 'grepprg'. Its - regular expressions can be different from those of Vim. </para> </section> <section id="TLookAll"> --- 2219,2229 ---- don't have to enclose argument in "". <cr> takes you to location. Other keys work as described in |latex-viewer|. </para> + <note> + <para> + TLookBib uses :grep command and is using 'grepprg'. Its + regular expressions can be different from those of Vim. + </para> + </note> </section> <section id="TLookAll"> *************** *** 2477,2480 **** --- 2582,2610 ---- </para> </note> + </section> + <section id="Tex_PromptedCommands"> + <title>g:Tex_PromptedCommands</title> + <informaltable frame="all"> + <tgroup cols="2"> + <tbody> + <row><entry>Type</entry><entry>String</entry></row> + <row><entry>Default Value</entry> + <entry> + <literal>'footnote,cite,pageref,label'</literal> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + This string represents a comma seperated list of &latex; commands + which &ls; uses for the <literal><F7></literal> and + <literal><S-F7></literal> maps as described <link + linkend="latex-command-maps">here</link>. + </para> + <para> + Leaving this string empty will leave the <literal><F7></literal> + key unmapped. + </para> </section> </section> Index: latex-suite.txt =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.txt,v retrieving revision 1.29 retrieving revision 1.30 diff -C2 -d -r1.29 -r1.30 *** latex-suite.txt 21 Jun 2003 22:16:15 -0000 1.29 --- latex-suite.txt 23 Jun 2003 09:13:51 -0000 1.30 *************** *** 12,17 **** macros to speed up editing LaTeX documents to functions for forward searching .dvi documents. Latex-suite has been possible because of the contributions of ! many people. Please see latex-suite-credits [|latex-suite-credits|] for a list ! of people who have helped. Latex-suite is released under the Vim charityware license. For license and --- 12,17 ---- macros to speed up editing LaTeX documents to functions for forward searching .dvi documents. Latex-suite has been possible because of the contributions of ! many people. Please see latex-suite-credits [|ls_a_dk|] for a list of people who [...2763 lines suppressed...] ! ================================================================================ ! About this file ! ! This file was created automatically from its XML variant using db2vim. db2vim is ! a python script which understands a very limited subset of the Docbook XML 4.2 ! DTD and outputs a plain text file in vim help format. ! ! db2vim can be obtained via anonymous CVS from sourceforge.net. Use ! ! cvs -d:pserver:ano...@cv...:/cvsroot/vim-latex co db2vim ! ! Or you can visit the web-interface to sourceforge CVS at: ! http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vim-latex/db2vim/ ! ! The following modelines should nicely fold up this help manual. ! ! vim:ft=help:fdm=expr:nowrap vim:foldexpr=getline(v\:lnum-1)=~'-\\{80}'?'>2'\:getline(v\:lnum-1)=~'=\\{80}'?'>1'\:getline(v\:lnum)=~'=\\{80}'?'0'\:getline(v\:lnum)=~'-\\{80}'?'1'\:'=' ! vim:foldtext=substitute(v\:folddashes.substitute(getline(v\:foldstart),'\\s*\\*.*',"",""),'^--','\ \ \ \ \ \ ','') ================================================================================ |
From: <sri...@us...> - 2003-06-22 17:57:20
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/tex In directory sc8-pr-cvs1:/tmp/cvs-serv5415 Modified Files: texviewer.vim Log Message: Bug: On windows gvim +cygwin, \cite completion does not work when the bib file is in a completeley different location. Cause: gvim calls grep as "grep -nH @.*{ /path/to/file" which does not work because grep thinks / corresponds to something like c:/cygwin, so it looks for the file in the wrong place. Fix: Always lcd to the current directory of the bib file being searched. This avoids any path issues. Index: texviewer.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/tex/texviewer.vim,v retrieving revision 1.26 retrieving revision 1.27 diff -C2 -d -r1.26 -r1.27 *** texviewer.vim 20 Jun 2003 06:11:54 -0000 1.26 --- texviewer.vim 22 Jun 2003 17:57:16 -0000 1.27 *************** *** 504,517 **** split let thisbufnum = bufnr('%') exec 'silent! find '.Tex_Strntok(bibnames, ',', i).'.bib' if bufnr('%') != thisbufnum " use the appropriate syntax for the .bib file. exec 'silent! grepadd @.*{'.a:prefix.' %' else let thisbufnum = bufnr('%') - call Tex_Debug('silent! find '.Tex_Strntok(bibnames, ',', i).'.bbl from '.thisbufnum, 'bib') exec 'silent! find '.Tex_Strntok(bibnames, ',', i).'.bbl' call Tex_Debug('now in bufnum#'.bufnr('%'), 'bib') if bufnr('%') != thisbufnum exec 'silent! grepadd \\bibitem{'.a:prefix.' %' endif --- 504,521 ---- split let thisbufnum = bufnr('%') + call Tex_Debug('silent! find '.Tex_Strntok(bibnames, ',', i).'.bib', 'bib') exec 'silent! find '.Tex_Strntok(bibnames, ',', i).'.bib' if bufnr('%') != thisbufnum + call Tex_Debug('finding .bib file ['.bufname('%').']', 'bib') + lcd %:p:h " use the appropriate syntax for the .bib file. exec 'silent! grepadd @.*{'.a:prefix.' %' else let thisbufnum = bufnr('%') exec 'silent! find '.Tex_Strntok(bibnames, ',', i).'.bbl' call Tex_Debug('now in bufnum#'.bufnr('%'), 'bib') if bufnr('%') != thisbufnum + call Tex_Debug('finding .bbl file ['.bufname('.').']', 'bib') + lcd %:p:h exec 'silent! grepadd \\bibitem{'.a:prefix.' %' endif *************** *** 535,539 **** --- 539,547 ---- let foundCiteFile = 1 + + split + lcd %:p:h exec 'silent! grepadd \\bibitem{'.a:prefix.' %' + q return 1 *************** *** 549,559 **** let filename = matchstr(getline('.'), '\\\(input\|include\){\zs.\{-}\ze}') ! let v:errmsg = '' exec 'silent! find '.filename ! if v:errmsg == '' " DANGER! recursive call. let foundCiteFile = Tex_ScanFileForCite(a:prefix) - exec 'e #'.presBufNum endif if foundCiteFile --- 557,571 ---- let filename = matchstr(getline('.'), '\\\(input\|include\){\zs.\{-}\ze}') ! ! split ! let thisbufnum = bufnr('%') ! exec 'silent! find '.filename ! if bufnr('%') != thisbufnum " DANGER! recursive call. + call Tex_Debug('scanning recursively in ['.bufname('%').']', 'bib') let foundCiteFile = Tex_ScanFileForCite(a:prefix) endif + q if foundCiteFile |
From: <sri...@us...> - 2003-06-21 22:16:18
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv7004 Modified Files: latex-suite.txt Log Message: Oops! Some debugging statements got into latex-suite.txt. Have modified db2vim so it doesn't happen again. Index: latex-suite.txt =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.txt,v retrieving revision 1.28 retrieving revision 1.29 diff -C2 -d -r1.28 -r1.29 *** latex-suite.txt 21 Jun 2003 22:13:07 -0000 1.28 --- latex-suite.txt 21 Jun 2003 22:16:15 -0000 1.29 *************** *** 1,44 **** - bodyText = [[u'w', u'address'], [u'a', u'author'], [u'b', u'booktitle'], [u'c', u'chapter'], [u'd', u'edition'], [u'e', u'editor'], [u'h', u'howpublished'], [u'i', u'institution'], [u'k', u'isbn'], [u'j', u'journal'], [u'm', u'month'], [u'z', u'note'], [u'n', u'number'], [u'o', u'organization'], [u'p', u'pages'], [u'q', u'publisher'], [u'r', u'school'], [u's', u'series'], [u't', u'title'], [u'u', u'type'], [u'v', u'volume'], [u'y', u'year']] - bodyText = [[u'(', u'\\left( <++> \\right)'], [u'[', u'\\left[ <++> \\right]'], [u'|', u'\\left| <++> \\right|'], [u'{', u'\\left\\{ <++> \\right\\}'], [u'<', u'\\langle <++> \\rangle'], [u'q', u'\\lefteqn{<++>}<++>']] - bodyText = [[u'{New}', u'Creates a new (unnamed) buffer in the latex-suite/macros/ directory. Use the\ncommand :TexMacroNew in non-gui mode.'], [u'{Edit}', u'Opens up the corresponding macro file for editing. Use :TexMacroEdit in non-gui\nmode.'], [u'{Delete}', u'Deletes the corresponding macro. Use the prefixed numbers for fast navigation of\nmenus. Use :TexMacroDelete in non-gui mode.'], [u'{Redraw}', u'Rescans the macros/ directory and refreshes the macros list.']] - bodyText = [[u'startpat', u'a line matching this pattern defines the beginning of a fold.'], [u'endpat', u'a line matching this pattern defines the end of a fold.'], [u'startoff', u'this is the offset from the starting line at which folding will actually start'], [u'endoff', u'like startoff, but gives the offset of the actual fold end from the line satisfying endpat. startoff and\nendoff are necessary when the folding region does not have a specific end pattern corresponding to a start\npattern. for example in latex, \\begin{section} defines the beginning of a section, but its not necessary to\nhave a corresponding \\end{section} the section is assumed to end 1 line before another section starts.'], [u'startskip', u'A Pattern Which Defines The Beginning Of A "Skipped" Region.\n\nFor example, suppose we define a \\itemize fold as follows: >\n = \'^\\s*\\\\item\',\n = \'^\\s*\\\\item\\|^\\s*\\\\end{\\(enumerate\\|itemize\\|description\\)}\',\n = 0,\n = -1&codeend;\n\nThis defines a fold which starts with a line beginning with an \\item and ending one line before a line\nbeginning with an \\item or \\end{enumerate} etc.\n\nThen, as long as \\item\'s are not nested things are fine. However, once items begin to nest, the fold\nstarted by one \\item can end because of an \\item in an \\itemize environment within this \\item. i.e, the\nfollowing can happen: >\n \\begin{itemize}\n \\item Some text <------- fold will start here\n This item will contain a nested item\n \\begin{itemize} <----- fold will end here because next line contains \\item...\n \\item Hello \n \\end{itemize} <----- ... instead of here.\n \\item Next item of the parent itemize \n \\end{itemize}&codeend;\n\nTherefore, in order to completely define a folding item which allows nesting, we need to also define a\n"skip" pattern. startskip and end skip do that. Leave \'\' when there is no nesting.'], [u'endskip', u'the pattern which defines the end of the "skip" pattern for nested folds.']] - bodyText = [[u'<Plug>IMAP_JumpForward', u'<C-j>'], [u'<Plug>IMAP_JumpBack', u'(none)'], [u'<Plug>IMAP_DeleteAndJumpForward', u'(none)'], [u'<Plug>IMAP_DeleteAndJumpBack', u'(none)']] - bodyText = [[u'<Plug>Tex_MathBF', u'<Alt-B>'], [u'<Plug>Tex_MathCal', u'<Alt-C>'], [u'<Plug>Tex_LeftRight', u'<Alt-L>']] - bodyText = [[u'0', u'part'], [u'1', u'chapter'], [u'2', u'section'], [u'3', u'subsection'], [u'4', u'subsubsection'], [u'5', u'paragraph'], [u'6', u'subparagraph']] - bodyText = [[u'+<n>', u'inserts section name <n> logical levels above the last used comand'], [u'-<n>', u'inserts section name <n> logical levels below the last used comand'], [u'+', u'inserts section name one logical level below the last used command (equal to +1).'], [u'++', u'inserts section name two logical levels below the last used command (equal to +2).'], [u'-', u'inserts section name one logical level over the last used command (equal to -1).'], [u'--', u'inserts section name two logical levels over the last used command (equal to -2).']] - bodyText = [[u'g', u'General shortcuts'], [u'e', u'Environment shortcuts'], [u'f', u'Font shortcuts'], [u's', u'Section shortcuts'], [u'a', u'All shortcuts']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Imap_PlaceHolderStart', u'String', u"'<+'"], [u'Imap_PlaceHolderEnd', u'String', u"'+>'"]] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'g:Tex_EnvironmentMaps', u'Environment Mappings [|insert-mode-environment-mappings|]', u'1'], [u'g:Tex_EnvironmentMenus', '', u'1'], [u'g:Tex_FontMaps', u'Font Mappings [|font-maps|]', u'1'], [u'g:Tex_FontMenus', '', u'1'], [u'g:Tex_SectionMaps', u'Section Mappings [|section-mappings|]', u'1'], [u'g:Tex_SectionMenus', '', u'1']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']] - bodyText = [[u'Type', u'String'], [u'Default Value', u"'`'"]] - bodyText = [[u'Type', u'String'], [u'Default Value', u"','"]] - bodyText = [[u'Type', u'String'], [u'Default Value', u"'eqnarray*,eqnarray,equation,equation*,\\[,$$,align,align*'"]] - bodyText = [[u'Type', u'String'], [u'Default Value', u"'eqnarray*,eqnarray,bmatrix'"]] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'g:Tex_SmartQuoteOpen', u'"``"'], [u'g:Tex_SmartQuoteClose', u'"\'\'"']] - bodyText = [[u'g:Tex_ViewerCwindowHeight', u'The height of the cwindow which displays the list of \\labels etc.', u'5'], [u'g:Tex_ViewerPreviewHeight', u'The height of the preview window which shows the context of a \\label etc.', u'10'], [u'g:Tex_ExplorerHeight', u'The height of the explorer window which lists the files from which to choose an\nimage file.', u'10'], [u'g:Tex_ImageDir', u'The directory to scan for images', u"''"]] - bodyText = [[u'Type', u'string'], [u'Default Value', u"''"]] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']] - bodyText = [[u'Type', u'String'], [u'Default Value', u'dvi for windows/*nix and pdf for mac']] - bodyText = [[u'g:Tex_CompileRule_dvi', u"'latex -interaction=nonstopmode $*'"], [u'g:Tex_CompileRule_ps', u"'ps2pdf $*'"], [u'g:Tex_CompileRule_pdf', u"'pdflatex -interaction=nonstopmode $*'"]] - bodyText = [[u'Type', u'String'], [u'Default Value', u'a new-line seperated list of patterns as described below']] - bodyText = [[u'Type', u'Integer'], [u'Default Value', u'7']] - bodyText = [[u'g:Tex_ViewRule_dvi', u"'yap -1'", u"'xdvi'"], [u'g:Tex_ViewRule_ps', u"'gsview32'", u"'ghostview'"], [u'g:Tex_ViewRule_pdf', u"'AcroRd32'", u"'xpdf'"]] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'String'], [u'Default Value', u"'TeX-'"]] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] - bodyText = [[u'Type', u'string'], [u'Default Value', u"''"]] - bodyText = [[u'Lubomir Host', u'provided the diacritics and also helped in development.\n\n'], [u'Alexander Wagner', u'valuable suggestions during development.\n\n'], [u'Luc Hermitte', u"his variation of Stephen Riehm's bracketing system is used in latex-suite.\n\n"], [u'Gergely Kontra', u'the clever little JumpFunc() in imaps.vim is due to him. The implementation of the\ntemplates also borrows from mu-template.vim by him.\n\n'], [u'Dimitri Antoniou', u'author of ltags and also provided the nice tip about forward / reverse search on\nDVI documents.\n\n'], [u'Stephen Riehm', u'the extremely helpful bracketing system is from him.\n\n'], [u'Alan Schmitt', u'provided some macros/folding elements.\n\n'], [u'Hari Krishna Dara', u'for ExecMap(), the clever little function which makes typing visual mode mappings\nso much easier and error-free.\n\n'], [u'Alan G Isac', u'for the comprehensive BibT() function for entering bibtex entries.\n\n'], [u'Gontran Baerts', u'for libList.vim\n\n'], [u'Peter Heslin', u'useful discussion and also a lot of bug fixes. the %%fakesection in folding.vim.\n\n']] Latex-Suite Reference *latex-suite.txt* --- 1,2 ---- |
From: <sri...@us...> - 2003-06-21 22:13:10
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv6663 Modified Files: latex-suite.txt latex-suite.xml Log Message: More documentation. more fixed typos... Still a lot more to go... Index: latex-suite.txt =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.txt,v retrieving revision 1.27 retrieving revision 1.28 diff -C2 -d -r1.27 -r1.28 *** latex-suite.txt 20 Jun 2003 06:02:39 -0000 1.27 --- latex-suite.txt 21 Jun 2003 22:13:07 -0000 1.28 *************** *** 1,2 **** --- 1,44 ---- + bodyText = [[u'w', u'address'], [u'a', u'author'], [u'b', u'booktitle'], [u'c', u'chapter'], [u'd', u'edition'], [u'e', u'editor'], [u'h', u'howpublished'], [u'i', u'institution'], [u'k', u'isbn'], [u'j', u'journal'], [u'm', u'month'], [u'z', u'note'], [u'n', u'number'], [u'o', u'organization'], [u'p', u'pages'], [u'q', u'publisher'], [u'r', u'school'], [u's', u'series'], [u't', u'title'], [u'u', u'type'], [u'v', u'volume'], [u'y', u'year']] + bodyText = [[u'(', u'\\left( <++> \\right)'], [u'[', u'\\left[ <++> \\right]'], [u'|', u'\\left| <++> \\right|'], [u'{', u'\\left\\{ <++> \\right\\}'], [u'<', u'\\langle <++> \\rangle'], [u'q', u'\\lefteqn{<++>}<++>']] + bodyText = [[u'{New}', u'Creates a new (unnamed) buffer in the latex-suite/macros/ directory. Use the\ncommand :TexMacroNew in non-gui mode.'], [u'{Edit}', u'Opens up the corresponding macro file for editing. Use :TexMacroEdit in non-gui\nmode.'], [u'{Delete}', u'Deletes the corresponding macro. Use the prefixed numbers for fast navigation of\nmenus. Use :TexMacroDelete in non-gui mode.'], [u'{Redraw}', u'Rescans the macros/ directory and refreshes the macros list.']] + bodyText = [[u'startpat', u'a line matching this pattern defines the beginning of a fold.'], [u'endpat', u'a line matching this pattern defines the end of a fold.'], [u'startoff', u'this is the offset from the starting line at which folding will actually start'], [u'endoff', u'like startoff, but gives the offset of the actual fold end from the line satisfying endpat. startoff and\nendoff are necessary when the folding region does not have a specific end pattern corresponding to a start\npattern. for example in latex, \\begin{section} defines the beginning of a section, but its not necessary to\nhave a corresponding \\end{section} the section is assumed to end 1 line before another section starts.'], [u'startskip', u'A Pattern Which Defines The Beginning Of A "Skipped" Region.\n\nFor example, suppose we define a \\itemize fold as follows: >\n = \'^\\s*\\\\item\',\n = \'^\\s*\\\\item\\|^\\s*\\\\end{\\(enumerate\\|itemize\\|description\\)}\',\n = 0,\n = -1&codeend;\n\nThis defines a fold which starts with a line beginning with an \\item and ending one line before a line\nbeginning with an \\item or \\end{enumerate} etc.\n\nThen, as long as \\item\'s are not nested things are fine. However, once items begin to nest, the fold\nstarted by one \\item can end because of an \\item in an \\itemize environment within this \\item. i.e, the\nfollowing can happen: >\n \\begin{itemize}\n \\item Some text <------- fold will start here\n This item will contain a nested item\n \\begin{itemize} <----- fold will end here because next line contains \\item...\n \\item Hello \n \\end{itemize} <----- ... instead of here.\n \\item Next item of the parent itemize \n \\end{itemize}&codeend;\n\nTherefore, in order to completely define a folding item which allows nesting, we need to also define a\n"skip" pattern. startskip and end skip do that. Leave \'\' when there is no nesting.'], [u'endskip', u'the pattern which defines the end of the "skip" pattern for nested folds.']] + bodyText = [[u'<Plug>IMAP_JumpForward', u'<C-j>'], [u'<Plug>IMAP_JumpBack', u'(none)'], [u'<Plug>IMAP_DeleteAndJumpForward', u'(none)'], [u'<Plug>IMAP_DeleteAndJumpBack', u'(none)']] + bodyText = [[u'<Plug>Tex_MathBF', u'<Alt-B>'], [u'<Plug>Tex_MathCal', u'<Alt-C>'], [u'<Plug>Tex_LeftRight', u'<Alt-L>']] + bodyText = [[u'0', u'part'], [u'1', u'chapter'], [u'2', u'section'], [u'3', u'subsection'], [u'4', u'subsubsection'], [u'5', u'paragraph'], [u'6', u'subparagraph']] + bodyText = [[u'+<n>', u'inserts section name <n> logical levels above the last used comand'], [u'-<n>', u'inserts section name <n> logical levels below the last used comand'], [u'+', u'inserts section name one logical level below the last used command (equal to +1).'], [u'++', u'inserts section name two logical levels below the last used command (equal to +2).'], [u'-', u'inserts section name one logical level over the last used command (equal to -1).'], [u'--', u'inserts section name two logical levels over the last used command (equal to -2).']] + bodyText = [[u'g', u'General shortcuts'], [u'e', u'Environment shortcuts'], [u'f', u'Font shortcuts'], [u's', u'Section shortcuts'], [u'a', u'All shortcuts']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Imap_PlaceHolderStart', u'String', u"'<+'"], [u'Imap_PlaceHolderEnd', u'String', u"'+>'"]] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'g:Tex_EnvironmentMaps', u'Environment Mappings [|insert-mode-environment-mappings|]', u'1'], [u'g:Tex_EnvironmentMenus', '', u'1'], [u'g:Tex_FontMaps', u'Font Mappings [|font-maps|]', u'1'], [u'g:Tex_FontMenus', '', u'1'], [u'g:Tex_SectionMaps', u'Section Mappings [|section-mappings|]', u'1'], [u'g:Tex_SectionMenus', '', u'1']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']] + bodyText = [[u'Type', u'String'], [u'Default Value', u"'`'"]] + bodyText = [[u'Type', u'String'], [u'Default Value', u"','"]] + bodyText = [[u'Type', u'String'], [u'Default Value', u"'eqnarray*,eqnarray,equation,equation*,\\[,$$,align,align*'"]] + bodyText = [[u'Type', u'String'], [u'Default Value', u"'eqnarray*,eqnarray,bmatrix'"]] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'g:Tex_SmartQuoteOpen', u'"``"'], [u'g:Tex_SmartQuoteClose', u'"\'\'"']] + bodyText = [[u'g:Tex_ViewerCwindowHeight', u'The height of the cwindow which displays the list of \\labels etc.', u'5'], [u'g:Tex_ViewerPreviewHeight', u'The height of the preview window which shows the context of a \\label etc.', u'10'], [u'g:Tex_ExplorerHeight', u'The height of the explorer window which lists the files from which to choose an\nimage file.', u'10'], [u'g:Tex_ImageDir', u'The directory to scan for images', u"''"]] + bodyText = [[u'Type', u'string'], [u'Default Value', u"''"]] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']] + bodyText = [[u'Type', u'String'], [u'Default Value', u'dvi for windows/*nix and pdf for mac']] + bodyText = [[u'g:Tex_CompileRule_dvi', u"'latex -interaction=nonstopmode $*'"], [u'g:Tex_CompileRule_ps', u"'ps2pdf $*'"], [u'g:Tex_CompileRule_pdf', u"'pdflatex -interaction=nonstopmode $*'"]] + bodyText = [[u'Type', u'String'], [u'Default Value', u'a new-line seperated list of patterns as described below']] + bodyText = [[u'Type', u'Integer'], [u'Default Value', u'7']] + bodyText = [[u'g:Tex_ViewRule_dvi', u"'yap -1'", u"'xdvi'"], [u'g:Tex_ViewRule_ps', u"'gsview32'", u"'ghostview'"], [u'g:Tex_ViewRule_pdf', u"'AcroRd32'", u"'xpdf'"]] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'String'], [u'Default Value', u"'TeX-'"]] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'0']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'Boolean'], [u'Default Value', u'1']] + bodyText = [[u'Type', u'string'], [u'Default Value', u"''"]] + bodyText = [[u'Lubomir Host', u'provided the diacritics and also helped in development.\n\n'], [u'Alexander Wagner', u'valuable suggestions during development.\n\n'], [u'Luc Hermitte', u"his variation of Stephen Riehm's bracketing system is used in latex-suite.\n\n"], [u'Gergely Kontra', u'the clever little JumpFunc() in imaps.vim is due to him. The implementation of the\ntemplates also borrows from mu-template.vim by him.\n\n'], [u'Dimitri Antoniou', u'author of ltags and also provided the nice tip about forward / reverse search on\nDVI documents.\n\n'], [u'Stephen Riehm', u'the extremely helpful bracketing system is from him.\n\n'], [u'Alan Schmitt', u'provided some macros/folding elements.\n\n'], [u'Hari Krishna Dara', u'for ExecMap(), the clever little function which makes typing visual mode mappings\nso much easier and error-free.\n\n'], [u'Alan G Isac', u'for the comprehensive BibT() function for entering bibtex entries.\n\n'], [u'Gontran Baerts', u'for libList.vim\n\n'], [u'Peter Heslin', u'useful discussion and also a lot of bug fixes. the %%fakesection in folding.vim.\n\n']] Latex-Suite Reference *latex-suite.txt* *************** *** 27,32 **** |ls_2| Inserting Templates |ls_3| Latex-Suite Macros ! |ls_3_1| Insert-mode Environment Mappings ! |ls_3_2| Visual-mode Environment Mappings |ls_3_3| Font Mappings |ls_3_4| Section Mappings --- 69,74 ---- |ls_2| Inserting Templates |ls_3| Latex-Suite Macros ! |ls_3_1| Environment Mappings ! |ls_3_2| LaTeX command maps |ls_3_3| Font Mappings |ls_3_4| Section Mappings *************** *** 46,50 **** |ls_5_1| Latex-Suite \cite completion |ls_6| Compiling LaTeX files via Latex-Suite ! |ls_6_1| Setting Compilation rules. |ls_6_2| Specifying which file to compile |ls_6_3| Customizing the compiler output --- 88,92 ---- |ls_5_1| Latex-Suite \cite completion |ls_6| Compiling LaTeX files via Latex-Suite ! |ls_6_1| Setting Compilation rules |ls_6_2| Specifying which file to compile |ls_6_3| Customizing the compiler output *************** *** 72,75 **** --- 114,127 ---- ================================================================================ + Viewing this file + + This file can be viewed with all the sections and subsections folded to ease + navigation. By default, vim does not fold help documents. To create the folds, + press za now. + + See |usr_28.txt| for an introduction to folding and |fold-commands| for key + sequences and commands to work with folds. + + ================================================================================ Recommended Settings *ls_1* *recommended-settings* *************** *** 77,86 **** ! Latex-Suite works best if you have the following settings in your ~/.vimrc: > ! " this line is responsible for loading latex-suite when a .tex file is ! " opened. filetype plugin on ! " for automatic indentation specific to LaTeX. filetype indent on --- 129,149 ---- ! Make sure that you create a few necessary settings in your ~/.vimrc. > ! ! " REQUIRED. This makes vim invoke latex-suite when you open a tex file. filetype plugin on ! ! " IMPORTANT: win32 users will need to have 'shellslash' set so that latex ! " can be called correctly. ! set shellslash ! ! " IMPORTANT: grep will sometimes skip displaying the file name if you ! " search in a singe file. This will confuse latex-suite. Set your grep ! " program to alway generate a file-name. ! set grepprg=grep\ -nH\ $* ! ! " OPTIONAL: This enables automatic indentation as you type. filetype indent on + *************** *** 94,100 **** " all the figure labels. Very useful! set iskeyword+=: ! " IMPORTANT: If you are a win32 user, then the following setting is ! " necessary in order to have latex called correctly from within Vim. ! set shellslash --- 157,161 ---- " all the figure labels. Very useful! set iskeyword+=: ! *************** *** 135,140 **** *latex-macros* ! |ls_3_1| Insert-mode Environment Mappings ! |ls_3_2| Visual-mode Environment Mappings |ls_3_3| Font Mappings |ls_3_4| Section Mappings --- 196,201 ---- *latex-macros* ! |ls_3_1| Environment Mappings ! |ls_3_2| LaTeX command maps |ls_3_3| Font Mappings |ls_3_4| Section Mappings *************** *** 185,194 **** -------------------------------------------------------------------------------- ! Insert-mode Environment Mappings *ls_3_1* *insert-mode-environment-mappings* - |ls_3_1_1| Method 1 - |ls_3_1_2| Method 2 - |ls_3_1_3| Method 3 - |ls_3_1_4| Method 4 These mappings insert LaTeX "environments" such as: > --- 246,260 ---- -------------------------------------------------------------------------------- ! Environment Mappings *ls_3_1* ! *environment-mappings* ! |ls_3_1_1| Insert-mode Mappings ! |ls_3_1_2| Visual-mode Mappings ! |ls_3_1_3| Normal Mode Mappings ! ! Latex-Suite provides a rich set of mappings to insert, enclose and modify LaTeX ! environments. ! ! Insert-mode Mappings *ls_3_1_1* *insert-mode-environment-mappings* These mappings insert LaTeX "environments" such as: > *************** *** 203,207 **** ! Method 1 *ls_3_1_1* *ls-imap-f5* --- 269,273 ---- ! Method 1 *ls_3_1_1_1* *ls-imap-f5* *************** *** 216,220 **** ! Method 2 *ls_3_1_2* If you press <F5> while on a line containing a single word, then latex-suite --- 282,286 ---- ! Method 2 *ls_3_1_1_2* If you press <F5> while on a line containing a single word, then latex-suite *************** *** 222,234 **** ! Method 3 *ls_3_1_3* ! The shifted function keys, <S-F1> to <S-F4>can also be optionally mapped to some ! common environments which you insert most often. The environments mapped to each ! key can also be customized via the g:Tex_HotKeyMappings [|Tex_HotKeyMappings|] ! setting. ! Method 4 *ls_3_1_4* Environments can also be inserted by pressing a 3 capital letter sequence --- 288,300 ---- ! Method 3 *ls_3_1_1_3* ! The shifted function keys, <S-F1> to <S-F4> can also be optionally mapped to ! some common environments which you insert most often. The environments mapped to ! each key can also be customized via the g:Tex_HotKeyMappings ! [|Tex_HotKeyMappings|] setting. ! Method 4 *ls_3_1_1_4* Environments can also be inserted by pressing a 3 capital letter sequence *************** *** 259,264 **** item should give the hint for the map. ! -------------------------------------------------------------------------------- ! Visual-mode Environment Mappings *ls_3_2* *visual-mode-environment-mapings* --- 325,330 ---- item should give the hint for the map. ! ! Visual-mode Mappings *ls_3_1_2* *visual-mode-environment-mapings* *************** *** 284,287 **** --- 350,391 ---- + + Normal Mode Mappings *ls_3_1_3* + *normal-mode-environment-mappings* + + Pressing <S-F5> in normal mode detects which environment the cursor is presently + located in and prompts you to replace it with a new one. The innermost + environment is detected. For example, in the following source: > + \begin{eqnarray} + \begin{array}{ccc} + 2 & 3 & 4 + \end{array} + \end{eqnarray} + if you are located in the middle "2 & 3 & 4" line, then pressing <S-F5> will + prompt you to change the array environment, not the eqnarray environment. In + addition, Latex-Suite will also try to change lines within the environment to be + consistent with the new environment. For example, if the original environment + was an eqnarray environment with a \label command, then changing it to an + eqnarray* environment will delete the \label. + + Pressing <F5> in normal mode has the same effect as pressing <F5> in + insert-mode, namely you will be prompted to choose an environment to insert. + + -------------------------------------------------------------------------------- + LaTeX command maps *ls_3_2* + *latex-command-maps* + + *ls-imap-f7* + Latex-Suite provides two simple mappings <F7> and <S-F7> which work in both + insert and normal mode in an idential manner. Pressing <F7> prompts you with a + list of commands to choose from and then inserts it into the text of the + document. The list of commands is constructed from the g:Tex_PromptedCommands + [|Tex_PromptedCommands|] setting and also from commands which Latex-Suite finds + while scanning custom packages which Latex-Suite finds. See the Package actions + [|package-actions|] section for details on which files are scanned etc. + + In both insert and normal mode <S-F7> will find out if you are presently within + an environment and then prompt you with a list of commands to change it to. + -------------------------------------------------------------------------------- Font Mappings *ls_3_3* *font-maps* *************** *** 296,300 **** 2. next 2 letters are the 2 letters describing the font. ! Example: Typing FEM in insert-mode expands to \textem{<++>}<++>. Just like environment mappings, you can visually select an area and press `sf to --- 400,404 ---- 2. next 2 letters are the 2 letters describing the font. ! Example: Typing FEM in insert-mode expands to \emph{<++>}<++>. Just like environment mappings, you can visually select an area and press `sf to *************** *** 565,571 **** Latex-Suite utilizes a set of macros originally created by Carl Mueller in ! auctex.vim to make inserting all the \left ... \right stuff very easy. The ! following maps are provided: --- 669,690 ---- Latex-Suite utilizes a set of macros originally created by Carl Mueller in ! auctex.vim to make inserting all the \left ... \right stuff very easy and to ! also make some use of the heavily under-utilized <Alt> key. + NOTE: By default, typing Alt-<key> in Vim takes focus to the menu bar if a menu + with the hotkey <key> exists. If in your case, there are conflicts due to + this behavior, you will need to set > + set winaltkeys=no + < in your $VIM/ftplugin/tex.vim in order to use these maps. + + + NOTE: Customizing the maps + -------------------- + If for some reason, you wish to not map the <Alt> keys, (some European + users need to use the <Alt> key to enter diacritics), you can change these + maps to other keys as described in the section Customizing Alt-key maps + [|customize-alt-key-maps|]. + + *************** *** 602,619 **** 2. otherwise insert \cite{}. In visual mode, it will simply enclose the selection in \mathcal{} - NOTE: By default, typing Alt-<key> in Vim takes focus to the menu bar if a menu - with the hotkey <key> exists. If in your case, there are conflicts due to - this behavior, you will need to set > - set winaltkeys=no - < in your $VIM/ftplugin/tex.vim in order to use these maps. - - - NOTE: Customizing the maps - -------------------- - You can also customize the keys which trigger this functionality by - remapping certain <Plug> mappings as described in Customizing Alt-key maps - [|customize-alt-key-maps|]. - - -------------------------------------------------------------------------------- --- 721,724 ---- *************** *** 639,648 **** ! {New} Creates a new (unnamed) buffer in the latex-suite/macros/ directory. ! Use the command :TexMacroNew in non-gui mode. ! {Edit} Opens up the corresponding macro file for editing. Use :TexMacroEdit ! in non-gui mode. ! {Delete} Deletes the corresponding macro. Use the prefixed numbers for fast ! navigation of menus. Use :TexMacroDelete in non-gui mode. {Redraw} Rescans the macros/ directory and refreshes the macros list. --- 744,753 ---- ! {New} Creates a new (unnamed) buffer in the latex-suite/macros/ directory. Use the ! command :TexMacroNew in non-gui mode. ! {Edit} Opens up the corresponding macro file for editing. Use :TexMacroEdit in non-gui ! mode. ! {Delete} Deletes the corresponding macro. Use the prefixed numbers for fast navigation of ! menus. Use :TexMacroDelete in non-gui mode. {Redraw} Rescans the macros/ directory and refreshes the macros list. *************** *** 715,718 **** --- 820,824 ---- For example, the SIUnits package has a custom dictionary. + *latex-package-scanning* If a package detected at startup is found by Latex-Suite in the current directory or in a location specified by the g:Tex_TEXINPUTS [|Tex_TEXINPUTS|] *************** *** 721,725 **** commands and environments which you are prompted with when you press <F5> [|ls-imap-f5|] or <F7> [|ls-imap-f7|] in insert mode. - *latex-package-scanning* In addition, the TeX-Suite > Packages menu also contains the following submenus --- 827,830 ---- *************** *** 1058,1062 **** *latex-compiling* ! |ls_6_1| Setting Compilation rules. |ls_6_2| Specifying which file to compile |ls_6_3| Customizing the compiler output --- 1163,1167 ---- *latex-compiling* ! |ls_6_1| Setting Compilation rules |ls_6_2| Specifying which file to compile |ls_6_3| Customizing the compiler output *************** *** 1089,1093 **** -------------------------------------------------------------------------------- ! Setting Compilation rules. *ls_6_1* *compiler-rules* --- 1194,1198 ---- -------------------------------------------------------------------------------- ! Setting Compilation rules *ls_6_1* *compiler-rules* *************** *** 1315,1319 **** table, figure etc. (an environment). In this case, if a \caption and/or a label is found in the folded region, then those are used to make a more meaningful ! fold-tex, otherwise the second line of the environment is displayed along with the name of the environment. In other words, the following --- 1420,1424 ---- table, figure etc. (an environment). In this case, if a \caption and/or a label is found in the folded region, then those are used to make a more meaningful ! fold-text, otherwise the second line of the environment is displayed along with the name of the environment. In other words, the following *************** *** 1375,1387 **** startpat a line matching this pattern defines the beginning of a fold. endpat a line matching this pattern defines the end of a fold. ! startoff this is the offset from the starting line at which folding will ! actually start ! endoff like startoff, but gives the offset of the actual fold end from the ! line satisfying endpat. startoff and endoff are necessary when the ! folding region does not have a specific end pattern corresponding to ! a start pattern. for example in latex, \begin{section} defines the ! beginning of a section, but its not necessary to have a corresponding ! \end{section} the section is assumed to end 1 line before another ! section starts. startskip A Pattern Which Defines The Beginning Of A "Skipped" Region. --- 1480,1488 ---- startpat a line matching this pattern defines the beginning of a fold. endpat a line matching this pattern defines the end of a fold. ! startoff this is the offset from the starting line at which folding will actually start ! endoff like startoff, but gives the offset of the actual fold end from the line satisfying endpat. startoff and ! endoff are necessary when the folding region does not have a specific end pattern corresponding to a start ! pattern. for example in latex, \begin{section} defines the beginning of a section, but its not necessary to ! have a corresponding \end{section} the section is assumed to end 1 line before another section starts. startskip A Pattern Which Defines The Beginning Of A "Skipped" Region. *************** *** 1393,1404 **** < ! This defines a fold which starts with a line beginning with an \item ! and ending one line before a line beginning with an \item or ! \end{enumerate} etc. ! Then, as long as \item's are not nested things are fine. However, ! once items begin to nest, the fold started by one \item can end ! because of an \item in an \itemize environment within this \item. ! i.e, the following can happen: > \begin{itemize} \item Some text <------- fold will start here --- 1494,1503 ---- < ! This defines a fold which starts with a line beginning with an \item and ending one line before a line ! beginning with an \item or \end{enumerate} etc. ! Then, as long as \item's are not nested things are fine. However, once items begin to nest, the fold ! started by one \item can end because of an \item in an \itemize environment within this \item. i.e, the ! following can happen: > \begin{itemize} \item Some text <------- fold will start here *************** *** 1411,1419 **** < ! Therefore, in order to completely define a folding item which allows ! nesting, we need to also define a "skip" pattern. startskip and end ! skip do that. Leave '' when there is no nesting. ! endskip the pattern which defines the end of the "skip" pattern for nested ! folds. NOTE: Example 1 --- 1510,1516 ---- < ! Therefore, in order to completely define a folding item which allows nesting, we need to also define a ! "skip" pattern. startskip and end skip do that. Leave '' when there is no nesting. ! endskip the pattern which defines the end of the "skip" pattern for nested folds. NOTE: Example 1 *************** *** 1453,1458 **** ! LatexSuite defines set of commands for non-GUI and power users. They are taking ! care about Macros, Templates and Packages. --- 1550,1555 ---- ! This section describes the maps and commands used in Latex-Suite. It also ! describes a way to change the map sequences according to your preference. *************** *** 1479,1487 **** NOTE: To change the IMAP mappings which affect jumping between placeholders, the map statement above has to be placed in your ~/.vimrc. For other mappings ! you can place the map statement in your $VIM/ftplugin/tex.vim file. ! ! The reason for this is that the <C-j> maps are created in ! plugin/imaps.vim, which is sourced as soon as Vim starts before sourcing ! any ftplugin files. --- 1576,1582 ---- NOTE: To change the IMAP mappings which affect jumping between placeholders, the map statement above has to be placed in your ~/.vimrc. For other mappings ! you can place the map statement in your $VIM/ftplugin/tex.vim file. The ! reason for this is that the <C-j> maps are created in plugin/imaps.vim, ! which is sourced as soon as Vim starts before sourcing any ftplugin files. *************** *** 1645,1656 **** +<n> inserts section name <n> logical levels above the last used comand -<n> inserts section name <n> logical levels below the last used comand ! + inserts section name one logical level below the last used command (equal ! to +1). ! ++ inserts section name two logical levels below the last used command (equal ! to +2). ! - inserts section name one logical level over the last used command (equal ! to -1). ! -- inserts section name two logical levels over the last used command (equal ! to -2). --- 1740,1747 ---- +<n> inserts section name <n> logical levels above the last used comand -<n> inserts section name <n> logical levels below the last used comand ! + inserts section name one logical level below the last used command (equal to +1). ! ++ inserts section name two logical levels below the last used command (equal to +2). ! - inserts section name one logical level over the last used command (equal to -1). ! -- inserts section name two logical levels over the last used command (equal to -2). *************** *** 1853,1864 **** *Tex_SectionMaps* *Tex_SectionMenus* ! Setting Link to relevant section Default Value~ ! g:Tex_EnvironmentMaps Environment Mappings 1 ! [|insert-mode-environment-mappings|] ! g:Tex_EnvironmentMenus 1 ! g:Tex_FontMaps Font Mappings [|font-maps|] 1 ! g:Tex_FontMenus 1 ! g:Tex_SectionMaps Section Mappings [|section-mappings|] 1 ! g:Tex_SectionMenus 1 --- 1944,1954 ---- *Tex_SectionMaps* *Tex_SectionMenus* ! Setting Link to relevant section Default Value~ ! g:Tex_EnvironmentMaps Environment Mappings [|insert-mode-environment-mappings|] 1 ! g:Tex_EnvironmentMenus 1 ! g:Tex_FontMaps Font Mappings [|font-maps|] 1 ! g:Tex_FontMenus 1 ! g:Tex_SectionMaps Section Mappings [|section-mappings|] 1 ! g:Tex_SectionMenus 1 *************** *** 2024,2039 **** *Tex_ExplorerHeight* *Tex_ImageDir* ! Setting Explanation Default Value~ ! g:Tex_ViewerCwindowHeight The height of the cwindow which 5 ! displays the list of \labels ! etc. ! g:Tex_ViewerPreviewHeight The height of the preview window 10 ! which shows the context of a ! \label etc. ! g:Tex_ExplorerHeight The height of the explorer 10 ! window which lists the files ! from which to choose an image ! file. ! g:Tex_ImageDir The directory to scan for images '' --- 2114,2123 ---- *Tex_ExplorerHeight* *Tex_ImageDir* ! Setting Explanation Default Value~ ! g:Tex_ViewerCwindowHeight The height of the cwindow which displays the list of \labels etc. 5 ! g:Tex_ViewerPreviewHeight The height of the preview window which shows the context of a \label etc. 10 ! g:Tex_ExplorerHeight The height of the explorer window which lists the files from which to choose an 10 ! image file. ! g:Tex_ImageDir The directory to scan for images '' *************** *** 2081,2091 **** Type String ! Default Value dvi for windows/*nix and ! pdf for mac ! Use this setting to choose the default compilation target. For example, setting ! this to pdf makes Latex-Suite compile a pdf file when you press \l. Make sure ! that a rule has been defined for compiling to this target format as described ! here [|Tex_CompileRule_format|]. --- 2165,2175 ---- Type String ! Default Value dvi for windows/*nix and pdf for mac ! Use this setting to choose the default target format. For example, setting this ! to pdf makes Latex-Suite compile a pdf file when you press \ll and fire up the ! pdf viewer on pressing \lv. Make sure that a rules for compiling and viewing ! have been defined for this target format as described here ! [|Tex_CompileRule_format|] and here [|Tex_ViewRule_format|]. *************** *** 2098,2108 **** ! g:Tex_CompileRule_dvi 'latex ! -interaction=nonstopmode ! $*' g:Tex_CompileRule_ps 'ps2pdf $*' ! g:Tex_CompileRule_pdf 'pdflatex ! -interaction=nonstopmode ! $*' If you desire forward and inverse searching via Latex-Suite, you will need to --- 2182,2188 ---- ! g:Tex_CompileRule_dvi 'latex -interaction=nonstopmode $*' g:Tex_CompileRule_ps 'ps2pdf $*' ! g:Tex_CompileRule_pdf 'pdflatex -interaction=nonstopmode $*' If you desire forward and inverse searching via Latex-Suite, you will need to *************** *** 2354,2368 **** ! Luc Hermitte his variation of Stephen Riehm's bracketing system is used in ! latex-suite. ! Gergely Kontra the clever little JumpFunc() in imaps.vim is due to him. The ! implementation of the templates also borrows from ! mu-template.vim by him. ! Dimitri Antoniou author of ltags and also provided the nice tip about forward ! / reverse search on DVI documents. --- 2434,2446 ---- ! Luc Hermitte his variation of Stephen Riehm's bracketing system is used in latex-suite. ! Gergely Kontra the clever little JumpFunc() in imaps.vim is due to him. The implementation of the ! templates also borrows from mu-template.vim by him. ! Dimitri Antoniou author of ltags and also provided the nice tip about forward / reverse search on ! DVI documents. *************** *** 2373,2382 **** ! Hari Krishna Dara for ExecMap(), the clever little function which makes typing ! visual mode mappings so much easier and error-free. ! Alan G Isac for the comprehensive BibT() function for entering bibtex ! entries. --- 2451,2459 ---- ! Hari Krishna Dara for ExecMap(), the clever little function which makes typing visual mode mappings ! so much easier and error-free. ! Alan G Isac for the comprehensive BibT() function for entering bibtex entries. *************** *** 2384,2389 **** ! Peter Heslin useful discussion and also a lot of bug fixes. the ! %%fakesection in folding.vim. --- 2461,2465 ---- ! Peter Heslin useful discussion and also a lot of bug fixes. the %%fakesection in folding.vim. *************** *** 2410,2415 **** vim:ft=help:fdm=expr ! vim:foldexpr=getline(v\:lnum-1)=~"=\\\\{80,}"?"a1"\:(getline(v\:lnum+1)=~"=\\\\{80,}"?"s1"\:"=") vim:foldtext=v\:folddashes.substitute(getline(v\:foldstart),"\\\\s*\\\\*.*","","") ================================================================================ - --- 2486,2490 ---- vim:ft=help:fdm=expr ! vim:foldexpr=getline(v\:lnum-1)=~'-\\{80}'?'>2'\:getline(v\:lnum-1)=~'=\\{80}'?'>1'\:getline(v\:lnum)=~'=\\{80}'?'0'\:getline(v\:lnum)=~'-\\{80}'?'1'\:'=' vim:foldtext=v\:folddashes.substitute(getline(v\:foldstart),"\\\\s*\\\\*.*","","") ================================================================================ Index: latex-suite.xml =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** latex-suite.xml 20 Jun 2003 06:02:39 -0000 1.4 --- latex-suite.xml 21 Jun 2003 22:13:07 -0000 1.5 *************** *** 56,65 **** <title>Recommended Settings</title> <para> ! Latex-Suite works best if you have the following settings in your ~/.vimrc: ! <programlisting>" this line is responsible for loading latex-suite when a .tex file is ! " opened. filetype plugin on ! " for automatic indentation specific to LaTeX. ! filetype indent on</programlisting> </para> <para> --- 56,77 ---- <title>Recommended Settings</title> <para> ! Make sure that you create a few necessary settings in your ! <literal>~/.vimrc.</literal> ! <programlisting> ! " REQUIRED. This makes vim invoke latex-suite when you open a tex file. filetype plugin on ! ! " IMPORTANT: win32 users will need to have 'shellslash' set so that latex ! " can be called correctly. ! set shellslash ! ! " IMPORTANT: grep will sometimes skip displaying the file name if you ! " search in a singe file. This will confuse latex-suite. Set your grep ! " program to alway generate a file-name. ! set grepprg=grep\ -nH\ $* ! ! " OPTIONAL: This enables automatic indentation as you type. ! filetype indent on ! </programlisting> </para> <para> *************** *** 73,79 **** " all the figure labels. Very useful! set iskeyword+=: ! " IMPORTANT: If you are a win32 user, then the following setting is ! " necessary in order to have latex called correctly from within Vim. ! set shellslash</programlisting> </para> </section> --- 85,89 ---- " all the figure labels. Very useful! set iskeyword+=: ! </programlisting> </para> </section> *************** *** 165,227 **** by &ls;. </para> ! <section id="insert-mode-environment-mappings"> ! <title>Insert-mode Environment Mappings</title> ! <para> These mappings insert LaTeX "environments" such as: ! <programlisting>\begin{center} &ph; \end{center}&ph;</programlisting> ! with the cursor left at the first |placeholder|. There are ! various ways of inserting environments into the source file. If ! the environment is a standard latex environment, then latex suite ! might also include common fields associated with it. ! </para> ! <section id="ls-imap-f5"> ! <title>Method 1</title> ! <para> ! If you press <literal><F5></literal> in the ! insert mode while on an empty line, latex-suite prompts you ! with a list of environments you might want to insert. You can ! either choose one from the list or type in a new environment ! name. This list can be customized via the <link ! linkend="Tex_PromptedEnvironments"><literal>g:Tex_PromptedEnvironments</literal></link> ! setting. </para> ! <para> ! In addition to the <literal>Tex_PromptedEnvironments</literal> ! variable, &ls; also lists envionments found in custom packages as ! described in the section <link linkend="package-actions">Package ! actions.</link> </para> </section> ! <section> ! <title>Method 2</title> ! <para> ! If you press <literal><F5></literal> while on a line ! containing a single word, then latex-suite creates a ! environment of that name. </para> </section> ! <section> ! <title>Method 3</title> ! <para> ! The shifted function keys, <literal><S-F1></literal> to ! <literal><S-F4></literal>can also be optionally mapped ! to some common environments which you insert most often. The ! environments mapped to each key can also be customized via the <link ! linkend="Tex_HotKeyMappings">g:Tex_HotKeyMappings</link> setting. </para> </section> ! <section> ! <title>Method 4</title> ! <para> ! Environments can also be inserted by pressing a 3 capital ! letter sequence starting with an <literal>E</literal>. The following subsection ! describes this in detail. The sequence of 3 letters generally ! tries to follow the following rules: </para> <orderedlist> <listitem> All environment mappings begin with <literal>E</literal> ! </listitem> <listitem> If the environment can be broken up into 2 distinct words, --- 175,242 ---- by &ls;. </para> ! <section id="environment-mappings"> ! <title>Environment Mappings</title> ! &ls; provides a rich set of mappings to insert, enclose and modify ! &latex; environments. ! <section id="insert-mode-environment-mappings"> ! <title>Insert-mode Mappings</title> ! <para> ! These mappings insert LaTeX "environments" such as: ! <programlisting>\begin{center} &ph; \end{center}&ph;</programlisting> ! with the cursor left at the first |placeholder|. There are ! various ways of inserting environments into the source file. If ! the environment is a standard latex environment, then latex suite ! might also include common fields associated with it. </para> ! <section id="ls-imap-f5"> ! <title>Method 1</title> ! <para> ! If you press <literal><F5></literal> in the ! insert mode while on an empty line, latex-suite prompts you ! with a list of environments you might want to insert. You can ! either choose one from the list or type in a new environment ! name. This list can be customized via the <link ! linkend="Tex_PromptedEnvironments"><literal>g:Tex_PromptedEnvironments</literal></link> ! setting. ! </para> ! <para> ! In addition to the <literal>Tex_PromptedEnvironments</literal> ! variable, &ls; also lists envionments found in custom packages as ! described in the section <link linkend="package-actions">Package ! actions.</link> </para> </section> ! <section> ! <title>Method 2</title> ! <para> ! If you press <literal><F5></literal> while on a line ! containing a single word, then latex-suite creates a ! environment of that name. </para> </section> ! <section> ! <title>Method 3</title> ! <para> ! The shifted function keys, <literal><S-F1></literal> to ! <literal><S-F4></literal> can also be optionally mapped ! to some common environments which you insert most often. The ! environments mapped to each key can also be customized via the <link ! linkend="Tex_HotKeyMappings">g:Tex_HotKeyMappings</link> setting. </para> </section> ! <section> ! <title>Method 4</title> ! <para> ! Environments can also be inserted by pressing a 3 capital ! letter sequence starting with an <literal>E</literal>. The following subsection ! describes this in detail. The sequence of 3 letters generally ! tries to follow the following rules: </para> <orderedlist> <listitem> All environment mappings begin with <literal>E</literal> ! </listitem> <listitem> If the environment can be broken up into 2 distinct words, *************** *** 236,284 **** Example: <programlisting>equation (_eq_uation) ---> EEQ</programlisting> ! </listitem> </orderedlist> ! <para> ! Unfortunately there are some environments that cannot be ! split in two words and first two letters in name are ! identical. In this case shortcut is created from E, first and ! last letter. Example: ! <programlisting>quote (_q_uot_e_) ---> EQE quotation (_q_uotatio_n_) ---> EQN</programlisting> ! Of course, not every last one of the environments can follow ! this rule because of ambiguities. In case of doubt, pull down ! the Tex-Environments menu. The menu item should give the hint ! for the map. </para> </section> </section> ! <section id="visual-mode-environment-mapings"> ! <title>Visual-mode Environment Mappings</title> ! <para> ! &ls; provides visual-mode mappings which enclose visually ! selected portions of text in environments. These mappings are ! derived from the corresponding insert-mode environment mappings ! according to the following simple rule: ! <programlisting>ECE --> ,ce</programlisting> ! The rule simply says that the leading <literal>E</literal> is ! converted to <literal>,</literal> and the next 2 letters are ! small case. ! Here <literal>ECE</literal> is the insert-mode map which inserts ! the <literal>\begin{center} ... \end{center}</literal> ! environment. Correspondingly, if you select a portion of text ! visually and press <literal>,ce</literal> while still in visual ! mode, then the selected portion will be enclosed in ! <literal>\begin{center} ... \end{center}</literal>. ! Some of the visual mode mappings are sensitive to whether you ! choose line-wise or character-wise. For example, if you choose a ! word and press <literal>,ce</literal>, then you get ! <literal>\centerline{word}</literal>, whereas if you press ! <literal>,ce</literal> on a line-wise selection, you get: ! <programlisting>\begin{center} line \end{center}</programlisting> </para> </section> <section id="font-maps"> --- 251,350 ---- Example: <programlisting>equation (_eq_uation) ---> EEQ</programlisting> ! </listitem> </orderedlist> ! <para> ! Unfortunately there are some environments that cannot be ! split in two words and first two letters in name are ! identical. In this case shortcut is created from E, first and ! last letter. Example: ! <programlisting>quote (_q_uot_e_) ---> EQE quotation (_q_uotatio_n_) ---> EQN</programlisting> ! Of course, not every last one of the environments can follow ! this rule because of ambiguities. In case of doubt, pull down ! the Tex-Environments menu. The menu item should give the hint ! for the map. </para> </section> </section> ! <section id="visual-mode-environment-mapings"> ! <title>Visual-mode Mappings</title> ! <para> ! &ls; provides visual-mode mappings which enclose visually ! selected portions of text in environments. These mappings are ! derived from the corresponding insert-mode environment mappings ! according to the following simple rule: ! <programlisting>ECE --> ,ce</programlisting> ! The rule simply says that the leading <literal>E</literal> is ! converted to <literal>,</literal> and the next 2 letters are ! small case. ! Here <literal>ECE</literal> is the insert-mode map which inserts ! the <literal>\begin{center} ... \end{center}</literal> ! environment. Correspondingly, if you select a portion of text ! visually and press <literal>,ce</literal> while still in visual ! mode, then the selected portion will be enclosed in ! <literal>\begin{center} ... \end{center}</literal>. ! Some of the visual mode mappings are sensitive to whether you ! choose line-wise or character-wise. For example, if you choose a ! word and press <literal>,ce</literal>, then you get ! <literal>\centerline{word}</literal>, whereas if you press ! <literal>,ce</literal> on a line-wise selection, you get: ! <programlisting>\begin{center} line \end{center}</programlisting> </para> + </section> + <section id="normal-mode-environment-mappings"> + <title>Normal Mode Mappings</title> + <para> + Pressing <literal><S-F5></literal> in normal mode detects which + environment the cursor is presently located in and prompts you to + replace it with a new one. The innermost environment is detected. For + example, in the following source: + <programlisting>\begin{eqnarray} + \begin{array}{ccc} + 2 & 3 & 4 + \end{array} + \end{eqnarray}</programlisting> + if you are located in the middle "2 & 3 & 4" line, then pressing + <literal><S-F5></literal> will prompt you to change the array + environment, not the eqnarray environment. In addition, &ls; will also + try to change lines within the environment to be consistent with the + new environment. For example, if the original environment was an + <literal>eqnarray</literal> environment with a + <literal>\label</literal> command, then changing it to an + <literal>eqnarray*</literal> environment will delete the + <literal>\label</literal>. + </para> + <para> + Pressing <literal><F5></literal> in normal mode has the same + effect as pressing <literal><F5></literal> in insert-mode, + namely you will be prompted to choose an environment to insert. + </para> + </section> + </section> + <section id="latex-command-maps"> + <title>&latex; command maps</title> + <anchor id="ls-imap-f7" /> + <para> + &ls; provides two simple mappings <literal><F7></literal> and + <literal><S-F7></literal> which work in both insert and normal + mode in an idential manner. Pressing <literal><F7></literal> + prompts you with a list of commands to choose from and then inserts it + into the text of the document. The list of commands is constructed from + the <link + linkend="Tex_PromptedCommands"><literal>g:Tex_PromptedCommands</literal></link> + setting and also from commands which &ls; finds while scanning custom + packages which &ls; finds. See the <link + linkend="package-actions">Package actions</link> section for details + on which files are scanned etc. + </para> + <para> + In both insert and normal mode <literal><S-F7></literal> will + find out if you are presently within an environment and then prompt you + with a list of commands to change it to. + </para> </section> <section id="font-maps"> *************** *** 299,303 **** <para> Example: Typing <literal>FEM</literal> in insert-mode expands to ! <literal>\textem{&ph;}&ph;</literal>. </para> <para> --- 365,369 ---- <para> Example: Typing <literal>FEM</literal> in insert-mode expands to ! <literal>\emph{&ph;}&ph;</literal>. </para> <para> *************** *** 598,603 **** &ls; utilizes a set of macros originally created by Carl Mueller in auctex.vim to make inserting all the <literal>\left ... \right</literal> ! stuff very easy. The following maps are provided: </para> <section id="Alt-L"> <title><literal><Alt-L></literal></title> --- 664,691 ---- &ls; utilizes a set of macros originally created by Carl Mueller in auctex.vim to make inserting all the <literal>\left ... \right</literal> ! stuff very easy and to also make some use of the heavily under-utilized ! <literal><Alt></literal> key. </para> + <note> + <para> + By default, typing <literal>Alt-<key></literal> in &vim; takes + focus to the menu bar if a menu with the hotkey + <literal><key></literal> exists. If in your case, there are + conflicts due to this behavior, you will need to set + <programlisting>set winaltkeys=no</programlisting> + in your <literal>$VIM/ftplugin/tex.vim</literal> in order to use these + maps. + </para> + </note> + <note> + <title>Customizing the maps</title> + <para> + If for some reason, you wish to not map the + <literal><Alt></literal> keys, (some European users need to use + the <literal><Alt></literal> key to enter diacritics), you can + change these maps to other keys as described in the section <link + linkend="customize-alt-key-maps">Customizing Alt-key maps</link>. + </para> + </note> <section id="Alt-L"> <title><literal><Alt-L></literal></title> *************** *** 657,679 **** </para> </section> - <note> - <para> - By default, typing <literal>Alt-<key></literal> in &vim; takes - focus to the menu bar if a menu with the hotkey - <literal><key></literal> exists. If in your case, there are - conflicts due to this behavior, you will need to set - <programlisting>set winaltkeys=no</programlisting> - in your <literal>$VIM/ftplugin/tex.vim</literal> in order to use these - maps. - </para> - </note> - <note> - <title>Customizing the maps</title> - <para>You can also customize the keys which trigger this functionality - by remapping certain <literal><Plug></literal> mappings as - described in <link linkend="customize-alt-key-maps">Customizing - Alt-key maps</link>. - </para> - </note> </section> <section id="custom-macros-menu"> --- 745,748 ---- *************** *** 816,819 **** --- 885,889 ---- dictionary. </para> + <anchor id="latex-package-scanning" /> <para> If a package detected at startup is found by &ls; in the current *************** *** 829,833 **** </para> </section> - <anchor id="latex-package-scanning" /> <para> In addition, the <literal>TeX-Suite > Packages</literal> menu also --- 899,902 ---- *************** *** 1258,1262 **** </para> <section id="compiler-rules"> ! <title>Setting Compilation rules.</title> <para> In order to compile &latex; files into various formats, &ls; needs to know --- 1327,1331 ---- </para> <section id="compiler-rules"> ! <title>Setting Compilation rules</title> <para> In order to compile &latex; files into various formats, &ls; needs to know *************** *** 1524,1528 **** table, figure etc. (an environment). In this case, if a \caption and/or a label is found in the folded region, then those are used to make a more ! meaningful fold-tex, otherwise the second line of the environment is displayed along with the name of the environment. In other words, the following </para> --- 1593,1597 ---- table, figure etc. (an environment). In this case, if a \caption and/or a label is found in the folded region, then those are used to make a more ! meaningful fold-text, otherwise the second line of the environment is displayed along with the name of the environment. In other words, the following </para> *************** *** 1715,1720 **** <title>&ls; Commands and Maps</title> <para> ! LatexSuite defines set of commands for non-GUI and power users. They are ! taking care about Macros, Templates and Packages. </para> <section id="latex-suite-maps"> --- 1784,1790 ---- <title>&ls; Commands and Maps</title> <para> ! This section describes the maps and commands used in &ls;. It also ! describes a way to change the map sequences according to your ! preference. </para> <section id="latex-suite-maps"> *************** *** 1744,1753 **** to be placed in your <literal>~/.vimrc</literal>. For other mappings you can place the <literal>map</literal> statement in your ! <literal>$VIM/ftplugin/tex.vim</literal> file. ! </para> ! <para> ! The reason for this is that the <literal><C-j></literal> maps ! are created in <literal>plugin/imaps.vim</literal>, which is sourced ! as soon as &vim; starts before sourcing any ftplugin files. </para> </note> --- 1814,1821 ---- to be placed in your <literal>~/.vimrc</literal>. For other mappings you can place the <literal>map</literal> statement in your ! <literal>$VIM/ftplugin/tex.vim</literal> file. The reason for this is ! that the <literal><C-j></literal> maps are created in ! <literal>plugin/imaps.vim</literal>, which is sourced as soon as &vim; ! starts before sourcing any ftplugin files. </para> </note> *************** *** 2594,2602 **** </informaltable> <para> ! Use this setting to choose the default compilation target. For example, ! setting this to <literal>pdf</literal> makes &ls; compile a pdf file when ! you press <literal>\l</literal>. Make sure that a rule has been defined ! for compiling to this target format as described <link ! linkend="Tex_CompileRule_format">here</link>. </para> </section> --- 2662,2673 ---- </informaltable> <para> ! Use this setting to choose the default target format. For example, ! setting this to <literal>pdf</literal> makes &ls; compile a pdf file ! when you press <literal>\ll</literal> and fire up the ! <literal>pdf</literal> viewer on pressing <literal>\lv</literal>. Make ! sure that a rules for compiling and viewing have been defined for this ! target format as described <li... [truncated message content] |
From: <sri...@us...> - 2003-06-20 06:11:58
|
Update of /cvsroot/vim-latex/vimfiles/ftplugin/tex In directory sc8-pr-cvs1:/tmp/cvs-serv30555 Modified Files: texviewer.vim Log Message: Bug: A recent change made in order to recognize strings such as \psfig{file=} for completion resulted in not completing \ref{eqn: ! (Sorry) Fix: Change the regexp again. Change: Use redraw! for helping terminal users. and also do not use <silent> unless we have gui running. Index: texviewer.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/tex/texviewer.vim,v retrieving revision 1.25 retrieving revision 1.26 diff -C2 -d -r1.25 -r1.26 *** texviewer.vim 17 Jun 2003 17:26:46 -0000 1.25 --- texviewer.vim 20 Jun 2003 06:11:54 -0000 1.26 *************** *** 19,23 **** inoremap <silent> <Plug>Tex_Completion <Esc>:call Tex_completion("default","text")<CR> if !hasmapto('<Plug>Tex_Completion', 'i') ! imap <buffer> <silent> <F9> <Plug>Tex_Completion endif endfunction --- 19,27 ---- inoremap <silent> <Plug>Tex_Completion <Esc>:call Tex_completion("default","text")<CR> if !hasmapto('<Plug>Tex_Completion', 'i') ! if has('gui_running') ! imap <buffer> <silent> <F9> <Plug>Tex_Completion ! else ! imap <buffer> <F9> <Plug>Tex_Completion ! endif endif endfunction *************** *** 80,84 **** " s:type = 'psfig' " s:typeoption = '[option=value]' ! let pattern = '.*\\\(\w\{-}\)\(\[.\{-}\]\)\?{\(\a\+=\)\?$' if s:curline =~ pattern let s:type = substitute(s:curline, pattern, '\1', 'e') --- 84,88 ---- " s:type = 'psfig' " s:typeoption = '[option=value]' ! let pattern = '.*\\\(\w\{-}\)\(\[.\{-}\]\)\?{\(\S\+\)\?$' if s:curline =~ pattern let s:type = substitute(s:curline, pattern, '\1', 'e') *************** *** 93,96 **** --- 97,101 ---- call Tex_Debug("silent! grep! '\\label{".s:prefix."' ".s:search_directory.'*.tex', 'view') exe "silent! grep! '\\label{".s:prefix."' ".s:search_directory.'*.tex' + redraw! call <SID>Tex_c_window_setup() *************** *** 107,110 **** --- 112,116 ---- call Tex_Debug('calling Tex_GrepForBibItems', 'bib') call Tex_GrepForBibItems(s:prefix) + redraw! call <SID>Tex_c_window_setup() endif |
From: <sri...@us...> - 2003-06-20 06:02:42
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv29752 Modified Files: latex-suite.txt latex-suite.xml Log Message: A bit more explanation about how to change the maps from default settings. Index: latex-suite.txt =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.txt,v retrieving revision 1.26 retrieving revision 1.27 diff -C2 -d -r1.26 -r1.27 *** latex-suite.txt 18 Jun 2003 18:54:30 -0000 1.26 --- latex-suite.txt 20 Jun 2003 06:02:39 -0000 1.27 *************** *** 39,44 **** |ls_3_11| Custom Macros |ls_4| Package Handling ! |ls_4_1| Custom Packages ! |ls_4_2| Supporting a package |ls_5| Latex Completion |ls_5_1| Latex-Suite \cite completion --- 39,46 ---- |ls_3_11| Custom Macros |ls_4| Package Handling ! |ls_4_1| Inserting package commands ! |ls_4_2| Actions taken for supported packages ! |ls_4_3| Automatic Package detection ! |ls_4_4| Writing supporting for a package |ls_5| Latex Completion |ls_5_1| Latex-Suite \cite completion *************** *** 201,210 **** ! Method 1 *ls_3_1_1* If you press <F5> in the insert mode while on an empty line, latex-suite prompts you with a list of environments you might want to insert. You can either choose ! one from the list or type in a new environment name. This list can be ! customized. See the 'Macros' section of the |texrc| file for details. --- 203,217 ---- ! Method 1 *ls_3_1_1* ! *ls-imap-f5* If you press <F5> in the insert mode while on an empty line, latex-suite prompts you with a list of environments you might want to insert. You can either choose ! one from the list or type in a new environment name. This list can be customized ! via the g:Tex_PromptedEnvironments [|Tex_PromptedEnvironments|] setting. ! ! In addition to the Tex_PromptedEnvironments variable, Latex-Suite also lists ! envionments found in custom packages as described in the section Package ! actions. [|package-actions|] *************** *** 219,223 **** The shifted function keys, <S-F1> to <S-F4>can also be optionally mapped to some common environments which you insert most often. The environments mapped to each ! key can also be customized. See the |texrc| file for details. --- 226,231 ---- The shifted function keys, <S-F1> to <S-F4>can also be optionally mapped to some common environments which you insert most often. The environments mapped to each ! key can also be customized via the g:Tex_HotKeyMappings [|Tex_HotKeyMappings|] ! setting. *************** *** 552,558 **** Alt Key Macros *ls_3_10* *bracketing-macros* ! |ls_3_10_1| <Alt-M> ! |ls_3_10_2| <Alt-C> ! |ls_3_10_3| <Alt-L> Latex-Suite utilizes a set of macros originally created by Carl Mueller in --- 560,566 ---- Alt Key Macros *ls_3_10* *bracketing-macros* ! |ls_3_10_1| <Alt-L> ! |ls_3_10_2| <Alt-M> ! |ls_3_10_3| <Alt-C> Latex-Suite utilizes a set of macros originally created by Carl Mueller in *************** *** 562,583 **** ! <Alt-M> *ls_3_10_1* *Alt-M* ! ! This insert-mode mapping encloses the previous character in \mathbf{}. ! ! ! <Alt-C> *ls_3_10_2* *Alt-C* ! ! In insert mode, this key is polymorphic as follows: ! ! ! 1. If the previous character is a letter or number, then capitalize it and ! enclose it in \mathcal{}. ! ! 2. otherwise insert \cite{}. ! In visual mode, it will simply enclose the selection in \mathcal{} ! ! ! <Alt-L> *ls_3_10_3* *Alt-L* This is a polymorphic insert-mode mapping which expands to one of the following --- 570,574 ---- ! <Alt-L> *ls_3_10_1* *Alt-L* This is a polymorphic insert-mode mapping which expands to one of the following *************** *** 594,601 **** If the character before the cursor is none of the above, then it will simply insert a \label{<++>}<++>. NOTE: By default, typing Alt-<key> in Vim takes focus to the menu bar if a menu with the hotkey <key> exists. If in your case, there are conflicts due to this behavior, you will need to set > ! set nowinaltkeys < in your $VIM/ftplugin/tex.vim in order to use these maps. --- 585,609 ---- If the character before the cursor is none of the above, then it will simply insert a \label{<++>}<++>. + + + <Alt-M> *ls_3_10_2* *Alt-M* + + This insert-mode mapping encloses the previous character in \mathbf{}. + + + <Alt-C> *ls_3_10_3* *Alt-C* + + In insert mode, this key is polymorphic as follows: + + + 1. If the previous character is a letter or number, then capitalize it and + enclose it in \mathcal{}. + + 2. otherwise insert \cite{}. + In visual mode, it will simply enclose the selection in \mathcal{} NOTE: By default, typing Alt-<key> in Vim takes focus to the menu bar if a menu with the hotkey <key> exists. If in your case, there are conflicts due to this behavior, you will need to set > ! set winaltkeys=no < in your $VIM/ftplugin/tex.vim in order to use these maps. *************** *** 604,609 **** -------------------- You can also customize the keys which trigger this functionality by ! remapping certain <Plug> mappings as described in ! |customizing-latex-suite-mappings|. --- 612,617 ---- -------------------- You can also customize the keys which trigger this functionality by ! remapping certain <Plug> mappings as described in Customizing Alt-key maps ! [|customize-alt-key-maps|]. *************** *** 643,651 **** *latex-packages* ! |ls_4_1| Custom Packages ! |ls_4_2| Supporting a package ! This functionality is avaiable via the Tex-Packages menu. When you first invoke Latex-Suite, it scans the --- 651,668 ---- *latex-packages* ! |ls_4_1| Inserting package commands ! |ls_4_2| Actions taken for supported packages ! |ls_4_3| Automatic Package detection ! |ls_4_4| Writing supporting for a package ! Latex-Suite has a lot of functionality written to ease working with packages. ! Packages here refers to files which you include into the LaTeX document using ! the \usepackage command. ! ! ! -------------------------------------------------------------------------------- ! Inserting package commands *ls_4_1* ! *inserting-packages* When you first invoke Latex-Suite, it scans the *************** *** 665,670 **** containing a single word will construct a \usepackage line from that word. ! Once a \usepackage line has been constructed in one of the above methods, if ! possible, the following sub-menus will be created --- 682,695 ---- containing a single word will construct a \usepackage line from that word. ! Once you have inserted a \usepackage line, for supported packages, you can use ! the Options and Commands menus described in the next section ! [|package-actions|]. ! ! -------------------------------------------------------------------------------- ! Actions taken for supported packages *ls_4_2* ! *package-actions* ! ! Once a \usepackage line has been constructed using one of the methods described ! in the previous section, if possible, the following sub-menus will be created *************** *** 672,677 **** TeX-Suite > Packages > <package> Commands ! where <package> is the package you just inserted. In addition to creating these sub-meuns, Latex-Suite will also scan the $VIM/ftplugin/latex-suite/dictionaries directory and if a dictionary file --- 697,710 ---- TeX-Suite > Packages > <package> Commands ! where <package> is the package you just inserted. You can use these menus to ! insert commands, environments and options which Latex-Suite recognizes as ! belonging to this package. + NOTE: While inserting an option, you need to position yourself in the + appropritate place in the document, most commonly inside the square braces + in the \usepackage[]{packname} command. Latex-Suite will not navigate to + that location. + + In addition to creating these sub-meuns, Latex-Suite will also scan the $VIM/ftplugin/latex-suite/dictionaries directory and if a dictionary file *************** *** 682,694 **** For example, the SIUnits package has a custom dictionary. *latex-package-scanning* - Whenever Latex-Suite begins editing a new LaTeX file, it scans it for - \usepackage{name} lines, and if a supported package is found, then it will - create sub-menus and add to the 'dict' setting as described above. - - If a master-file [|latex-master-file|] has been specified, then it will scan - that file instead of the current file. See the section Custom Packages - [|custom-packages|] to see which files Latex-Suite will scan in more detail. - In addition, the TeX-Suite > Packages menu also contains the following submenus --- 715,725 ---- For example, the SIUnits package has a custom dictionary. + If a package detected at startup is found by Latex-Suite in the current + directory or in a location specified by the g:Tex_TEXINPUTS [|Tex_TEXINPUTS|] + variable, Latex-Suite will scan the package for \newenvironment and newcommand + lines and also append any commands and environments found to the list of + commands and environments which you are prompted with when you press <F5> + [|ls-imap-f5|] or <F7> [|ls-imap-f7|] in insert mode. *latex-package-scanning* In addition, the TeX-Suite > Packages menu also contains the following submenus *************** *** 707,711 **** -------------------------------------------------------------------------------- ! Custom Packages *ls_4_1* *custom-packages* --- 738,759 ---- -------------------------------------------------------------------------------- ! Automatic Package detection *ls_4_3* ! *automatic-package-detection* ! |ls_4_3_1| Custom Packages ! ! Whenever Latex-Suite begins editing a new LaTeX file, it scans it for ! \usepackage{name} lines, and if a supported package is found, then it will ! create sub-menus and add to the 'dict' setting as described above. ! ! If a master-file [|latex-master-file|] has been specified, then it will scan ! that file instead of the current file. See the section Custom Packages ! [|custom-packages|] to see which files Latex-Suite will scan in more detail. ! ! For all the packages detected in this manner, Latex-Suite will take certain ! actions as described in the section package support. [|package-actions|]. ! ! ! ! Custom Packages *ls_4_3_1* *custom-packages* *************** *** 732,737 **** Example: > ! let g:Tex_TEXINPUTS = '~/texmf/mypackages/**;./**' ! Note that directories are delimited by ';'. NOTE: The present directory '.' is always searched. You need not incude that in --- 780,786 ---- Example: > ! let g:Tex_TEXINPUTS = '~/texmf/mypackages/**,./**' ! The ** indicates that all directories below the directory ~/texmf/mypackages and ! ./ are to be scanned for custom packages. NOTE: The present directory '.' is always searched. You need not incude that in *************** *** 741,748 **** -------------------------------------------------------------------------------- ! Supporting a package *ls_4_2* *supporting-packages* ! |ls_4_2_1| g:Tex_package_option_<package> ! |ls_4_2_2| g:Tex_package_<package> Supporting a package is easy and consists of writing a vim script with the same --- 790,797 ---- -------------------------------------------------------------------------------- ! Writing supporting for a package *ls_4_4* *supporting-packages* ! |ls_4_4_1| g:Tex_package_option_<package> ! |ls_4_4_2| g:Tex_package_<package> Supporting a package is easy and consists of writing a vim script with the same *************** *** 753,757 **** ! g:Tex_package_option_<package> *ls_4_2_1* This setting is a string containing a comma seperated list of options supported --- 802,806 ---- ! g:Tex_package_option_<package> *ls_4_4_1* This setting is a string containing a comma seperated list of options supported *************** *** 765,769 **** ! g:Tex_package_<package> *ls_4_2_2* > --- 814,818 ---- ! g:Tex_package_<package> *ls_4_4_2* > *************** *** 820,871 **** This module provides an easy way to insert references to labels and ! bibliographic entries. Suppose you want to refer to an equation which is ! labelled as "eqn:eq-1" using the \label{eqn:eq-1} command. Somewhere in the ! text, you write "\ref{" with the cursor after the {. Now if you press <F9>, ! Latex-suite will try to search through all the .tex files in the present ! directory for lines beginning with "\label{". It will provide you with a list of ! all such matches in two small windows. > ! +========================================================+ ! | I want to insert a reference to equation 1. Therefore | ! | I will write \ref{ | ! | | ! | | ! | | ! | | ! | | ! +--------------------------------------------------------+ ! +file1.tex + ! +========================================================+ ! |file1.tex|100| \label{eqn:eq-1} | ! |file1.tex|110| \label{eqn:eq-2} | ! |file2.tex|178| \label{tab:table1} | ! +--------------------------------------------------------+ ! +[Error List] + ! +========================================================+ ! |\begin{equation} | ! | e^{j*pi} + 1 = 0 \label{eqn:eq-1} | ! |\end{equation} | ! |And there was some text after this. I dont remember | ! +--------------------------------------------------------+ ! +file1.tex [Preview] + ! +========================================================+ ! The first window (shown as "[Error List]" above) is a |cwindow| containing a ! list of matches and you will be left in it. The window beneath it is a ! |preview-window| showing the context of the match. When you move up and down in ! the "[Error List]" window, the preview window will be scrolled to keep in sync ! with the label. Pressing the "J" and "K" keys in the "[Error List]" window ! scrolls the preview window enabling you to see more context if you desire. After ! positioning yourself on a label which you want to insert, press CR>. This will ! automatically close all the new windows, take you back to the file being edited ! and insert the chosen label in place. Pressing "q" in the "[Error List]" window ! closes all windows without inserting anything. ! As can be seen above, the matches include everything which begins with \label. ! If you have the habit of prefixing all equation labels with "eqn:" or something ! similar, then you can restrict the matches to only equations by first typing ! "\ref{eqn:" and then pressing <F9>. This only brings up matches starting with ! "\label{eqn:" thus allowing you to skip table and figure labels. The same mechanism also works with citations by pressing <F9> after typing --- 869,944 ---- This module provides an easy way to insert references to labels and ! bibliographic entries. ! ! Consider the situation where you are editing a file with two equations labelled ! eqn:euler and eqn:einstein. Now you want to insert a reference to one of these ! equations. To do this, you type the \ref{eqn:} command and with the cursor ! placed after eqn:, press <F9>. This will bring up two new windows beneath the ! main window you were working in as shown in the figure below. > ! ! 7 ! 8 These are a couple of equations: ! 9 +-- 4 lines: eqnarray (eqn:euler) : e^{j\pi} + 1 &=& 0--------------- ! 13 +-- 4 lines: equation (eqn:einstein) : E = m c^2--------------------- ! 17 ! 18 These are a couple of figures: ! 19 +-- 7 lines: figure (fig:monkeys) : Monkeys can Type------------------- ! 26 +-- 7 lines: figure (fig:shakespeare) : Shakespeare could not type----- ! 33 ! 34 This is a reference to \ref{eqn:}<++> ! 35 ! 36 ! 37 \end{document} ! 38 ! ~ ! ~ ! ~ ! ~ ! ~ ! ~ ! ~ ! newfile.tex 34,32 Bot ! newfile.tex|11| \label{eqn:euler} ! newfile.tex|15| \label{eqn:einstein} ! ~ ! ~ ! ~ ! [Error List] 1,1 All ! 7 ! 8 These are a couple of equations: ! 9 \begin{eqnarray} ! 10 e^{j\pi} + 1 &=& 0 ! 11 \label{eqn:euler} ! 12 \end{eqnarray} ! 13 \begin{equation} ! 14 E = m c^2 ! 15 \label{eqn:einstein} ! 16 \end{equation} ! newfile.tex [Preview] 11,3 21% ! ! The first window (shown as [ErrorList] above) is a |cwindow| containing a list ! of possible matches for the reference. The cursor will be located in the first ! line of this window. The bottom window is a preview-window showing the context ! of the \label. Moving around in the [ErrorList] window automatically scrolls the ! preview window so as to always keep showing the context of the \label being ! viewed in the [ErrorList] window. You can also press J and K in the [ErrorList] ! window to scroll the preview window up and down. ! To insert one of the labels, simply position the cursor in the correct line in ! the [ErrorList] window and press <enter>. This will immediately close the two ! newly opened windows, get back to the correct location in the original file ! being edited and insert the label into the \ref command. ! ! If you notice carefully in the example above, the [ErrorList] window only showed ! the matches for the equations and did not list any of the figure labels. This is ! because we pressed <F9> after \ref{eqn: instead of simply after \ref{. This ! caused Latex-Suite to search only for those labels which started with the string ! eqn:. If you had pressed <F9> after a \ref{, you would have been shown matches ! from all labels, not just those starting with eqn:. ! ! Thus prefixing all your labels with eqn:, fig:, tab: etc. depending on what you ! are labelling will lead to an easier time completing references. The same mechanism also works with citations by pressing <F9> after typing *************** *** 1387,1423 **** Latex-Suite Maps *ls_9_1* *latex-suite-maps* ! |ls_9_1_1| <Plug>IMAP_JumpForward ! |ls_9_1_2| <Plug>IMAP_JumpBack ! |ls_9_1_3| <Plug>IMAP_DeleteAndJumpForward ! Normal usage of Latex-Suite will typically involve using a fairly large number ! of mappings. It should be noted that many of the mappings can be changed to a ! different set of characters according to your particular needs. - <Plug>IMAP_JumpForward *ls_9_1_1* - *Plug_IMAPJumpForward* ! Default Key assigned : <Ctrl-J> - This map takes you to the location of the next place-holder [|place-holders|]. ! <Plug>IMAP_JumpBack *ls_9_1_2* ! *Plug_IMAPJumpBack* ! Default Key assigned : NONE ! This map takes you to the previous place-holder [|place-holders|]. ! <Plug>IMAP_DeleteAndJumpForward *ls_9_1_3* ! *Plug_IMAP_DeleteAndJumpForward* ! Default Key assigned : NONE ! This map deletes the presently selected place-holder irrespective of whether the ! present placeholder is empty or not and ignoring the value of place-holder ! settings like g:Imap_DeleteEmptyPlaceHolders [|Imap_DeleteEmptyPlaceHolders|] ! and g:Imap_StickyPlaceHolders [|Imap_StickyPlaceHolders|] -------------------------------------------------------------------------------- --- 1460,1540 ---- Latex-Suite Maps *ls_9_1* *latex-suite-maps* ! |ls_9_1_1| IMAP mappings ! |ls_9_1_2| Alt-Key mappings ! *remapping-latex-suite-keys* ! Most of the mappings used in Latex-Suite can be mapped to a different key ! combination to suit your particular needs. An example best explains the ! procedure for doing this. Suppose you want to remap the <C-j> key which ! Latex-Suite (actually imaps.vim) uses to jump to the next placeholder. To do ! this, you first need to find out which <Plug> mapping <C-j> is derived from. You ! will need to look at the relevant section of this manual to do this. For ! example, the section IMAP mappings [|customize-imap-maps|] has the information ! that the <C-j> key is derived from <Plug>IMAP_JumpForward. Therefore to remap ! the <C-j> key to say <C-space>, you will need to put a statement like the ! following in your ~/.vimrc. > ! imap <C-space> <Plug>IMAP_JumpForward ! NOTE: To change the IMAP mappings which affect jumping between placeholders, the ! map statement above has to be placed in your ~/.vimrc. For other mappings ! you can place the map statement in your $VIM/ftplugin/tex.vim file. ! ! The reason for this is that the <C-j> maps are created in ! plugin/imaps.vim, which is sourced as soon as Vim starts before sourcing ! any ftplugin files. ! ! + IMAP mappings *ls_9_1_1* + *customize-imap-maps* ! These mappings are utlilized for jumping between placeholders as described here ! [|place-holders|]. See the parent section [|latex-suite-maps|] to find out how ! to use this information to change the default maps. ! *Plug_IMAP_JumpForward* ! *Plug_IMAP_JumpBack* ! *Plug_IMAP_DeleteAndJumpForward* ! *Plug_IMAP_DeleteAndJumBack* ! Plug map Default Key~ ! <Plug>IMAP_JumpForward <C-j> ! <Plug>IMAP_JumpBack (none) ! <Plug>IMAP_DeleteAndJumpForward (none) ! <Plug>IMAP_DeleteAndJumpBack (none) ! <Plug>IMAP_JumpForward takes you to the location of the next place-holder ! [|place-holders|]. + <Plug>IMAP_JumpBack takes you to the previous place-holder [|place-holders|]. ! <Plug>IMAP_DeleteAndJumpForward deletes the presently selected place-holder and ! jumps to the next place-holder irrespective of whether the present placeholder ! is empty or not and ignoring the value of place-holder settings like ! g:Imap_DeleteEmptyPlaceHolders [|Imap_DeleteEmptyPlaceHolders|] and ! g:Imap_StickyPlaceHolders [|Imap_StickyPlaceHolders|] ! <Plug>IMAP_DeleteAndJumpBack deletes the presently selected place-holder and ! jumps to the previous place-holder irrespective of whether the present ! placeholder is empty or not and ignoring the value of place-holder settings like ! g:Imap_DeleteEmptyPlaceHolders [|Imap_DeleteEmptyPlaceHolders|] and ! g:Imap_StickyPlaceHolders [|Imap_StickyPlaceHolders|] ! ! Alt-Key mappings *ls_9_1_2* ! *customize-alt-key-maps* ! ! These mappings are are described in the section Alt key macros ! [|bracketing-macros|]. See the parent section [|remapping-latex-suite-keys|] to ! see how to use the following information to remap keys. ! ! *Plug_Tex_MathBF* ! *Plug_Tex_MathCal* ! *Plug_Tex_LeftRight* ! Plug Mapping Default Key~ ! <Plug>Tex_MathBF <Alt-B> ! <Plug>Tex_MathCal <Alt-C> ! <Plug>Tex_LeftRight <Alt-L> -------------------------------------------------------------------------------- Index: latex-suite.xml =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** latex-suite.xml 18 Jun 2003 18:54:30 -0000 1.3 --- latex-suite.xml 20 Jun 2003 06:02:39 -0000 1.4 *************** *** 176,180 **** might also include common fields associated with it. </para> ! <section> <title>Method 1</title> <para> --- 176,180 ---- might also include common fields associated with it. </para> ! <section id="ls-imap-f5"> <title>Method 1</title> <para> *************** *** 183,188 **** with a list of environments you might want to insert. You can either choose one from the list or type in a new environment ! name. This list can be customized. See the 'Macros' section ! of the |texrc| file for details. </para> </section> --- 183,195 ---- with a list of environments you might want to insert. You can either choose one from the list or type in a new environment ! name. This list can be customized via the <link ! linkend="Tex_PromptedEnvironments"><literal>g:Tex_PromptedEnvironments</literal></link> ! setting. ! </para> ! <para> ! In addition to the <literal>Tex_PromptedEnvironments</literal> ! variable, &ls; also lists envionments found in custom packages as ! described in the section <link linkend="package-actions">Package ! actions.</link> </para> </section> *************** *** 201,206 **** <literal><S-F4></literal>can also be optionally mapped to some common environments which you insert most often. The ! environments mapped to each key can also be customized. See ! the |texrc| file for details. </para> </section> --- 208,213 ---- <literal><S-F4></literal>can also be optionally mapped to some common environments which you insert most often. The ! environments mapped to each key can also be customized via the <link ! linkend="Tex_HotKeyMappings">g:Tex_HotKeyMappings</link> setting. </para> </section> *************** *** 593,622 **** stuff very easy. The following maps are provided: </para> - <section id="Alt-M"> - <title><literal><Alt-M></literal></title> - <para> - This insert-mode mapping encloses the previous character in - <literal>\mathbf{}</literal>. - </para> - </section> - <section id="Alt-C"> - <title><literal><Alt-C></literal></title> - <para> - In insert mode, this key is polymorphic as follows: - </para> - <orderedlist> - <listitem> - If the previous character is a letter or number, then capitalize it and - enclose it in <literal>\mathcal{}</literal>. - </listitem> - <listitem> - otherwise insert <literal>\cite{}</literal>. - </listitem> - </orderedlist> - <para> - In visual mode, it will simply enclose the selection in - <literal>\mathcal{}</literal> - </para> - </section> <section id="Alt-L"> <title><literal><Alt-L></literal></title> --- 600,603 ---- *************** *** 650,653 **** --- 631,660 ---- </para> </section> + <section id="Alt-M"> + <title><literal><Alt-M></literal></title> + <para> + This insert-mode mapping encloses the previous character in + <literal>\mathbf{}</literal>. + </para> + </section> + <section id="Alt-C"> + <title><literal><Alt-C></literal></title> + <para> + In insert mode, this key is polymorphic as follows: + </para> + <orderedlist> + <listitem> + If the previous character is a letter or number, then capitalize it and + enclose it in <literal>\mathcal{}</literal>. + </listitem> + <listitem> + otherwise insert <literal>\cite{}</literal>. + </listitem> + </orderedlist> + <para> + In visual mode, it will simply enclose the selection in + <literal>\mathcal{}</literal> + </para> + </section> <note> <para> *************** *** 656,660 **** <literal><key></literal> exists. If in your case, there are conflicts due to this behavior, you will need to set ! <programlisting>set nowinaltkeys</programlisting> in your <literal>$VIM/ftplugin/tex.vim</literal> in order to use these maps. --- 663,667 ---- <literal><key></literal> exists. If in your case, there are conflicts due to this behavior, you will need to set ! <programlisting>set winaltkeys=no</programlisting> in your <literal>$VIM/ftplugin/tex.vim</literal> in order to use these maps. *************** *** 663,669 **** <note> <title>Customizing the maps</title> ! <para>You can also customize the keys which trigger this functionality by ! remapping certain <literal><Plug></literal> mappings as described ! in |customizing-latex-suite-mappings|.</para> </note> </section> --- 670,678 ---- <note> <title>Customizing the maps</title> ! <para>You can also customize the keys which trigger this functionality ! by remapping certain <literal><Plug></literal> mappings as ! described in <link linkend="customize-alt-key-maps">Customizing ! Alt-key maps</link>. ! </para> </note> </section> *************** *** 736,769 **** <title>Package Handling</title> <para> ! This functionality is avaiable via the Tex-Packages menu. ! </para> ! <para> ! When you first invoke &ls;, it scans the ! <literal>$VIM/ftplugin/latex-suite/packages</literal> directory for ! package script files and creates a menu from all the files found there. ! This menu is created under <literal>TeX-Suite > Packages > ! Supported</literal>. This menu contains a list of packages "supported" ! by &ls;. When you choose one of the packages from this menu (for example ! the <literal>amsmath</literal> package), then a line of ! the form ! <programlisting>\usepackage[&ph;]{amsmath}&ph;</programlisting> ! will be inserted into the current file. ! </para> ! <para> ! The <literal>\usepackage</literal> line can also be inserted in an easy ! manner in the current file by pressing <literal><F5></literal> ! while in the preamble of the current document. This will set up a prompt ! from the supported packages and ask you to choose from one of them. If ! you do not find the package you want to insert in the list, you can type ! in a package-name and it will use that. Pressing ! <literal><F5></literal> in the preamble on a line containing a ! single word will construct a <literal>\usepackage</literal> line from ! that word. ! </para> ! <para> ! Once a <literal>\usepackage</literal> line has been constructed in one ! of the above methods, if possible, the following sub-menus will be ! created </para> <simplelist> <member><literal>TeX-Suite > Packages > <package> Options</literal></member> --- 745,790 ---- <title>Package Handling</title> <para> ! &ls; has a lot of functionality written to ease working with packages. ! Packages here refers to files which you include into the &latex; ! document using the <literal>\usepackage</literal> command. </para> + <section id="inserting-packages"> + <title>Inserting package commands</title> + <para> + When you first invoke &ls;, it scans the + <literal>$VIM/ftplugin/latex-suite/packages</literal> directory for + package script files and creates a menu from all the files found there. + This menu is created under <literal>TeX-Suite > Packages > + Supported</literal>. This menu contains a list of packages "supported" + by &ls;. When you choose one of the packages from this menu (for example + the <literal>amsmath</literal> package), then a line of + the form + <programlisting>\usepackage[&ph;]{amsmath}&ph;</programlisting> + will be inserted into the current file. + </para> + <para> + The <literal>\usepackage</literal> line can also be inserted in an easy + manner in the current file by pressing <literal><F5></literal> + while in the preamble of the current document. This will set up a prompt + from the supported packages and ask you to choose from one of them. If + you do not find the package you want to insert in the list, you can type + in a package-name and it will use that. Pressing + <literal><F5></literal> in the preamble on a line containing a + single word will construct a <literal>\usepackage</literal> line from + that word. + </para> + <para> + Once you have inserted a <literal>\usepackage</literal> line, for + supported packages, you can use the Options and Commands menus + described in the <link linkend="package-actions">next section</link>. + </para> + </section> + <section id="package-actions"> + <title>Actions taken for supported packages</title> + <para> + Once a <literal>\usepackage</literal> line has been constructed using + one of the methods described in the previous section, if possible, the + following sub-menus will be created + </para> <simplelist> <member><literal>TeX-Suite > Packages > <package> Options</literal></member> *************** *** 772,803 **** <para> where <literal><package></literal> is the package you just ! inserted. </para> ! <para> ! In addition to creating these sub-meuns, &ls; will also scan the ! <literal>$VIM/ftplugin/latex-suite/dictionaries</literal> directory and ! if a dictionary file corresponding to the package file is found, then ! it will add the file to the <literal>'dict'</literal> setting in &vim; ! so you can use the <literal><C-X><C-K></literal> command to ! complete words from that file. ! </para> ! <para> ! For example, the <literal>SIUnits</literal> package has a custom ! dictionary. ! </para> <anchor id="latex-package-scanning" /> <para> - Whenever &ls; begins editing a new &latex; file, it scans it for - <literal>\usepackage{name}</literal> lines, and if a supported package - is found, then it will create sub-menus and add to the - <literal>'dict'</literal> setting as described above. - </para> - <para> - If a <link linkend="latex-master-file">master-file</link> has been specified, - then it will scan that file instead of the current file. See the section - <link linkend="custom-packages">Custom Packages</link> - to see which files &ls; will scan in more detail. - </para> - <para> In addition, the <literal>TeX-Suite > Packages</literal> menu also contains the following submenus --- 793,834 ---- <para> where <literal><package></literal> is the package you just ! inserted. You can use these menus to insert commands, environments and ! options which &ls; recognizes as belonging to this package. </para> ! <note> ! <para> ! While inserting an option, you need to position yourself in the ! appropritate place in the document, most commonly inside the square ! braces in the <literal>\usepackage[]{packname}</literal> command. &ls; ! will not navigate to that location. ! </para> ! </note> ! <para> ! In addition to creating these sub-meuns, &ls; will also scan the ! <literal>$VIM/ftplugin/latex-suite/dictionaries</literal> directory and ! if a dictionary file corresponding to the package file is found, then ! it will add the file to the <literal>'dict'</literal> setting in &vim; ! so you can use the <literal><C-X><C-K></literal> command to ! complete words from that file. ! </para> ! <para> ! For example, the <literal>SIUnits</literal> package has a custom ! dictionary. ! </para> ! <para> ! If a package detected at startup is found by &ls; in the current ! directory or in a location specified by the <link ! linkend="Tex_TEXINPUTS">g:Tex_TEXINPUTS</link> variable, &ls; will ! scan the package for <literal>\newenvironment</literal> and ! <literal>newcommand</literal> lines and also append any commands and ! environments found to the list of commands and environments which you ! are prompted with when you press <link ! linkend="ls-imap-f5"><literal><F5></literal></link> or <link ! linkend="ls-imap-f7"><literal><F7></literal></link> in insert ! mode. ! </para> ! </section> <anchor id="latex-package-scanning" /> <para> In addition, the <literal>TeX-Suite > Packages</literal> menu also contains the following submenus *************** *** 816,866 **** are created. </formalpara> ! <section id="custom-packages"> ! <title>Custom Packages</title> ! <para> ! Often times, the preamble can become too long, and some people prefer ! to put most of their personalization in a custom package and include ! that using a <literal>\usepackage</literal> line. &ls; tries to search ! such customs package for other <literal>\usepackage</literal> lines, so ! that supported packages included in this indirect manner can also be ! used to create sub-menus, extend the <literal>'dict'</literal> setting ! etc. The most obvious place to place such custom packages is in the ! same directory as the edited file. In addition, &latex; also supports ! placing custom packages in places pointed to by the ! <literal>$TEXINPUTS</literal> environment variable. ! </para> ! <para> ! If you use the <literal>$TEXINPUTS</literal> variable in &latex;, and ! you wish &ls; to search these custom packages for ! <literal>\usepackage</literal> lines, then you need to initialize the ! <link linkend="Tex_TEXINPUTS"><literal>g:Tex_TEXINPUTS</literal></link> ! variable. ! </para> <para> ! The <literal>g:Tex_TEXINPUTS</literal> variable needs to be set in the ! same format which &vim; uses for the <literal>'path'</literal> setting. ! This format is explained in detail if you do ! <programlisting>:help file-searching</programlisting> ! from within &vim;. </para> <para> ! Therefore the value of <literal>g:Tex_TEXINPUTS</literal> will most ! probably be different from <literal>$TEXINPUTS</literal> which your ! native &latex; distribution uses. </para> <para> ! Example: ! <programlisting>let g:Tex_TEXINPUTS = '~/texmf/mypackages/**;./**'</programlisting> ! Note that directories are delimited by <literal>';'</literal>. </para> ! <note> <para> ! The present directory <literal>'.'</literal> is always searched. You ! need not incude that in <literal>g:Tex_TEXINPUTS</literal>. </para> ! </note> </section> <section id="supporting-packages"> ! <title>Supporting a package</title> <para> Supporting a package is easy and consists of writing a vim script with --- 847,919 ---- are created. </formalpara> ! <section id="automatic-package-detection"> ! <title>Automatic Package detection</title> <para> ! Whenever &ls; begins editing a new &latex; file, it scans it for ! <literal>\usepackage{name}</literal> lines, and if a supported package ! is found, then it will create sub-menus and add to the ! <literal>'dict'</literal> setting as described above. </para> <para> ! If a <link linkend="latex-master-file">master-file</link> has been specified, ! then it will scan that file instead of the current file. See the section ! <link linkend="custom-packages">Custom Packages</link> ! to see which files &ls; will scan in more detail. </para> <para> ! For all the packages detected in this manner, &ls; will take certain ! actions as described in the section <link ! linkend="package-actions">package support.</link>. </para> ! <section id="custom-packages"> ! <title>Custom Packages</title> <para> ! Often times, the preamble can become too long, and some people prefer ! to put most of their personalization in a custom package and include ! that using a <literal>\usepackage</literal> line. &ls; tries to search ! such customs package for other <literal>\usepackage</literal> lines, so ! that supported packages included in this indirect manner can also be ! used to create sub-menus, extend the <literal>'dict'</literal> setting ! etc. The most obvious place to place such custom packages is in the ! same directory as the edited file. In addition, &latex; also supports ! placing custom packages in places pointed to by the ! <literal>$TEXINPUTS</literal> environment variable. </para> ! <para> ! If you use the <literal>$TEXINPUTS</literal> variable in &latex;, and ! you wish &ls; to search these custom packages for ! <literal>\usepackage</literal> lines, then you need to initialize the ! <link linkend="Tex_TEXINPUTS"><literal>g:Tex_TEXINPUTS</literal></link> ! variable. ! </para> ! <para> ! The <literal>g:Tex_TEXINPUTS</literal> variable needs to be set in the ! same format which &vim; uses for the <literal>'path'</literal> setting. ! This format is explained in detail if you do ! <programlisting>:help file-searching</programlisting> ! from within &vim;. ! </para> ! <para> ! Therefore the value of <literal>g:Tex_TEXINPUTS</literal> will most ! probably be different from <literal>$TEXINPUTS</literal> which your ! native &latex; distribution uses. ! </para> ! <para> ! Example: ! <programlisting>let g:Tex_TEXINPUTS = '~/texmf/mypackages/**,./**'</programlisting> ! The <literal>**</literal> indicates that all directories below the ! directory <literal>~/texmf/mypackages</literal> and ! <literal>./</literal> are to be scanned for custom packages. ! </para> ! <note> ! <para> ! The present directory <literal>'.'</literal> is always searched. You ! need not incude that in <literal>g:Tex_TEXINPUTS</literal>. ! </para> ! </note> ! </section> </section> <section id="supporting-packages"> ! <title>Writing supporting for a package</title> <para> Supporting a package is easy and consists of writing a vim script with *************** *** 888,892 **** <section> <title><literal>g:Tex_package_<package></literal></title> ! <programlisting> g:TeX_package_<package> = "pre:Command,pre:Command1" More detailed example is in latex-suite/packages/exmpl file (slightly --- 941,945 ---- <section> <title><literal>g:Tex_package_<package></literal></title> ! <programlisting> g:TeX_package_<package> = "pre:Command,pre:Command1" More detailed example is in latex-suite/packages/exmpl file (slightly *************** *** 937,989 **** <para> This module provides an easy way to insert references to labels and ! bibliographic entries. Suppose you want to refer to an equation which is ! labelled as "eqn:eq-1" using the \label{eqn:eq-1} command. Somewhere in the ! text, you write "\ref{" with the cursor after the {. Now if you press <F9>, ! Latex-suite will try to search through all the .tex files in the present ! directory for lines beginning with "\label{". It will provide you with a list ! of all such matches in two small windows. </para> - <programlisting>+========================================================+ - | I want to insert a reference to equation 1. Therefore | - | I will write \ref{ | - | | - | | - | | - | | - | | - +--------------------------------------------------------+ - +file1.tex + - +========================================================+ - |file1.tex|100| \label{eqn:eq-1} | - |file1.tex|110| \label{eqn:eq-2} | - |file2.tex|178| \label{tab:table1} | - +--------------------------------------------------------+ - +[Error List] + - +========================================================+ - |\begin{equation} | - | e^{j*pi} + 1 = 0 \label{eqn:eq-1} | - |\end{equation} | - |And there was some text after this. I dont remember | - +--------------------------------------------------------+ - +file1.tex [Preview] + - +========================================================+</programlisting> <para> ! The first window (shown as "[Error List]" above) is a |cwindow| containing a ! list of matches and you will be left in it. The window beneath it is a ! |preview-window| showing the context of the match. When you move up and down ! in the "[Error List]" window, the preview window will be scrolled to keep in ! sync with the label. Pressing the "J" and "K" keys in the "[Error List]" ! window scrolls the preview window enabling you to see more context if you ! desire. After positioning yourself on a label which you want to insert, press ! CR>. This will automatically close all the new windows, take you back to the ! file being edited and insert the chosen label in place. Pressing "q" in the ! "[Error List]" window closes all windows without inserting anything. </para> <para> ! As can be seen above, the matches include everything which begins with \label. ! If you have the habit of prefixing all equation labels with "eqn:" or ! something similar, then you can restrict the matches to only equations by ! first typing "\ref{eqn:" and then pressing <F9>. This only brings up matches ! starting with "\label{eqn:" thus allowing you to skip table and figure labels. </para> <para> --- 990,1082 ---- <para> This module provides an easy way to insert references to labels and ! bibliographic entries. </para> <para> ! Consider the situation where you are editing a file with two equations ! labelled <literal>eqn:euler</literal> and <literal>eqn:einstein</literal>. ! Now you want to insert a reference to one of these equations. To do this, ! you type the <literal>\ref{eqn:}</literal> command and with the cursor ! placed after <literal>eqn:</literal>, press <literal><F9></literal>. ! This will bring up two new windows beneath the main window you were working ! in as shown in the figure below. </para> + <programlisting> + 7 + 8 These are a couple of equations: + 9 +-- 4 lines: eqnarray (eqn:euler) : e^{j\pi} + 1 &=& 0--------------- + 13 +-- 4 lines: equation (eqn:einstein) : E = m c^2--------------------- + 17 + 18 These are a couple of figures: + 19 +-- 7 lines: figure (fig:monkeys) : Monkeys can Type------------------- + 26 +-- 7 lines: figure (fig:shakespeare) : Shakespeare could not type----- + 33 + 34 This is a reference to \ref{eqn:}&ph; + 35 + 36 + 37 \end{document} + 38 + ~ + ~ + ~ + ~ + ~ + ~ + ~ + newfile.tex 34,32 Bot + newfile.tex|11| \label{eqn:euler} + newfile.tex|15| \label{eqn:einstein} + ~ + ~ + ~ + [Error List] 1,1 All + 7 + 8 These are a couple of equations: + 9 \begin{eqnarray} + 10 e^{j\pi} + 1 &=& 0 + 11 \label{eqn:euler} + 12 \end{eqnarray} + 13 \begin{equation} + 14 E = m c^2 + 15 \label{eqn:einstein} + 16 \end{equation} + newfile.tex [Preview] 11,3 21% + </programlisting> <para> ! The first window (shown as <literal>[Error List]</literal> above) is a ! <literal>|cwindow|</literal> containing a list of possible matches for the ! reference. The cursor will be located in the first line of this window. The ! bottom window is a <literal>preview-window</literal> showing the context of ! the <literal>\label</literal>. Moving around in the ! <literal>[Error List]</literal> window automatically scrolls the ! preview window so as to always keep showing the context of the ! <literal>\label</literal> being viewed in the ! <literal>[Error List]</literal> window. You can also press ! <literal>J</literal> and <literal>K</literal> in the ! <literal>[ErrorList]</literal> window to scroll the preview window up and ! down. ! </para> ! <para> ! To insert one of the labels, simply position the cursor in the correct line ! in the <literal>[Error List]</literal> window and press ! <literal><enter></literal>. This will immediately close the two newly ! opened windows, get back to the correct location in the original file being ! edited and insert the label into the <literal>\ref</literal> command. ! </para> ! <para> ! If you notice carefully in the example above, the ! <literal>[Error List]</literal> window only showed the matches for the ! equations and did not list any of the figure labels. This is because we ! pressed <literal><F9></literal> after <literal>\ref{eqn:</literal> ! instead of simply after <literal>\ref{</literal>. This caused &ls; to ! search only for those labels which started with the string ! <literal>eqn:</literal>. If you had pressed ! <literal><F9></literal> after a <literal>\ref{</literal>, you would ! have been shown matches from <emphasis>all</emphasis> labels, not just ! those starting with <literal>eqn:</literal>. ! </para> ! <para> ! Thus prefixing all your labels with <literal>eqn:</literal>, ! <literal>fig:</literal>, <literal>tab:</literal> etc. depending on what you ! are labelling will lead to an easier time completing references. </para> <para> *************** *** 1627,1662 **** <section id="latex-suite-maps"> <title>&ls; Maps</title> ! Normal usage of &ls; will typically involve using a fairly large number ! of mappings. It should be noted that many of the mappings can be changed ! to a different set of characters according to your particular needs. ! <section id="Plug_IMAPJumpForward"> ! <title><Plug>IMAP_JumpForward</title> <para> ! Default Key assigned : <literal><Ctrl-J></literal> </para> <para> ! This map takes you to the location of the next <link ! linkend="place-holders">place-holder</link>. </para> ! </section> ! <section id="Plug_IMAPJumpBack"> ! <title><Plug>IMAP_JumpBack</title> <para> ! Default Key assigned : NONE </para> <para> ! This map takes you to the previous <link linkend="place-holders">place-holder</link>. </para> - </section> - <section id="Plug_IMAP_DeleteAndJumpForward"> - <title><Plug>IMAP_DeleteAndJumpForward</title> <para> ! Default Key assigned : NONE </para> <para> ! This map deletes the presently selected place-holder irrespective of ! whether the present placeholder is empty or not and ignoring the value ! of place-holder settings like <link linkend="Imap_DeleteEmptyPlaceHolders"><literal>g:Imap_DeleteEmptyPlaceHolders</literal></link> and <link --- 1720,1818 ---- <section id="latex-suite-maps"> <title>&ls; Maps</title> ! <anchor id="remapping-latex-suite-keys" /> ! <para> ! Most of the mappings used in &ls; can be mapped to a different key ! combination to suit your particular needs. An example best explains the ! procedure for doing this. Suppose you want to remap the ! <literal><C-j></literal> key which &ls; (actually imaps.vim) uses ! to jump to the next placeholder. To do this, you first need to find out ! which <literal><Plug></literal> mapping ! <literal><C-j></literal> is derived from. You will need to look ! at the relevant section of this manual to do this. For example, the ! section <link linkend="customize-imap-maps">IMAP mappings</link> has ! the information that the <literal><C-j></literal> key is derived ! from <literal><Plug>IMAP_JumpForward</literal>. Therefore to ! remap the <literal><C-j></literal> key to say ! <literal><C-space></literal>, you will need to put a ! statement like the following in your <literal>~/.vimrc</literal>. ! <programlisting>imap <C-space> <Plug>IMAP_JumpForward</programlisting> ! </para> ! <note> <para> ! To change the <literal>IMAP</literal> mappings which affect jumping ! between placeholders, the <literal>map</literal> statement above has ! to be placed in your <literal>~/.vimrc</literal>. For other mappings ! you can place the <literal>map</literal> statement in your ! <literal>$VIM/ftplugin/tex.vim</literal> file. </para> <para> ! The reason for this is that the <literal><C-j></literal> maps ! are created in <literal>plugin/imaps.vim</literal>, which is sourced ! as soon as &vim; starts before sourcing any ftplugin files. </para> ! </note> ! <section id="customize-imap-maps"> ! <title>IMAP mappings</title> <para> ! These mappings are utlilized for jumping between placeholders as ! described <link linkend="place-holders">here</link>. See the <link ! linkend="latex-suite-maps">parent section</link> to find out how to ! use this information to change the default maps. </para> + <anchor id="Plug_IMAP_JumpForward" /> + <anchor id="Plug_IMAP_JumpBack" /> + <anchor id="Plug_IMAP_DeleteAndJumpForward" /> + <anchor id="Plug_IMAP_DeleteAndJumBack" /> + <informaltable frame="all"> + <tgroup cols="2"> + <thead> + <row> + <entry>Plug map</entry> + <entry>Default Key</entry> + </row> + </thead> + <tbody> + <row> + <entry><literal><Plug>IMAP_JumpForward</literal></entry> + <entry><literal><C-j></literal></entry> + </row> + <row> + <entry><literal><Plug>IMAP_JumpBack</literal></entry> + <entry>(none)</entry> + </row> + <row> + <entry><literal><Plug>IMAP_DeleteAndJumpForward</literal></entry> + <entry>(none)</entry> + </row> + <row> + <entry><literal><Plug>IMAP_DeleteAndJumpBack</literal></entry> + <entry>(none)</entry> + </row> + </tbody> + </tgroup> + </informaltable> <para> ! <literal><Plug>IMAP_JumpForward</literal> takes you to the ! location of the next <link linkend="place-holders">place-holder</link>. </para> <para> ! <literal><Plug>IMAP_JumpBack</literal> takes you to the previous ! <link linkend="place-holders">place-holder</link>. </para> <para> ! <literal><Plug>IMAP_DeleteAndJumpForward</literal> deletes the ! presently selected place-holder and jumps to the next place-holder ! irrespective of whether the present placeholder is empty or not and ! ignoring the value of place-holder settings like <link ! linkend="Imap_DeleteEmptyPlaceHolders"><literal>g:Imap_DeleteEmptyPlaceHolders</literal></link> ! and <link ! linkend="Imap_StickyPlaceHolders"><literal>g:Imap_StickyPlaceHolders</literal></link> ! </para> ! <para> ! <literal><Plug>IMAP_DeleteAndJumpBack</literal> deletes the ! presently selected place-holder and jumps to the previous place-holder ! irrespective of whether the present placeholder is empty or not and ! ignoring the value of place-holder settings like <link linkend="Imap_DeleteEmptyPlaceHolders"><literal>g:Imap_DeleteEmptyPlaceHolders</literal></link> and <link *************** *** 1664,1667 **** --- 1820,1859 ---- </para> </section> + <section id="customize-alt-key-maps"> + <title>Alt-Key mappings</title> + <para> + These mappings are are described in the section <link + linkend="bracketing-macros">Alt key macros</link>. See <link + linkend="remapping-latex-suite-keys">the parent section</link> to see + how to use the following information to remap keys. + </para> + <anchor id="Plug_Tex_MathBF" /> + <anchor id="Plug_Tex_MathCal" /> + <anchor id="Plug_Tex_LeftRight" /> + <informaltable frame="all"> + <tgroup cols="2"> + <thead> + <row> + <entry>Plug Mapping</entry> + <entry>Default Key</entry> + </row> + </thead> + <tbody> + <row> + <entry><literal><Plug>Tex_MathBF</literal></entry> + <entry><literal><Alt-B></literal></entry> + </row> + <row> + <entry><literal><Plug>Tex_MathCal</literal></entry> + <entry><literal><Alt-C></literal></entry> + </row> + <row> + <entry><literal><Plug>Tex_LeftRight</literal></entry> + <entry><literal><Alt-L></literal></entry> + </row> + </tbody> + </tgroup>... [truncated message content] |
From: <sri...@us...> - 2003-06-19 01:21:36
|
Update of /cvsroot/vim-latex/vimfiles/plugin In directory sc8-pr-cvs1:/tmp/cvs-serv9593 Modified Files: imaps.vim Log Message: Bug: IMAP_Jumpfunc() and VEnclose() do not work with &selection = 'exclusive' (Jannie Hofmeyr, Pierre Antoine Champin) Fix: Select one more character in 'exclusive' mode. (suggested by Pierre Antoine Champin). Index: imaps.vim =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/plugin/imaps.vim,v retrieving revision 1.31 retrieving revision 1.32 diff -C2 -d -r1.31 -r1.32 *** imaps.vim 25 Mar 2003 19:11:40 -0000 1.31 --- imaps.vim 19 Jun 2003 01:21:33 -0000 1.32 *************** *** 8,12 **** " while preserving filetype indentation. " ! " $Header$ " " Documentation: {{{ --- 8,12 ---- " while preserving filetype indentation. " ! " $Id$ " " Documentation: {{{ *************** *** 418,435 **** let placeHolderEmpty = !strlen(template) ! " Jumping doesn't work with exclusive ! let _selection = &selection ! let &selection = 'inclusive' ! let restoreselection = "let &selection = '"._selection."'" " Select till the end placeholder character. ! let movement = "\<C-o>v/\\V".pheUser."/e\<CR>" " Now either goto insert mode or select mode. if placeHolderEmpty && g:Imap_DeleteEmptyPlaceHolders " delete the empty placeholder into the blackhole. ! return movement."\"_c\<C-o>:".s:RemoveLastHistoryItem."|".restoreselection."\<CR>" else ! return movement."\<C-\>\<C-N>:".s:RemoveLastHistoryItem."|".restoreselection."\<CR>gv\<C-g>" endif --- 418,437 ---- let placeHolderEmpty = !strlen(template) ! " If we are selecting in exclusive mode, then we need to move one step to ! " the right ! let extramove = '' ! if &selection == 'exclusive' ! let extramove = 'l' ! endif " Select till the end placeholder character. ! let movement = "\<C-o>v/\\V".pheUser."/e\<CR>".extramove " Now either goto insert mode or select mode. if placeHolderEmpty && g:Imap_DeleteEmptyPlaceHolders " delete the empty placeholder into the blackhole. ! return movement."\"_c\<C-o>:".s:RemoveLastHistoryItem."\<CR>" else ! return movement."\<C-\>\<C-N>:".s:RemoveLastHistoryItem."\<CR>gv\<C-g>" endif *************** *** 512,518 **** endif let normcmd = normcmd. ! \a:vstart."!!mark!!".a:vend.newline. ! \"\<C-\>\<C-N>?!!mark!!\<CR>v7l\"_s\<C-r>r\<C-\>\<C-n>" " this little if statement is because till very recently, vim used to --- 514,526 ---- endif + " In exclusive selection, we need to select an extra character. + if &selection == 'exclusive' + let movement = 8 + else + let movement = 7 + endif let normcmd = normcmd. ! \ a:vstart."!!mark!!".a:vend.newline. ! \ "\<C-\>\<C-N>?!!mark!!\<CR>v".movement."l\"_s\<C-r>r\<C-\>\<C-n>" " this little if statement is because till very recently, vim used to |
From: <sri...@us...> - 2003-06-18 18:54:33
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv10906 Modified Files: latex-suite-chunk.xsl latex-suite.txt latex-suite.xml latex-suite.xsl Log Message: Oops. snipped Tex_TEXINPUTS section from wrong place. Index: latex-suite-chunk.xsl =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite-chunk.xsl,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** latex-suite-chunk.xsl 18 Jun 2003 05:12:38 -0000 1.1 --- latex-suite-chunk.xsl 18 Jun 2003 18:54:30 -0000 1.2 *************** *** 7,11 **** <!-- $Id$ --> ! <xsl:import href="file:///c:/users/srinath/testing/docbook/xhtml/chunk.xsl"/> <!-- import common customizations --> --- 7,11 ---- <!-- $Id$ --> ! <xsl:import href="docbook/xhtml/chunk.xsl"/> <!-- import common customizations --> Index: latex-suite.txt =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.txt,v retrieving revision 1.25 retrieving revision 1.26 diff -C2 -d -r1.25 -r1.26 *** latex-suite.txt 18 Jun 2003 05:12:38 -0000 1.25 --- latex-suite.txt 18 Jun 2003 18:54:30 -0000 1.26 *************** *** 1890,1896 **** *customizing-latex-completion* |ls_10_4_1| Window size settings ! |ls_10_4_2| g:Tex_TEXINPUTS ! |ls_10_4_3| g:Tex_BIBINPUTS ! |ls_10_4_4| g:Tex_RememberCiteSearch The following settings affect the completion [|latex-completion|] functionality --- 1890,1895 ---- *customizing-latex-completion* |ls_10_4_1| Window size settings ! |ls_10_4_2| g:Tex_BIBINPUTS ! |ls_10_4_3| g:Tex_RememberCiteSearch The following settings affect the completion [|latex-completion|] functionality *************** *** 1922,1941 **** ! g:Tex_TEXINPUTS *ls_10_4_2* ! *Tex_TEXINPUTS* ! ! ! Type string ! Default Value '' ! ! This setting describes the directories scanned by Latex-Suite while searching ! for custom user packages as desribed in the custom packages [|custom-packages|] ! section. Do not include the present directory in this setting. The present ! directory is always scanned for custom packages. ! ! This string should be set in the syntax accepted by Vim's native 'path' setting. ! ! ! g:Tex_BIBINPUTS *ls_10_4_3* *Tex_BIBINPUTS* --- 1921,1925 ---- ! g:Tex_BIBINPUTS *ls_10_4_2* *Tex_BIBINPUTS* *************** *** 1953,1957 **** ! g:Tex_RememberCiteSearch *ls_10_4_4* *Tex_RememberCiteSearch* --- 1937,1941 ---- ! g:Tex_RememberCiteSearch *ls_10_4_3* *Tex_RememberCiteSearch* *************** *** 2217,2240 **** Package Handling Customization *ls_10_9* *customizing-packages* ! |ls_10_4_2| g:Tex_TEXINPUTS ! Latex-Suite is capable of handling simple projects in which all the source files ! live in a single directory using the *.latexmain [|latex-master-file|] method. ! However, for more complex projects with files distributed in various ! directories, define the g:Tex_TEXINPUTS variable. ! g:Tex_TEXINPUTS *ls_10_4_2* *Tex_TEXINPUTS* ! Type String Default Value '' ! This string defines a set of directories which contain user packages. This ! setting corresponds to the $TEXINPUTS environment variable. ! TODO: The documentation for this part needs to be improved. ================================================================================ --- 2201,2224 ---- Package Handling Customization *ls_10_9* *customizing-packages* ! |ls_10_9_1| g:Tex_TEXINPUTS ! These settings affect the custom packages [|custom-packages|] functionality in ! Latex-Suite ! g:Tex_TEXINPUTS *ls_10_9_1* *Tex_TEXINPUTS* ! Type string Default Value '' ! This setting describes the directories scanned by Latex-Suite while searching ! for custom user packages as desribed in the custom packages [|custom-packages|] ! section. Do not include the present directory in this setting. The present ! directory is always scanned for custom packages. ! This string should be set in the syntax accepted by Vim's native 'path' setting. ================================================================================ Index: latex-suite.xml =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** latex-suite.xml 18 Jun 2003 17:28:35 -0000 1.2 --- latex-suite.xml 18 Jun 2003 18:54:30 -0000 1.3 *************** *** 2341,2367 **** </informaltable> </section> - <section id="Tex_TEXINPUTS"> - <title>g:Tex_TEXINPUTS</title> - <informaltable frame="all"> - <tgroup cols="2"> - <tbody> - <row><entry>Type</entry><entry>string</entry></row> - <row><entry>Default Value</entry> - <entry><literal>''</literal></entry></row> - </tbody> - </tgroup> - </informaltable> - <para> - This setting describes the directories scanned by &ls; while searching - for custom user packages as desribed in the <link - linkend="custom-packages">custom packages</link> section. Do not - include the present directory in this setting. The present directory - is always scanned for custom packages. - </para> - <para> - This string should be set in the syntax accepted by &vim;'s native - <literal>'path'</literal> setting. - </para> - </section> <section id="Tex_BIBINPUTS"> <title>g:Tex_BIBINPUTS</title> --- 2341,2344 ---- *************** *** 2753,2764 **** <section id="customizing-packages"> <title>Package Handling Customization</title> ! <para> &ls; is capable of handling simple projects in which all the ! source files live in a single directory using the <link ! linkend="latex-master-file">*.latexmain</link> method. However, for ! more complex projects with files distributed in various directories, ! define the <link ! linkend="Tex_TEXINPUTS"><literal>g:Tex_TEXINPUTS</literal></link> ! variable. </para> </section> <section id="latex-suite-credits"> --- 2730,2761 ---- <section id="customizing-packages"> <title>Package Handling Customization</title> ! <para> ! These settings affect the <link linkend="custom-packages">custom ! packages</link> functionality in &ls; </para> + <section id="Tex_TEXINPUTS"> + <title>g:Tex_TEXINPUTS</title> + <informaltable frame="all"> + <tgroup cols="2"> + <tbody> + <row><entry>Type</entry><entry>string</entry></row> + <row><entry>Default Value</entry> + <entry><literal>''</literal></entry></row> + </tbody> + </tgroup> + </informaltable> + <para> + This setting describes the directories scanned by &ls; while searching + for custom user packages as desribed in the <link + linkend="custom-packages">custom packages</link> section. Do not + include the present directory in this setting. The present directory + is always scanned for custom packages. + </para> + <para> + This string should be set in the syntax accepted by &vim;'s native + <literal>'path'</literal> setting. + </para> + </section> + </section> </section> <section id="latex-suite-credits"> Index: latex-suite.xsl =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.xsl,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** latex-suite.xsl 18 Jun 2003 05:12:38 -0000 1.1 --- latex-suite.xsl 18 Jun 2003 18:54:30 -0000 1.2 *************** *** 7,11 **** <!-- $Id$ --> ! <xsl:import href="file:///c:/users/srinath/testing/docbook/xhtml/docbook.xsl"/> <!-- import common customizations --> --- 7,11 ---- <!-- $Id$ --> ! <xsl:import href="docbook/xhtml/docbook.xsl"/> <!-- import common customizations --> |
From: <sri...@us...> - 2003-06-18 17:28:38
|
Update of /cvsroot/vim-latex/vimfiles/doc In directory sc8-pr-cvs1:/tmp/cvs-serv30009 Modified Files: latex-suite.xml Log Message: Remove duplicate section on g:Tex_TEXINPUTS. Index: latex-suite.xml =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/doc/latex-suite.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** latex-suite.xml 18 Jun 2003 05:12:38 -0000 1.1 --- latex-suite.xml 18 Jun 2003 17:28:35 -0000 1.2 *************** *** 2,6 **** <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" ! "file:///c:/users/srinath/testing/docbook/docbookx.dtd" [<!ENTITY dummy "dummy"> <!ENTITY date "$Date$"> --- 2,6 ---- <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" ! "docbook/xml/docbookx.dtd" [<!ENTITY dummy "dummy"> <!ENTITY date "$Date$"> *************** *** 2753,2784 **** <section id="customizing-packages"> <title>Package Handling Customization</title> ! <para> ! &ls; is capable of handling simple projects in which all the source files ! live in a single directory using the <link ! linkend="latex-master-file">*.latexmain</link> method. However, for more ! complex projects with files distributed in various directories, define the ! <literal>g:Tex_TEXINPUTS</literal> variable. </para> - <section id="Tex_TEXINPUTS"> - <title>g:Tex_TEXINPUTS</title> - <informaltable frame="all"> - <tgroup cols="2"> - <tbody> - <row><entry>Type</entry><entry>String</entry></row> - <row><entry>Default Value</entry> - <entry><literal>''</literal></entry></row> - </tbody> - </tgroup> - </informaltable> - <para> - This string defines a set of directories which contain user packages. - This setting corresponds to the <literal>$TEXINPUTS</literal> environment - variable. - </para> - <para> - TODO: The documentation for this part needs to be improved. - </para> - </section> - </section> </section> <section id="latex-suite-credits"> --- 2753,2764 ---- <section id="customizing-packages"> <title>Package Handling Customization</title> ! <para> &ls; is capable of handling simple projects in which all the ! source files live in a single directory using the <link ! linkend="latex-master-file">*.latexmain</link> method. However, for ! more complex projects with files distributed in various directories, ! define the <link ! linkend="Tex_TEXINPUTS"><literal>g:Tex_TEXINPUTS</literal></link> ! variable. </para> </section> <section id="latex-suite-credits"> |
From: <sri...@us...> - 2003-06-18 06:17:18
|
Update of /cvsroot/vim-latex/vimfiles In directory sc8-pr-cvs1:/tmp/cvs-serv32258 Modified Files: makefile Log Message: Also include the remoteOpen and bib_latexSuite files for the release. Index: makefile =================================================================== RCS file: /cvsroot/vim-latex/vimfiles/makefile,v retrieving revision 1.15 retrieving revision 1.16 diff -C2 -d -r1.15 -r1.16 *** makefile 31 May 2003 17:47:31 -0000 1.15 --- makefile 18 Jun 2003 06:17:15 -0000 1.16 *************** *** 13,18 **** --- 13,20 ---- zip -q latexSuite.zip plugin/libList.vim zip -q latexSuite.zip plugin/explorer.vim + zip -q latexSuite.zip plugin/remoteOpen.vim # ftplugins zip -q latexSuite.zip ftplugin/tex_latexSuite.vim + zip -q latexSuite.zip ftplugin/bib_latexSuite.vim zip -q latexSuite.zip ftplugin/tex/*.vim # files in the latex-suite directory. Skip the CVS files. *************** *** 39,44 **** \mv latexSuite.tar.gz $(DIR1)/ ; \ ) ! mv latexSuite.zip latexSuite`date +%Y%m%d`.zip ; \ ! mv latexSuite.tar.gz latexSuite`date +%Y%m%d`.tar.gz ; \ # target for removing archive files. --- 41,46 ---- \mv latexSuite.tar.gz $(DIR1)/ ; \ ) ! mv latexSuite.zip latexSuite`date +%Y%m%d`.zip ; \ ! mv latexSuite.tar.gz latexSuite`date +%Y%m%d`.tar.gz ; \ # target for removing archive files. *************** *** 55,64 **** # script looks like: # ! # #!/bin/bash ! # cd ~/testing/vimfiles; \ ! # cvs -q update; \ ! # make clean; \ ! # make; \ ! # cp latexsuite.* ~/htdocs/download/ # # Doing a release via sf.net has a couple of advantages: --- 57,66 ---- # script looks like: # ! # #!/bin/bash ! # cd ~/testing/vimfiles; \ ! # cvs -q update; \ ! # make clean; \ ! # make; \ ! # cp latexsuite.* ~/htdocs/download/ # # Doing a release via sf.net has a couple of advantages: *************** *** 76,84 **** # This is again related to the uphtdocs script on my sf.net account which # looks like: ! # #!/bin/sh ! # ! # # update the htdocs directory ! # cd /home/groups/v/vi/vim-latex/htdocs; cvs -q update ! # # update the packages directory # cd /home/groups/v/vi/vim-latex/htdocs/packages; cvs -q update uphtdocs: --- 78,86 ---- # This is again related to the uphtdocs script on my sf.net account which # looks like: ! # #!/bin/sh ! # ! # # update the htdocs directory ! # cd /home/groups/v/vi/vim-latex/htdocs; cvs -q update ! # # update the packages directory # cd /home/groups/v/vi/vim-latex/htdocs/packages; cvs -q update uphtdocs: |