vim-latex-devel Mailing List for Vim-Latex (Page 8)
Brought to you by:
srinathava,
tmaas
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(120) |
Dec
(118) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(145) |
Feb
(23) |
Mar
(30) |
Apr
(50) |
May
(88) |
Jun
(49) |
Jul
(41) |
Aug
(13) |
Sep
(51) |
Oct
(30) |
Nov
(80) |
Dec
(43) |
2004 |
Jan
(15) |
Feb
(25) |
Mar
(48) |
Apr
(12) |
May
(37) |
Jun
(52) |
Jul
(16) |
Aug
(10) |
Sep
(7) |
Oct
(19) |
Nov
(17) |
Dec
(19) |
2005 |
Jan
(15) |
Feb
(5) |
Mar
(7) |
Apr
(3) |
May
(2) |
Jun
(4) |
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
(16) |
Dec
(16) |
2006 |
Jan
(15) |
Feb
(27) |
Mar
(49) |
Apr
(31) |
May
(24) |
Jun
(12) |
Jul
(23) |
Aug
(13) |
Sep
(22) |
Oct
(6) |
Nov
(8) |
Dec
(10) |
2007 |
Jan
(3) |
Feb
(13) |
Mar
(19) |
Apr
(1) |
May
(5) |
Jun
(10) |
Jul
(2) |
Aug
(13) |
Sep
(10) |
Oct
(2) |
Nov
(30) |
Dec
(15) |
2008 |
Jan
(11) |
Feb
(9) |
Mar
(27) |
Apr
(27) |
May
(22) |
Jun
(29) |
Jul
|
Aug
(21) |
Sep
(6) |
Oct
(4) |
Nov
(9) |
Dec
(2) |
2009 |
Jan
(52) |
Feb
(21) |
Mar
(9) |
Apr
(41) |
May
(13) |
Jun
(8) |
Jul
(5) |
Aug
(31) |
Sep
(14) |
Oct
(10) |
Nov
(17) |
Dec
(17) |
2010 |
Jan
(25) |
Feb
(22) |
Mar
(22) |
Apr
(24) |
May
(35) |
Jun
(23) |
Jul
(22) |
Aug
(10) |
Sep
(6) |
Oct
(29) |
Nov
(8) |
Dec
(6) |
2011 |
Jan
(12) |
Feb
(89) |
Mar
(41) |
Apr
(8) |
May
(17) |
Jun
(11) |
Jul
(3) |
Aug
(13) |
Sep
(14) |
Oct
(23) |
Nov
(8) |
Dec
(9) |
2012 |
Jan
(15) |
Feb
(27) |
Mar
(6) |
Apr
(17) |
May
(29) |
Jun
(9) |
Jul
(50) |
Aug
(15) |
Sep
(11) |
Oct
(12) |
Nov
(22) |
Dec
(7) |
2013 |
Jan
(24) |
Feb
(32) |
Mar
(6) |
Apr
(5) |
May
(2) |
Jun
(15) |
Jul
(20) |
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(7) |
Dec
(4) |
2014 |
Jan
(3) |
Feb
(7) |
Mar
(4) |
Apr
|
May
(4) |
Jun
(5) |
Jul
(4) |
Aug
(3) |
Sep
(9) |
Oct
|
Nov
(2) |
Dec
(3) |
2015 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
(6) |
Sep
(2) |
Oct
|
Nov
(6) |
Dec
|
2016 |
Jan
(1) |
Feb
(11) |
Mar
(4) |
Apr
(2) |
May
(8) |
Jun
(9) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
(7) |
Nov
|
Dec
|
2017 |
Jan
(7) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2018 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mauro S. <mau...@gm...> - 2013-11-17 09:52:47
|
Although I read some posts on the net about vim and biber, still I'm not able to compile correctly. Following some suggestion, I put in my texcr (at line 96) ================================= TexLet g:Tex_MultipleCompileFormats = 'pdf,bbl' ================================= and at line 126 ========================================== TexLet g:Tex_BibtexFlavor = 'biber' ========================================== Moreover, I changed my compiler.vim this way at lines 567-8: ============================================================================== if runCount == 0 && Tex_IsPresentInFile('\\bibdata', mainFileName_root.'.bcf') let bibFileName = mainFileName_root.'.bbl' ============================================================================== However, during the compilation I receive the message: =================================================== LaTeX Warning: Empty Bibliography on line 27 =================================================== (the line of the source file tex where I put \printbibliography). I find only bcf file, not bbl nor blg So I really I don'k know what else I can do... Note that leaving bibtex as backend all works fine thanx in advamce m -- Linux user no.: 353546 public key at http://keyserver.linux.it |
From: John R. <joh...@ne...> - 2013-11-05 09:18:37
|
Hi, If I don't do ':set paste on' before using ':TTemplate', the indentation of the template is all messed up. Is it possible to get vim-latex to turn this on when using templates? Thanks for vim-latex! Regards, John. |
From: Till M. <ope...@ti...> - 2013-10-20 09:38:55
|
Thank you, the patch was applied in commit ca0e25807347c7f61b05a00d56bd8e94f8925c25. Regards Till |
From: Till M. <ope...@ti...> - 2013-10-13 21:51:22
|
Hi, I just created a new repo for vim-latex at github: https://github.com/vim-latex/vim-latex Ted Pavlic should have commit access there together with me. I will probably remove the sourceforge Git repo eventually. Regards Till |
From: Ruthard B. <rut...@we...> - 2013-09-17 11:15:31
|
>== Auszüge aus der Nachricht von Rudra Banerjee vom 2013-09-14 11:35: > Hello friends, > I am facing a problem for using shortcuts provided by vim-latex. Say, I > want \textbf, so I was trying `bf. But, given, `b is a shortcut for > \beta, I always end up with something \betaf. > > FBF works, how can I use `bf? > any help? > `bf (as `sf and other friends) are _not_ synonyms for FBF of FSF and such. The Manual says: 3.3 Font Mappings These mappings insert font descriptions such as: \textsf{<++>}<++> with the cursor left in place of the first placeholder (the <++> characters). Mnemonic: first letter is always F (F for font) 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 have it enclosed in: \textsf{word} or {\sffamily line } depending on character-wise or line-wise selection. Thus you have to use FBF during typing to insert \textbf{}, and `bf to apply the same _after_ typing the text to a visually selected part of the text. happy vimming, Ruthard |
From: Rudra B. <rud...@ao...> - 2013-09-14 09:48:41
|
Hello friends, I am facing a problem for using shortcuts provided by vim-latex. Say, I want \textbf, so I was trying `bf. But, given, `b is a shortcut for \beta, I always end up with something \betaf. FBF works, how can I use `bf? any help? |
From: Michael L. <va...@gm...> - 2013-09-05 11:37:30
|
Dear developers und maintainers, I used to change the default output format (e.g. from pdf to ps) while editing a .tex file in vim/gvim 7.3 (2010 Aug 15, compiled May 4 2012 04:21:49) on Linux (Ubuntu 12.04). It worked perfectly some months ago, but for a couple of weeks, vim (or vim latex-suite) doesn't recognize the necessary variable changes. My ~/.vim/ftplugin/tex.vim is as follows: let g:Tex_DefaultTargetFormat = 'ps' let g:Tex_FormatDependency_ps = 'dvi,ps' let g:Tex_FormatDependency_pdf = 'pdf' let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode --src-specials $*' let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi' let g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*' set sw=2 set iskeyword+=: When I open a *.tex file in vim and compile via \ll, I get a *.ps file. If I now change the default target format by typing :let g:Tex_DefaultTargetFormat = 'pdf' in vim, the variable seems to be set correctly (at least a ":echo g:Tex_DefaultTargetFormat" reveals "pdf"), but when compiling, I still only get a *.ps. As I mentioned, it worked some months ago. If I change the format in the tex.vim file and restart vim, everything is perfect. I tried (clean) reinstalling latex-suite, resetting my .vimrc etc - it just doesn't work. I'm not sure if vim was updated on Ubuntu a few weeks ago. Do you have any suggestions regarding this bug? Regards, Michael P.S.: Anyway - vim-latex is an excellent and very useful plugin! Thanks a lot!!! |
From: corentin b. <cor...@gm...> - 2013-08-27 22:42:36
|
Hi, I've been trying knitr ultimately and the smart quotes make the use of knitr impossible. In order to keep the functionality of the smart quotes but being able to use knitr I propose to disable the smart quotes in comments, just like it's done within math expressions. The following is working perfectly on my machine: in ftplugin/latex-suite/main.vim in function! s:TexQuotes() " In math mode or when preceded by a \, just move the cursor past the " already-inserted " character. if (synIDattr(synID(l, c, 1), "name") =~ "^texMath") \ || (c > 1 && (getline(l)[c-2] == '\')) becomes " In math mode, comments or when preceded by a \, just move the cursor past the " already-inserted " character. let colComment = match(getline(l),"%",0) if (synIDattr(synID(l, c, 1), "name") =~ "^texMath") \ || (c > 1 && (getline(l)[c-2] == '\')) \ || ((colComment > -1) && (colComment < c)) Please tell me if I can do something else to get that into the code: any git repository where I can make a pull request? Corentin -- ___________________ Corentin Barbu-Covantes (484) 843-1580 http://scholar.google.com/citations?hl=en&user=sxDMRdQAAAAJ "For what does it profit a man to gain the whole world, and forfeit his soul?" Mark 8:36 |
From: Bernhard B. <bl...@db...> - 2013-07-26 15:51:57
|
> I confirm I can reproduce this on Arch Linux, using the packages gvim > 7.3.1287-1 and vim-latexsuite 20130126-1. Just my 2c. Thanks. If anyone is interested in a solution: I have traced the issue to vim itself and I have dug around in vim's code repository, trying out different versions. It turns out the mentioned issue appeared with vim 7.3.1253 and has been fixed in vim 7.3.1303. (https://code.google.com/p/vim/source/detail?r=6e611380b4cf586f210de94d92a4f158b6900a5f&path=/src/edit.c) So using a version older than 1253 or at least 1303 will help. I guess it won't be long until an updated Arch Linux package is available, too. Best regards Bernhard |
From: Alessandro P. <ale...@la...> - 2013-07-26 13:24:16
|
On 26 July 2013 12:32, Bernhard Bliem <bl...@db...> wrote: > 2013/7/26 Filip Kadlec <ka...@fz...>: >> Hello Bernhard, >> >> I don't have a solution to your problem, just want to note that in my >> case "u" undoes the whole word (or typing sequence) straight, no >> letter-by-letter behavior occurs. My version of vim is 7.3, too. This >> works regardless of whether the latex suite is loaded. >> >> Hope this helps, Filip > > Hello Filip, > > Thank you for looking into it. I am pretty sure that it's indeed not > the LaTeX suite's fault, since I have now compiled vim myself (both > 7.3 and the current Mercurial version) and everything works as it > should, also with the LaTeX suite. It seems that the problem concerns > the Arch Linux package of vim. I confirm I can reproduce this on Arch Linux, using the packages gvim 7.3.1287-1 and vim-latexsuite 20130126-1. Just my 2c. Alessandro |
From: Bernhard B. <bl...@db...> - 2013-07-26 10:32:22
|
2013/7/26 Filip Kadlec <ka...@fz...>: > Hello Bernhard, > > I don't have a solution to your problem, just want to note that in my > case "u" undoes the whole word (or typing sequence) straight, no > letter-by-letter behavior occurs. My version of vim is 7.3, too. This > works regardless of whether the latex suite is loaded. > > Hope this helps, Filip Hello Filip, Thank you for looking into it. I am pretty sure that it's indeed not the LaTeX suite's fault, since I have now compiled vim myself (both 7.3 and the current Mercurial version) and everything works as it should, also with the LaTeX suite. It seems that the problem concerns the Arch Linux package of vim. Best regards Bernhard |
From: Filip K. <ka...@fz...> - 2013-07-26 09:10:49
|
Hello Bernhard, I don't have a solution to your problem, just want to note that in my case "u" undoes the whole word (or typing sequence) straight, no letter-by-letter behavior occurs. My version of vim is 7.3, too. This works regardless of whether the latex suite is loaded. Hope this helps, Filip On Tue, 23 Jul 2013, Bernhard Bliem wrote: > Hello, > > Suppose I start vim, enter insert mode, write the text "foobar" and > exit insert mode. Then pressing "u" should undo this change, i.e., > remove "foobar". This works as expected in "plain" vim, but not after > vim-latex has been loaded (say when I open a *.tex file and vim > recognizes that vim-latex needs to be loaded). What happens then is > that "u" only undoes one character at a time, i.e., it removes only > "r"; when pressing it again it removes "a", and so on. > > To reproduce: > 1. Start vim and load some *.tex file such that vim-latex is loaded. > 2. Insert "foobar" somewhere in that buffer. > 3. Press u. > (I have tried this with a .vimrc only conaining "filetype plugin on".) > > Interestingly, closing the LaTeX file and opening any other buffer > (say with the :new command) does not make the problem go away. Even if > you start vim and open a *.tex file in a new tab, then the problem > suddenly appears also in the first ("virgin") tab. > > Clearly, this behavior is not desired, but I can't make sense of it. > It used to work fine some time ago but might have been broken during > an update. I'm using Arch Linux with the vim-latexsuite package, but > the problem persists when using the latest version from Git. Vim has > version 7.3. > > Hope this is not due to a silly mistake on my part. Thanks for the help. > > Best regards > Bernhard > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Bernhard B. <bl...@db...> - 2013-07-23 16:45:36
|
Hello, Suppose I start vim, enter insert mode, write the text "foobar" and exit insert mode. Then pressing "u" should undo this change, i.e., remove "foobar". This works as expected in "plain" vim, but not after vim-latex has been loaded (say when I open a *.tex file and vim recognizes that vim-latex needs to be loaded). What happens then is that "u" only undoes one character at a time, i.e., it removes only "r"; when pressing it again it removes "a", and so on. To reproduce: 1. Start vim and load some *.tex file such that vim-latex is loaded. 2. Insert "foobar" somewhere in that buffer. 3. Press u. (I have tried this with a .vimrc only conaining "filetype plugin on".) Interestingly, closing the LaTeX file and opening any other buffer (say with the :new command) does not make the problem go away. Even if you start vim and open a *.tex file in a new tab, then the problem suddenly appears also in the first ("virgin") tab. Clearly, this behavior is not desired, but I can't make sense of it. It used to work fine some time ago but might have been broken during an update. I'm using Arch Linux with the vim-latexsuite package, but the problem persists when using the latest version from Git. Vim has version 7.3. Hope this is not due to a silly mistake on my part. Thanks for the help. Best regards Bernhard |
From: Gary J. <gar...@sp...> - 2013-07-22 00:36:59
|
On 2013-07-21, Rudra Banerjee wrote: > Hi, > by any plugin (or from vim-latex), is it possible to browse image file > to be inserted? > i mean, if I put some key-combination after > \includegraphics[scale]{fig:<cursor is here>}, > then a filebrowser will open and selected file will be pasted at the > cursor position with its full path. > any idea? I don't have a turn-key solution, but it's possible to use the ranger file manager (ranger.nongnu.org) as a file browser for vim (in a terminal, not in gvim) and there has been some recent discussion on the ranger mailing list about how to use it with w3m to browse images, so I'm pretty sure you could hack something together. Regards, Gary |
From: Rudra B. <rud...@ao...> - 2013-07-21 17:33:59
|
Hi, by any plugin (or from vim-latex), is it possible to browse image file to be inserted? i mean, if I put some key-combination after \includegraphics[scale]{fig:<cursor is here>}, then a filebrowser will open and selected file will be pasted at the cursor position with its full path. any idea? |
From: Nick R. <nic...@gm...> - 2013-07-21 11:07:27
|
Many thanks Gary I have managed to sort it. While the vimlatex instructions refer to $PATH the windows path variable is merely called "Path". So there's the VIM name and the windows name. I'm getting it to compile in a directory with no space in the path, and now I need to experiment with a directory with a space in the path Thanks for input! Nick On 21 July 2013 06:26, Gary Johnson <gar...@sp...> wrote: > On 2013-07-19, Nick Riches wrote: > > Hi Gary > > > > Thanks for response. Here's some more info... > > > > - When I type :echo $PATH in vim I get a whole load of stuff, but it > doesn't > > appear to contain the environment variable for latex.exe. (image below) > > Right. I think you need to add the directory of latex.exe to that. > It may work to add this to your vimrc: > > let $PATH .= ';C:\Users\Nick > Riches\Documents\miktexportable\miktex\bin' > > > - The path (called $PATH) is "C:\Users\Nick > Riches\Documents\miktexportable\ > > miktex\bin", so it definitely contains a space. It's very difficult to > get rid > > of this space as it is part of my user name (I would have to set up a new > > account and transfer everything over - a big pain) > > If I could set up my Windows system again, I would not give it it my > first and last names. That space has indeed been a huge pain. > > In my case, my MikTex files are under "C:\Program Files", but that > space never seemed to cause a problem for vim-latex. > > > - Command to compile is \ll > > > > - The compile tells me that it "Ran latex 1 time", but it doesn't pick up > > errors, and no .dvi appears, so it doesn't appear to be running latex. > > When I compile LaTeX files, I also get a file with a .log extension. > You may find a clue in there. > > Regards, > Gary > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > -- Lecturer in Speech and Language Pathology Room 1.9 King George VI Building Queen Victoria Road University of Newcastle-upon Tyne NE1 7RU 0191 222 8720 |
From: Gary J. <gar...@sp...> - 2013-07-21 05:27:56
|
On 2013-07-19, Nick Riches wrote: > Hi Gary > > Thanks for response. Here's some more info... > > - When I type :echo $PATH in vim I get a whole load of stuff, but it doesn't > appear to contain the environment variable for latex.exe. (image below) Right. I think you need to add the directory of latex.exe to that. It may work to add this to your vimrc: let $PATH .= ';C:\Users\Nick Riches\Documents\miktexportable\miktex\bin' > - The path (called $PATH) is "C:\Users\Nick Riches\Documents\miktexportable\ > miktex\bin", so it definitely contains a space. It's very difficult to get rid > of this space as it is part of my user name (I would have to set up a new > account and transfer everything over - a big pain) If I could set up my Windows system again, I would not give it it my first and last names. That space has indeed been a huge pain. In my case, my MikTex files are under "C:\Program Files", but that space never seemed to cause a problem for vim-latex. > - Command to compile is \ll > > - The compile tells me that it "Ran latex 1 time", but it doesn't pick up > errors, and no .dvi appears, so it doesn't appear to be running latex. When I compile LaTeX files, I also get a file with a .log extension. You may find a clue in there. Regards, Gary |
From: Nick R. <nic...@gm...> - 2013-07-19 11:40:39
|
Hi Gary Thanks for response. Here's some more info... - When I type :echo $PATH in vim I get a whole load of stuff, but it doesn't appear to contain the environment variable for latex.exe. (image below) - The path (called $PATH) is "C:\Users\Nick Riches\Documents\miktexportable\miktex\bin", so it definitely contains a space. It's very difficult to get rid of this space as it is part of my user name (I would have to set up a new account and transfer everything over - a big pain) - Command to compile is \ll - The compile tells me that it "Ran latex 1 time", but it doesn't pick up errors, and no .dvi appears, so it doesn't appear to be running latex. Thanks Nick On 18 July 2013 23:41, Gary Johnson <gar...@sp...> wrote: > On 2013-07-17, Nick Riches wrote: > > Hi > > > > I'm learning vimlatex portable version (we have a locked in system at > work). > > When I compile a .dvi file does not appear. I've followed the > troubleshoot > > instructions, and it appears that vimlatex cannot find latex.exe (step > 3). The > > environment variable is called %PATH as specified in the instructions, > and I've > > double-checked the path name. I note that there is also another program > with > > the environment variable path (lower case). > > > > Could anyone advise me on why this isn't working? Could it be to do with > spaces > > in the path name? > > It could be, but since you haven't provided > > - the value of %PATH%, or within Vim, $PATH, > - the path to latex.exe, > - the command you use to compile, or > - what you see on the screen when you compile, > > it's hard to tell. > > Regards, > Gary > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > -- Lecturer in Speech and Language Pathology Room 1.9 King George VI Building Queen Victoria Road University of Newcastle-upon Tyne NE1 7RU 0191 222 8720 |
From: Gary J. <gar...@sp...> - 2013-07-18 22:57:29
|
On 2013-07-17, Nick Riches wrote: > Hi > > I'm learning vimlatex portable version (we have a locked in system at work). > When I compile a .dvi file does not appear. I've followed the troubleshoot > instructions, and it appears that vimlatex cannot find latex.exe (step 3). The > environment variable is called %PATH as specified in the instructions, and I've > double-checked the path name. I note that there is also another program with > the environment variable path (lower case). > > Could anyone advise me on why this isn't working? Could it be to do with spaces > in the path name? It could be, but since you haven't provided - the value of %PATH%, or within Vim, $PATH, - the path to latex.exe, - the command you use to compile, or - what you see on the screen when you compile, it's hard to tell. Regards, Gary |
From: Nick R. <nic...@gm...> - 2013-07-18 16:38:55
|
Thanks for the response anyway Best Nick On 18 July 2013 14:42, Raniere Silva <ra0...@im...> wrote: > Nick, > > all the machines that I use are running a GNU/Linux distribution. Sorry for > can't help you very much. > > Raniere > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > -- Lecturer in Speech and Language Pathology Room 1.9 King George VI Building Queen Victoria Road University of Newcastle-upon Tyne NE1 7RU 0191 222 8720 |
From: Raniere S. <ra0...@im...> - 2013-07-18 13:42:23
|
Nick, all the machines that I use are running a GNU/Linux distribution. Sorry for can't help you very much. Raniere |
From: Nick R. <nic...@gm...> - 2013-07-18 12:01:28
|
Sorry, Raniere. Should have specified this in the email. It's Windows 7. Best NIck On 17 July 2013 22:48, Raniere Silva <ra0...@im...> wrote: > Nick, > > are you using vim in a GNU/Linux distribution or in another operational > system? > > Raniere > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > -- Lecturer in Speech and Language Pathology Room 1.9 King George VI Building Queen Victoria Road University of Newcastle-upon Tyne NE1 7RU 0191 222 8720 |
From: Raniere S. <ra0...@im...> - 2013-07-17 21:48:38
|
Nick, are you using vim in a GNU/Linux distribution or in another operational system? Raniere |
From: Nick R. <nic...@gm...> - 2013-07-17 19:01:02
|
Hi I'm learning vimlatex portable version (we have a locked in system at work). When I compile a .dvi file does not appear. I've followed the troubleshoot instructions, and it appears that vimlatex cannot find latex.exe (step 3). The environment variable is called %PATH as specified in the instructions, and I've double-checked the path name. I note that there is also another program with the environment variable path (lower case). Could anyone advise me on why this isn't working? Could it be to do with spaces in the path name? Many thanks Nick Riches -- Lecturer in Speech and Language Pathology Room 1.9 King George VI Building Queen Victoria Road University of Newcastle-upon Tyne NE1 7RU 0191 222 8720 |
From: Rudra B. <rud...@ao...> - 2013-07-10 15:57:22
|
Thanks. its solved. main problem was to find the correct file to edit(which is envmacros.vim). On Tue, 2013-07-09 at 14:50 +0200, Ruthard Baudach wrote: > Just redefine EFI in .vim/after/ftplugin/tex.vim or in .vimrc: > > > call IMAP ( 'EFI', "\\begin{figure}[<+htpb+>]\<CR> \\centering\<CR> \\includegraphics[scale=<++>]{<+figure+>}\<CR> \\caption{<+caption text+>}\<CR> \\label{fig:<+label+>}\<CR>\\end{figure}<++>", 'tex') > > > The files in .vim/after are loaded after the normal plugin processing > took place, and are intended to override plugin code locally. > > As .vimrc is loaded as last file, this code could be placed there, too. > > Normally it was a bad idea to override a filetype plugin in .vimrc, > as the definitions here affect all file types, but IMAP has the > third parameter filetype, thus this redefinition in the .vimrc will > affect only .tex files. > > For a deeper understanding of IMAP try :help IMAP. > > Take care to escape all "\" and the first "<" of the vim keycode for > "Enter" (<CR>), and to use " for the second string. > > There is one problem left: if you use this code, the formatting will be > shifted one space each line. I think this might be due to the default > "nopaste" mode of vim, and don't know how vim-latex solves this. > > Either, if they shifted the default mode to "paste", it should work, or > you will have to take a look on vim-latex's code to solve it. > > Greetings, > > Ruthard > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |