vim-latex-devel Mailing List for Vim-Latex (Page 76)
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: Thomas W. <we...@nu...> - 2004-09-28 13:53:06
|
Hi, is it possible to store templates in a user's home directory? I don't want to fiddle around with the global settings/templates. Best regards Thomas |
From: Jan H. <vim...@so...> - 2004-09-24 13:36:11
|
Hi all, typically i have several gvims opened with *.tex files. When i want to enter reference (F9), it opens in preview window the source of reference. But it opens in *edit* mode, which cause vim to ask question "Swap file already exists...", which is annoying. Would it be possible to open files in preview as read-only (maybe as configurable option)? I understand, that this happens at line exe 'silent! bot pedit +'.viewline.' '.viewfile but have no idea, how to insert ro option. Thanks, Jan |
From: Shingo A. <vim...@so...> - 2004-09-22 15:10:52
|
Hello, I use vim-latex in mac os x, and today I update from 1.5 to 20040805. Then ¥ll won't work in my box. The way ¥ll works has been changed, and viewer rules g:Tex_ViewRule_{pdf,ps,dvi} too. Now, ftplugin/texrc says g:Tex_ViewRule_pdf takes Application commands to open pdf/dvi files (no 'open' needed) , and if leave blank, the system picks the default app(ex. preview.app). Tex_ViewLaTeX() implements as above. if strlen(s:viewer) let s:viewer = '-a '.s:viewer endif let execString = 'open '.s:viewer.' $*.'.s:target but if leave g:Tex_ViewRule_pdf blank, when open a .tex file I get an error from Tex_SetTeXCompilerTarget() like this No View rule defined for target pdf Please specify a rule in $VIMRUNTIME/ftplugin/tex/texrc. :help Tex_ViewRule_format for more information so, I made this patch (rather ad-hoc). --- compiler.vim.orig Thu Sep 22 22:00:21 2004 +++ compiler.vim Wed Sep 22 23:09:02 2004 @@ -23,7 +23,7 @@ let targetRule = Tex_GetVarValue('Tex_'.a:type.'Rule_'.target) - if targetRule != '' + if targetRule != '' || (has('macunix') && a:type == 'View') if a:type == 'Compile' let &l:makeprg = escape(targetRule, Tex_GetVarValue('Tex_EscapeChars')) elseif a:type == 'View' -- Shingo Adachi |
From: Bernard U. <vim...@so...> - 2004-09-22 07:41:26
|
Hello, I would like to know how to modify the latex-suite configuration in order to have access to the diacritics "é" character on my keyboard ? I believe that by default the keyboard character "é" is mapped with some action. Thank you for any help. Bernard |
From: tomek <p...@ll...> - 2004-09-19 11:57:18
|
hello, when i try `. it should insert \cdot tag but it doesn't... Others expansions work without problems... (`, `; `@ etc...) I'm doing something wrong ? thanks in advance, tomek ps. tested with latex-suite 1.5 and 20040805-dev versions |
From: Luc H. <her...@fr...> - 2004-09-17 10:10:21
|
Hello, * On Fri, Sep 17, 2004 at 02:50:56AM -0700, Miguel Alonso <vim...@so...valid> wrote: > I recently discovered vim-latex, it's very nice. I find very useful to > have the whole latex document folded, I even like to refresh the > foldings when possible. What I didn't like is that I haven't found a > "unfolding" command. I was using vimspell to spell check my (fully > folded) document and surprise! I had to unfold every single group to > find where the spelling errors were. Not very comfortable! zi and zn are your friends. :h zi :h zn You should ask Matthieu to reset &foldenable in his plugin. HTH. -- Luc Hermitte http://hermitte.free.fr/vim/ |
From: Miguel A. <vim...@so...> - 2004-09-17 09:50:57
|
I recently discovered vim-latex, it's very nice. I find very useful to have the whole latex document folded, I even like to refresh the foldings when possible. What I didn't like is that I haven't found a "unfolding" command. I was using vimspell to spell check my (fully folded) document and surprise! I had to unfold every single group to find where the spelling errors were. Not very comfortable! thanks |
From: Bjoern R. <vim...@so...> - 2004-08-27 21:01:40
|
Hi! A few days ago, I discovered your project when looking for a way to edit tex files in vim. I am running Debian Sarge, so I installed the Debian-package (vim-latexsuite (0.20040805-1)). When trying to compile a tex-file using the '\ll'-command, I get the following error message: Error detected while processing function Tex_RunLaTeX: line 7: E121: Undefined variable: s:target E15: Invalid expression: s:target line 10: E121: Undefined variable: s:target E116: Invalid arguments for function Tex_Debug("Tex_RunLaTeX: compiling to target [".s:target."]", "comp") line 12: E121: Undefined variable: s:target E116: Invalid arguments for function Tex_GetVarValue('Tex_FormatDependency_'.s:target) != '' E15: Invalid expression: Tex_GetVarValue('Tex_FormatDependency_'.s:target) != '' line 21: E121: Undefined variable: dependency E116: Invalid arguments for function Tex_Debug('Tex_RunLaTeX: getting dependency chain = ['.dependency.']', 'comp') line 25: E121: Undefined variable: dependency E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) != '' E15: Invalid expression: Tex_Strntok(dependency, ',', i) != '' line 51: E121: Undefined variable: initTarget E15: Invalid expression: initTarget I could not find anything about it in your FAQ. Please tell me if this is a misconfiguration or if maybe something is wrong with the debian package. Thanks in advance for your help! Regards Bjoern Rosenbach |
From: Young <vim...@so...> - 2004-08-27 16:54:42
|
I followed the installation instruction, but it does not seem to work. I downloaded and installed vim 6.3 and extracted latexSuite.tar.gz in the vim directory. (I am using Yellow Dog linux and I assumed ~/.vim directory in the instruction meant the vim directory) And I could not fine .vimrc file, but found vimrcexample file instead. In the vimrcexample file, it is said copy this file to use it. So, I copied it and assumed this as .vimrc file and changed it according to the instruction. And after I installed help files, help files won't be opened if I type ":help latex-suite.txt" according to the instruction. But, it will be opened if I type ":help latex" instead. After finishing installation procedure, I ran latex and it returns with the error message "bash: latex: command not found". I think installation failed, but do not know what is wrong. Please help me on this problem. Any help would be greatly appreciated. Thanks. |
From: Srinath A. <sr...@fa...> - 2004-08-26 02:44:27
|
On Wed, 25 Aug 2004, Sebastian wrote: > why is every special key in this form escaped?? > > it\'s hard to read, especially if > you post vim-scripts. > I fixed this just now... Thanks for pointing it out. Srinath |
From: David W. <vim...@so...> - 2004-08-25 13:38:09
|
Not strictly related to vim-latex, but could you help me set the \'include\' option so that files included by the \\input, \\include and \\bibliography commands are searched. |
From: Sebastian <vim...@so...> - 2004-08-25 12:59:34
|
why is every special key in this form escaped?? it\'s hard to read, especially if you post vim-scripts. Seb. |
From: Sebastian M. <vim...@so...> - 2004-08-25 12:54:52
|
Hi! If I open a new (german) quotation with \" I get a vimspell error after every word. Im not sure if this is a bug in vimspell or latex-suite (or my config)... I thinks it\'s vimspell. Anyway: If I _type_ \\glqq and \\grqq everything is ok. Now: How do I map these commands to SmartQuotation? I tried: let b:Tex_SmartQuoteOpen = \'\\glqq \' let b:Tex_SmartQuoteClose = \'\\grqq \' in the german-package but when I try to close quote, I get \\glqq again. Any idea what\'s wrong here? TIA, Sebastian |
From: Paulo <vim...@so...> - 2004-08-16 18:48:09
|
Hi ppl, Why I can\'t type ã on a tex document... :\'( .. How can I remove the map ~a -> \\cite{} ?? Thank you for the help. |
From: Aditya M. <adi...@al...> - 2004-08-14 05:00:04
|
Hello, In the latest version of latex-suite, there is a fixme in function Tex_GrepHelper() line 462: texviewer.vim let mainfname = Tex_GetMainFileName(':p') " If we are already editing the file, then use :split without any " arguments so it works even if the file is modified. " FIXME: If mainfname is being presently edited in another window and " is 'modified', then the second split statement will not work. " We will need to travel to that window and back. if mainfname == expand('%:p') split else exec 'split '.mainfname endif I think that this can be corrected as follows let mainfname = Tex_GerMainFileName(':p') " If mainfname is currently being edited, split if mainfname == expand('%:p') split " if mainfname is open in another window, drop elseif bufwinnr(mainfname) != -1 exec 'drop '.mainfname else exec 'split '.mainfname endif Aditya -- Aditya Mahajan, EECS Systems, University of Michigan http://www.eecs.umich.edu/~adityam || Ph: 7342624008 |
From: Richard K. <vim...@so...> - 2004-08-09 03:18:42
|
The user manual says (in section 3.10.2) that Alt-m inserts \\mathbf{}, but this should apparently be alt-m (which is accurately described in 9.1.2). All default alt-combos work for me in gvim except for alt-i. Any hints to get it to work, short of remapping the combo? Also, none of the alt-combos work for me for command line vime (run either from the console or rxvt). Any tricks to make this work? Thanks! Richard Karnesky |
From: Jacob E. <vim...@so...> - 2004-08-07 00:08:58
|
I\'ve just started using vim-latex, and I\'m having two problems: 1) \\lv refuses to work the way I expect. It always calls xpdf (which I don\'t have installed), even though g:Tex_ViewRule_pdf = \'preview\' and G:Tex_ViewRuleComplete = \'open $*.pdf\'. :!open <filename>.pdf works though. Echo gives the expected value for the variables above. 2) The F9 autocompletion features sound great, but F9 is mapped for expose in os x... can all F9 functions be remapped easily in vim-latex? Thanks for any help you can provide. jacob |
From: Michael H. <vim...@so...> - 2004-07-26 17:03:56
|
Hi, imaps in LookupCharacter(char) tries to delete the entered chars of the shortcut, omitting the first one: \" enough back-spaces to erase the left-hand side; \" -1 for the last character typed: let bs = substitute(strpart(lhs, 1), \".\", \"\\<bs>\", \"g\") This fails if the first character is a multibyte character. The strpart, instead of skipping the whole first character, will only skip the first byte, thus erasing one character to much. A solution for this would be let bs = substitute(substitute(lhs, \'^.\', \'\', \'\'), \".\", \"\\<bs>\", \"g\") The substitute takes care of multibyte characters. Bye Michael |
From: Srinath A. <sr...@fa...> - 2004-07-22 00:49:57
|
On Wed, 21 Jul 2004, Sebastian wrote: > It seems as if ALT-L only works with the first tex-buffer one loads. > In other buffers I get an \"i\" with an accent `, just as in any > non-tex buffer. This was a bug. Its fixed in the latest dev release. Srinath |
From: Sebastian M. <seb...@un...> - 2004-07-21 16:57:49
|
Hi! When using F7 to insert references, the list i can chose from is rather long. Would it be possible to layout it a bit more reasonable? e.g. lexikographically, so that "sec:"- and "fig:"-prefixes stand together. And again: If it's easy to script it myself, please give me a hint. im still a vim-newbie. :-) Sebastian. |
From: Mauricio de A. <vim...@so...> - 2004-07-21 14:04:59
|
If g:Tex_DefaultTargetFormat is defined before loading the .tex file, the mappings for viewing/compiling are not set accordingly. I Adding the following line somewhere in the bottom of main.vim solved this issue for me... call SetTeXTarget(g:Tex_DefaultTargetFormat) I hope it gets included in this great tool. Regards, Mauricio |
From: Sebastian <vim...@so...> - 2004-07-21 13:58:41
|
Im experiencing weird problems with ALT-L: It seems as if ALT-L only works with the first tex-buffer one loads. In other buffers I get an \"i\" with an accent `, just as in any non-tex buffer. |
From: Srinath A. <sr...@fa...> - 2004-07-06 16:45:17
|
On Tue, 6 Jul 2004, Andreas Mendat wrote: > > When I > compile my .tex-file via command line with compile flag \'--src-specials\' (and > when I switch back to gVim and press \'\\lv\') everything works fine. But compiling > from within gVim/Latex-Suite does not. (Compilation works, but no source > specials) > > I tried a modified ftplugin/tex.vim-file as described in > \'latex-suite-quickstart.html\' -- no go. > > Before I set the > \'-src-specials\'-flag in ftplugin/tex/texrc -- no go. > > btw: is it texrc or > texrc.vim? (But I tried both - that is not the point with this problem.) > It should be $RUNTIMEPATH/ftplugin/tex/texrc. However, I still have a feeling that for some reason, your setting for g:Tex_CompileRule_dvi is not taking effect. What does :set makeprg? say when you open a .tex file? It should echo back the value of g:Tex_CompileRule_dvi. If it doesn't, then there's your problem... Another place to try putting the value of g:Tex_CompileRule_dvi would be in your ~/vimfiles/ftplugin/tex.vim. That will hopefully always get sourced... Srinath |
From: Brian K. <vim...@so...> - 2004-07-06 16:40:54
|
The link to the nightly cvs build is broken. Thanks, Brian |
From: Andreas M. <vim...@so...> - 2004-07-06 15:59:15
|
Hi, currently I use the Latex-Suite with gVim 6.2 (with WinXP and MiKTEX). When I compile my .tex-file via command line with compile flag \'--src-specials\' (and when I switch back to gVim and press \'\\lv\') everything works fine. But compiling from within gVim/Latex-Suite does not. (Compilation works, but no source specials) I tried a modified ftplugin/tex.vim-file as described in \'latex-suite-quickstart.html\' -- no go. Before I set the \'-src-specials\'-flag in ftplugin/tex/texrc -- no go. btw: is it texrc or texrc.vim? (But I tried both - that is not the point with this problem.) Ciao and Thanks |