vim-latex-devel Mailing List for Vim-Latex (Page 68)
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: Fabian B. <f.b...@gm...> - 2006-03-24 06:07:48
|
Hi Srinath, * On 23 Mar 2006 * Srinath Avadhanula wrote: > Hi Fabian, > > On 3/23/06, Fabian Braennstroem <f.b...@gm...> wrote: > > > 4. What happens if you go to the ~/.vim/ftplugin/latex-suite directory > > > and type: > > > $python bibtools.py /path/to/bibtex/file > > > You should get a semi-formatted list of all the bibtex entries in > > > the given file. I'd like to know any errors this might generate. > > > > I get: > > > > `--> python bibtools.py /home/fab/HOME/Dissertation/CFD/Projects/Building_airflow/Paper/Ve rgleich_RANS-LES/biballsed.bib > > Traceback (most recent call last): > > File "bibtools.py", line 218, in ? > > bf = BibFile(sys.argv[1]) > > File "bibtools.py", line 165, in __init__ > > self.addfile(f) > > File "bibtools.py", line 180, in addfile > > b = Bibliography('@' + f, self.macros) > > File "bibtools.py", line 83, in __init__ > > raise "Only completely numeral fields can be left unquoted" > > Only completely numeral fields can be left unquoted > > > > Yup... This is most definitely where the problem stems from... It looks > like I was a little too strict in parsing the bibtex file. I relaxed the > parsing a little just now. Could you try replacing bibtools.py with the > following (see attached) version? If this makes things work (i.e you get > a formatted list), could you try if the \cite completion works? I don't > want to do an svn commit because there might still be outstanding > issues. Now, I get: `--> python bibtools.py /home/fab/HOME/Dissertation/CFD/Projects/Building_airflow/Paper/Vergleich_RANS-LES/biballsed.bib Traceback (most recent call last): File "bibtools.py", line 227, in ? bf = BibFile(sys.argv[1]) File "bibtools.py", line 174, in __init__ self.addfile(f) File "bibtools.py", line 189, in addfile b = Bibliography('@' + f, self.macros) File "bibtools.py", line 86, in __init__ value = m.group(2) + mn.group(0) AttributeError: 'NoneType' object has no attribute 'group' I just took a deeper look in my bib file and removed two entries, which had some problems with emacs/auctex' function 'validate bibtex entries'; but it does not change the output. Greetings! Fabian |
From: Srinath A. <sri...@gm...> - 2006-03-24 03:53:32
|
Hi Sebastian, On 3/23/06, Sebastian Menge <seb...@un...> wrote: > Am Donnerstag, den 23.03.2006, 11:04 -0800 schrieb Srinath Avadhanula: > > reported by Tex_ViewLaTeX. So, try > > :! xdvi "file.dvi" & > > from within vim to see what might be happening. This should give you > > a clue. The last command will be the most informative. It should tel= l > > Got it. I am in my homefolder, instead of the folder the tex/dvi file > resides in. Now i think that's a problem with my OS/Desktop. > > Or should latexsuite use the absolute path !? Well, latex-suite at least in my case, does not care about the current directory of vim as long as the DVI file is in the same directory as the tex file being edited. It also figures out the path using the .latexmain file if found.. So something like: $ cd ~/research/phd/ $ vim main.tex :cd /tmp " from within vim \lv " in normal mode. works for me. I hope the sequence of actions I'm describing is clear. > Thanks for the support, latexsuite rocks :-) Thanks :) Srinath |
From: Srinath A. <sri...@gm...> - 2006-03-24 03:03:28
|
Hi Fabian, On 3/23/06, Fabian Braennstroem <f.b...@gm...> wrote: > > 4. What happens if you go to the ~/.vim/ftplugin/latex-suite directory > > and type: > > $python bibtools.py /path/to/bibtex/file > > You should get a semi-formatted list of all the bibtex entries in > > the given file. I'd like to know any errors this might generate. > > I get: > > `--> python bibtools.py /home/fab/HOME/Dissertation/CFD/Projects/Building= _airflow/Paper/Ve = rgleich_RANS-LES/biballsed.bib > Traceback (most recent call last): > File "bibtools.py", line 218, in ? > bf =3D BibFile(sys.argv[1]) > File "bibtools.py", line 165, in __init__ > self.addfile(f) > File "bibtools.py", line 180, in addfile > b =3D Bibliography('@' + f, self.macros) > File "bibtools.py", line 83, in __init__ > raise "Only completely numeral fields can be left unquoted" > Only completely numeral fields can be left unquoted > Yup... This is most definitely where the problem stems from... It looks like I was a little too strict in parsing the bibtex file. I relaxed the parsing a little just now. Could you try replacing bibtools.py with the following (see attached) version? If this makes things work (i.e you get a formatted list), could you try if the \cite completion works? I don't want to do an svn commit because there might still be outstanding issues. Thanks, Srinath |
From: Fabian B. <f.b...@gm...> - 2006-03-23 22:39:22
|
Hi Srinath, * On 23 Mar 2006 * Srinath Avadhanula wrote: > Hi Fabian, > > Glad to see someone testing this :) > > On 3/23/06, Fabian Braennstroem <f.b...@gm...> wrote: > > Hi Srinath, > > > > took a while to test it :-) > > > > * On 02 Mar 2006 * Srinath Avadhanula wrote: > > > [snip] > > > > It does not real work for me. When I press M-c to write > > '\cite{}' and press F9 a buffer '__OUTLINE__' opens up, but > > without any bibtex items; it is empty. The pressing 'f' or > > 'a' I get: > > > > The errors due to pressing 'f' and 'a' are a symptom of the problem that > __OUTLINE__ does not show any bibtex items, which is what the real > problem is. Tex_BibFile is actually a python variable which should be > created via Tex_StartCiteCompletion(). However, it doesn't seem to be. > If its not, in subsequent calls, all hell will break loose. I forgot to mention that after pressing 'f' it takes a while until the 'filter menu' pops up; but this should not be the problem. > > If you are interested in helping debug this: > > 1. Which release of latex-suite are you using? If you are not using the > latest release, please update. Just updated using svn. > > 2. What is the value of: > 1. g:Tex_UsePython 1 > 2. g:Tex_UseCiteCompletionVer2 1 > > 3. When you open up the latex file, what happens when you type: > :echo Tex_FindBibFiles() > This should be a newline seperated list of all the bibtex files found > in the main file. If this is not working, its a source of the error. This works: /home/fab/HOME/Dissertation/CFD/Projects/Building_airflow/Paper/Vergleich_RANS-LES/biballsed.bib > > 4. What happens if you go to the ~/.vim/ftplugin/latex-suite directory > and type: > $python bibtools.py /path/to/bibtex/file > You should get a semi-formatted list of all the bibtex entries in the > given file. I'd like to know any errors this might generate. I get: `--> python bibtools.py /home/fab/HOME/Dissertation/CFD/Projects/Building_airflow/Paper/Ve rgleich_RANS-LES/biballsed.bib Traceback (most recent call last): File "bibtools.py", line 218, in ? bf = BibFile(sys.argv[1]) File "bibtools.py", line 165, in __init__ self.addfile(f) File "bibtools.py", line 180, in addfile b = Bibliography('@' + f, self.macros) File "bibtools.py", line 83, in __init__ raise "Only completely numeral fields can be left unquoted" Only completely numeral fields can be left unquoted Hope this helps! Greetings! Fabian |
From: Sebastian M. <seb...@un...> - 2006-03-23 21:47:29
|
Am Donnerstag, den 23.03.2006, 11:04 -0800 schrieb Srinath Avadhanula: > reported by Tex_ViewLaTeX. So, try > :! xdvi "file.dvi" & > from within vim to see what might be happening. This should give you > a clue. The last command will be the most informative. It should tell Got it. I am in my homefolder, instead of the folder the tex/dvi file resides in. Now i think that's a problem with my OS/Desktop. Or should latexsuite use the absolute path !? Thanks for the support, latexsuite rocks :-) Sebastian. |
From: Srinath A. <sri...@gm...> - 2006-03-23 21:44:59
|
Hi Fabian, Glad to see someone testing this :) On 3/23/06, Fabian Braennstroem <f.b...@gm...> wrote: > Hi Srinath, > > took a while to test it :-) > > * On 02 Mar 2006 * Srinath Avadhanula wrote: > [snip] > > It does not real work for me. When I press M-c to write > '\cite{}' and press F9 a buffer '__OUTLINE__' opens up, but > without any bibtex items; it is empty. The pressing 'f' or > 'a' I get: > The errors due to pressing 'f' and 'a' are a symptom of the problem that __OUTLINE__ does not show any bibtex items, which is what the real problem is. Tex_BibFile is actually a python variable which should be created via Tex_StartCiteCompletion(). However, it doesn't seem to be. If its not, in subsequent calls, all hell will break loose. If you are interested in helping debug this: 1. Which release of latex-suite are you using? If you are not using the latest release, please update. 2. What is the value of: 1. g:Tex_UsePython 2. g:Tex_UseCiteCompletionVer2 3. When you open up the latex file, what happens when you type: :echo Tex_FindBibFiles() This should be a newline seperated list of all the bibtex files found in the main file. If this is not working, its a source of the error. 4. What happens if you go to the ~/.vim/ftplugin/latex-suite directory and type: $python bibtools.py /path/to/bibtex/file You should get a semi-formatted list of all the bibtex entries in the given file. I'd like to know any errors this might generate. Answers to these questions will help me greatly in debugging what might be going wrong. Srinath |
From: Srinath A. <sri...@gm...> - 2006-03-23 19:04:29
|
Hi, On 3/23/06, Sebastian Menge <seb...@un...> wrote: > > Can give some suggestions how to debug it myself? I would like to see > what happens exactly when calling the view function. I guess that xdvi > dies out of some reason and vim/latexsuite doesnt sense that thinking > that > Thanks for offering to debug. Here are suggestions: 1. Put :let g:Tex_Debug =3D 1 in your ~/.vim/ftplugin/tex.vim. And then press \lv. Then type: :call Tex_PrintDebug('comp') This should show a string like: Tex_ViewLaTeX: execString =3D xdvi "file.dvi" & Vim-Latex basically runs this string as: exec 'silent! !'.execString You can try running this without the silent! to see any error messages which might pop up. Type in exactly the string which is reported by Tex_ViewLaTeX. So, try :! xdvi "file.dvi" & from within vim to see what might be happening. This should give you a clue. The last command will be the most informative. It should tell you if the external command has any errors etc. 2. If none of this gives you any new information, you can try as a last resort looking at the Tex_ViewLaTeX() function in ~/.vim/ftplugin/latex-suite/compiler.vim. This is the function invoked when you type \lv. HTH Srinath |
From: Christian E. <bla...@gm...> - 2006-03-23 11:03:15
|
* Srinath Avadhanula on Wednesday, March 22, 2006 at 16:49:48 -0800: > On 3/22/06, Christian Ebert <bla...@gm...> wrote: >> inoremap <buffer> <leader>il <Plug>Tex_InsertItemOnThisLine > > This should be :imap, :inoremap will fail. Oops, sorry typo, because I had experimented after it stopped working. >> to be able to type é. But with first revision from svn I this >> didn't help; I had to do >> >> iunmap <buffer> <M-i> >> >> first to make it work again. > > It looks like you put the :imap command in a file which got sourced > after tex_latexSuite.vim. Indeed, I had it in ~/.vim/after/ftplugin/tex.vim which seemed the logical place: :help after 5. In the "after" directory in your home directory. This is for personal preferences to overrule or add to the distributed defaults or system-wide settings (rarely needed). > latex-suite can only use the hasmapto() > function to check for other maps if they are already created by the time > latex-suite gets sourced. The recommended place to put this > customization is in ~/.vim/ftplugin/tex.vim. Ok, I put it there and it works again. Thanks! Instructing users to put their customizations in the "after" directory probably would have saved you to write that function, but this is getting too anal ;-) c -- _B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html> |
From: Fabian B. <f.b...@gm...> - 2006-03-23 10:59:47
|
Hi Srinath, took a while to test it :-) * On 02 Mar 2006 * Srinath Avadhanula wrote: > Hi, > > On 3/2/06, Fabian Braennstroem <f.b...@gm...> wrote: > > Hi Srinath, > > > > > something like this while accounting for the fact that there could be > > > multiple bibtex files will be a little hard. > > > > little bit late, but as you see, I can wait ... but not too > > long ;-) > > > > :) So I can give you what you want on one condition. There is almost no > documentation for this feature written yet. This means that I am not > ready to make a release yet. But I commited to CVS already, so if you > wish, update to the latest CVS. (See the download section of > vim-latex.sf.net for instructions). Then when you press <F9> after > \cite, you will see a completely different screen. Something like: > > -----------------------------------%<----------------------------------- > Masters [avadhanula:ms:01] > TI "The Design and fabrication of a dynamically tuned {MFI} thorax" > AU S. Avadhanula > IN In University of California, Berkeley, 2001 > > Conference [avadhanula:icra:02] > TI "Dynamically tuned design of the {MFI} thorax" > AU S. Avadhanula and R. J. Wood and D. Campolo and R. S. Fearing > IN In Proc. IEEE Int. Conf. on Robotics and Automation, 2002 > > Conference [avadhanula:iros:03] > TI "Lift Force improvements for the Micromechanical Flying Insect" > AU S. Avadhanula and R. J. Wood and E. Steltz and J. Yan and R. S. Fearing > IN In IEE Conf. on Intelligent Robots and Systems, 2003 > -----------------------------------%<----------------------------------- > > Note that syntax highlighting will hide some of these. Once in this > screen, you can use <n>, <p> to move back and forth. Press <enter> once > you are on the required entry. To filter, press <f>. This allows you to > specify a "filter". A filter is basically a string like "a ellington". > This filters out all results where the author field matches the string > ellington. (You can ofcourse use partial words). Press <a> to show all > results. You can also sort by pressing <s>. > > Note that this whole functionality although algorithmically stable is > still a little raw around the edges. Unfortunately, I cannot take a look > at this for at least 20 days or so because I am _really_ busy with > something else. > > Oh! You will need Vim with python support builtin to use this. Doing > this in Vim-script would have doubled my work. > > Let me know how it goes. It does not real work for me. When I press M-c to write '\cite{}' and press F9 a buffer '__OUTLINE__' opens up, but without any bibtex items; it is empty. The pressing 'f' or 'a' I get: Error detected while processing function Tex_HandleBibShortcuts: line 37: Traceback (most recent call last): File "<string>", line 1, in ? NameError: name 'Tex_BibFile' is not defined line 38: Traceback (most recent call last): File "<string>", line 1, in ? NameError: name 'Tex_BibFile' is not defined Error detected while processing function Tex_HandleBibShortcuts..Tex_DisplayBibList: line 22: Traceback (most recent call last): File "<string>", line 1, in ? NameError: name 'Tex_BibFile' is not defined (a) all (f) filter (s) sort (n) next (p) previous (q) quit (<CR>) choose Hit ENTER or type command to continue It seems that the Bibtexfile is not found. I include it in the latex code with: \bibliographystyle{plain} %jfm plain, dinat %\bibliography{biballsed} \bibliography{/home/fab/HOME/Dissertation/TeX/Bibliography/biballsed} I tried it with vim 6.3 and vim 7.something. Do you have an idea? Greetings! Fabian |
From: Sebastian M. <seb...@un...> - 2006-03-23 10:58:47
|
Am Mittwoch, den 22.03.2006, 14:05 -0800 schrieb Srinath Avadhanula: > Hi, > > > I switched from Debian to Ubuntu recently. When i start gvim from the > > file-browser (nautilus), "g:call Tex_ViewLaTeX()" (\lv), doesnt do > > anything. When I start gvim from the shell everything works fine. > > > cases, the $PATH variable is different so that in one case, the program > specified by g:Tex_ViewRule_dvi is not found while its found in the > other. > > In your case, I am pretty sure the following should work: > > :let g:Tex_ViewRule_dvi = '/usr/bin/xdvi' > > and then do \lv. If you specify the complete path to your viewer, things > _should_ work. Nope. > > In /usr/share/vim/addons/ftplugin/texrc, I uncommented > > > > " TexLet g:Tex_ViewRuleComplete_dvi = '' > > g:Tex_ViewRuleComplete_dvi is to fix another problem i.e, when your > viewer needs to be called with a custom syntax. I understood that, but default was the empty string, and if I get it right, that overwrites "g:Tex_ViewRule_dvi" !? Anyway, that's OT. > This is a _really_ old version of latex-suite. I would recommend getting > the latest version directly from: > > http://vim-latex.sourceforge.net/index.php?subject=download&title=Download OK, I did so, but that didnt help either. Can give some suggestions how to debug it myself? I would like to see what happens exactly when calling the view function. I guess that xdvi dies out of some reason and vim/latexsuite doesnt sense that thinking that regards, Sebastian. |
From: C. <sev...@ul...> - 2006-03-23 10:04:15
|
On Wed, Mar 22, 2006 at 08:07:45PM -0800, Srinath Avadhanula wrote: > Hi, >=20 > On 3/20/06, S=F8ren Christensen <sev...@ul...> wrote: > > I've tried to create some templates, but I'm not having great succes. > > > [snip] >=20 > This was a combination of a bug in latex-suite and a problem with the > template you have. I fixed the bug in SVN. I'll make a commit sometime > soon. >=20 > In the meanwhile, the problems with the template below are: >=20 > 1. The first line of the template file should be tab separated. The > template file below is basically separated by spaces. I would > consider this a pseudo-bug since this requirement is not documented > anywhere, but I have not yet changed this. >=20 > 2. The template file should _not_ have any indentation. The indentation > is automatically inserted when the template is read in. This happens > in two places in your template. >=20 > With these two fixes in the template and the latest fix from > latex-suite, things seem to work fine for me. Thank you. |
From: Srinath A. <sri...@gm...> - 2006-03-23 04:07:49
|
Hi, On 3/20/06, S=F8ren Christensen <sev...@ul...> wrote: > I've tried to create some templates, but I'm not having great succes. > [snip] This was a combination of a bug in latex-suite and a problem with the template you have. I fixed the bug in SVN. I'll make a commit sometime soon. In the meanwhile, the problems with the template below are: 1. The first line of the template file should be tab separated. The template file below is basically separated by spaces. I would consider this a pseudo-bug since this requirement is not documented anywhere, but I have not yet changed this. 2. The template file should _not_ have any indentation. The indentation is automatically inserted when the template is read in. This happens in two places in your template. With these two fixes in the template and the latest fix from latex-suite, things seem to work fine for me. Srinath |
From: Aethon <ae...@gm...> - 2006-03-23 01:04:17
|
On 3/22/06, Srinath Avadhanula <sri...@gm...> wrote: > > Version of latexsuite as reported by synaptic: 0.20041219-2 > > Version of vim: 6.4.6 > > > This is a _really_ old version of latex-suite. That is actually the version that Debian has packaged[1]. The package is currently up for adoption, waiting for someone who knows what they are doing to take over. Ubuntu has inherited the package straight from Debian, out of date as it is. [1] http://packages.qa.debian.org/v/vim-latexsuite.html |
From: Srinath A. <sri...@gm...> - 2006-03-23 00:49:55
|
Hi, On 3/22/06, Christian Ebert <bla...@gm...> wrote: > Hello *, > > Yes, I know it's a FAQ: > > inoremap <buffer> <leader>il <Plug>Tex_InsertItemOnThisLine This should be :imap, :inoremap will fail. > > to be able to type =E9. But with first revision from svn I this > didn't help; I had to do > > iunmap <buffer> <M-i> > > first to make it work again. > It looks like you put the :imap command in a file which got sourced after tex_latexSuite.vim. latex-suite can only use the hasmapto() function to check for other maps if they are already created by the time latex-suite gets sourced. The recommended place to put this customization is in ~/.vim/ftplugin/tex.vim. > From the logs I guess it has to do with r899, but I don't > understand whether this considered as fixed or bug. > It works for me. If I put imap <buffer> <leader>il <Plug>Tex_InsertItemOnThisLine in my ~/.vimrc, then I can type <M-i> without invoking the mapping (it inserts a e-acute character). Srinath |
From: Srinath A. <sri...@gm...> - 2006-03-22 22:05:37
|
Hi, > I switched from Debian to Ubuntu recently. When i start gvim from the > file-browser (nautilus), "g:call Tex_ViewLaTeX()" (\lv), doesnt do > anything. When I start gvim from the shell everything works fine. > I do not have access to Ubuntu right now, but a guess is that in the two cases, the $PATH variable is different so that in one case, the program specified by g:Tex_ViewRule_dvi is not found while its found in the other. In your case, I am pretty sure the following should work: :let g:Tex_ViewRule_dvi =3D '/usr/bin/xdvi' and then do \lv. If you specify the complete path to your viewer, things _should_ work. > In /usr/share/vim/addons/ftplugin/texrc, I uncommented > > " TexLet g:Tex_ViewRuleComplete_dvi =3D '' g:Tex_ViewRuleComplete_dvi is to fix another problem i.e, when your viewer needs to be called with a custom syntax. > > Version of latexsuite as reported by synaptic: 0.20041219-2 > Version of vim: 6.4.6 > This is a _really_ old version of latex-suite. I would recommend getting the latest version directly from: http://vim-latex.sourceforge.net/index.php?subject=3Ddownload&title=3DDownl= oad Srinath |
From: Christian E. <bla...@gm...> - 2006-03-22 20:24:45
|
Hello *, Yes, I know it's a FAQ: inoremap <buffer> <leader>il <Plug>Tex_InsertItemOnThisLine to be able to type é. But with first revision from svn I this didn't help; I had to do iunmap <buffer> <M-i> first to make it work again. From the logs I guess it has to do with r899, but I don't understand whether this considered as fixed or bug. c -- _B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html> |
From: Sebastian M. <seb...@un...> - 2006-03-22 13:09:39
|
Hi all I switched from Debian to Ubuntu recently. When i start gvim from the file-browser (nautilus), "g:call Tex_ViewLaTeX()" (\lv), doesnt do anything. When I start gvim from the shell everything works fine. In /usr/share/vim/addons/ftplugin/texrc, I uncommented " TexLet g:Tex_ViewRuleComplete_dvi = '' But that didnt help. Version of latexsuite as reported by synaptic: 0.20041219-2 Version of vim: 6.4.6 Any suggestions? Regards, Sebastian. |
From: Srinath A. <sri...@gm...> - 2006-03-21 19:39:54
|
Hi, On 3/21/06, Javier Rojas <jer...@gm...> wrote: > the last thing can be translated as "permission denied". I guess that so= me > files need exec permission in the repository, after all > Thanks for catching this. I use vim+python so that outline.py is imported as a module rather than used as an executable. I really recommend using vim+python for latex-suite, becase the \cite completion is hugely better when you use vim with +python. Its pretty easy to get. I beleive that almost all the distributions out there offer vim+python packages (I know ubuntu/debian does). Also, vim is really easy to compile with python support. Infact, there are guys who offer the latest vim snapshot with python support builtin. For example, the cream project: http://cream.sf.net offers such a distribution. Basically, |+python| enables you to script vim with python, which is a huge win for lots of things. Srinath |
From: Javier R. <jer...@gm...> - 2006-03-21 16:26:23
|
> I've moved the development of vim-latex from CVS to SVN. This is to > avoid the really crappy anonymous pserver of sourceforge. I also took > this chance to do some general maintainance. Cool, SVN rules :). But now when I attempt to use \ref completion, instead of getting the list of references I get the message /bin/bash: /home/jerojasro/.vim/ftplugin/latex-suite/outline.py: Permiso denegado the last thing can be translated as "permission denied". I guess that some files need exec permission in the repository, after all Greets Javier Rojas |
From: Srinath A. <sri...@gm...> - 2006-03-21 06:08:55
|
Hi, I've moved the development of vim-latex from CVS to SVN. This is to avoid the really crappy anonymous pserver of sourceforge. I also took this chance to do some general maintainance. I've worked on several bugs in the last couple of days. I've made a new release with these changes. If you want to keep up to date with svn, use svn co https://svn.sourceforge.net/svnroot/vim-latex/trunk/vimfiles vimfile= s Do use the full path to the svn repo otherwise you'll checkout all sorts of extra things which are part of the overall vim-latex repo. Srinath |
From: Javier R. <jer...@gm...> - 2006-03-20 21:42:00
|
Hi, I was using bibtex for the bibliographical references, and the <F9> complet= ion=20 wasn't working at all. Until I realized that I was calling the database fil= e=20 with \bibliography{db.bib} instead of=20 \bibliography{db} with the latter, the autocompletion worked. But I got my references well in= =20 both cases. I know is a nuisance (because I could perfectly take care of=20 writing the database name without the extension), but wouldn't it be possib= le=20 to check for the existence of the file considering both cases, with and=20 without the extension? =2D-=20 Javier Rojas Clave GPG: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xA1C57061 |
From: C. <sev...@ul...> - 2006-03-20 14:46:17
|
I've tried to create some templates, but I'm not having great succes. I've made this one: file: prediken.tex =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D <+ +> !comp! !exe! % File: !comp!expand("%:p:t")!comp! % \documentclass[danish,a5paper,12pt]{memoir} \input{prk-pream} \begin{document} \begin{center} \fbox{\parbox{0.95\textwidth}{% {\large Pr=E6diken til \textbf{<+dagens navn+>}} \vspace{0.5\onelineskip} <+dato+>: <+sted1+> kl. \kl{<++>}{<++>} og <+sted2+> kl. \kl{<++>}{<++>} \vspace{0.5\onelineskip} Tekster: \emph{<+1. l=E6sning+>; <+2. l=E6sning+>; <+Evangelium+>} Salmer: \emph{<+1.+>}, \emph{<+2.+>}, \emph{<+3.+>} --- \emph{<+4.+>}, \e= mph{<+5.+>}}} \end{center} \thispagestyle{empty} \begin{quote} <++> \end{quote} <++> % -- Afslutning -- \begin{center} %\lovogtak %\aerevaere \end{center} \end{document} =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Which was initially made with the articletemplate, part of the latex-suite. When I try to use this template, as follows: Calling vim to edit a new file: test-prk.test Then i use the command :TTemplate Chose my template prediken and the result is this: file: test-prk.tex =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ggVGzO+dagens navn+>}} \vspace{0.5\onelineskip} <+dato+>: <+sted1+> kl. \kl{<++>}{<++>} og <+sted2+> kl. \kl{<++>}{<+= +>} \vspace{0.5\onelineskip} Tekster: \emph{<+1. l=E6sning+>; <+2. l=E6sning+>; <+Evangelium+>} Salmer: \emph{<+1.+>}, \emph{<+2.+>}, \emph{<+3.+>} --- \emph{<+4.+>}= , \emph{<+5.+>}}} \end{center} \thispagestyle{empty} \begin{quote} <++> \end{quote} <++> % -- Afslutning -- \begin{center} %\lovogtak %\aerevaere \end{center} \end{document} =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I get this "error-message": ::call histdel("/", -1)|let @/=3Dg:Tex_LastSearchPattern What does that mean, and what do I do wrong? Best regards Severino |
From: Max H. <max...@we...> - 2006-03-19 20:16:19
|
Hello, I just started using the latex-suite seriously and am pretty impressed so far. However there is a little disturbing quirk: Whenever I compile my TeX file I am prompted two times by vim until the file is completely done. I have my .vimrc quoted below and yes I have to compile with those dependencies since I am working with pstricks a lot and dvi doesn't get all things correctly. I am using Ubuntu 5.10 with vim 6.3 and vim-latexsuite .20041219-2 So how do I get those prompts out of the way and increase productivity? Best regards, Max Hoffmann. $cat .vimrc set autowrite syntax on set autoindent set smartindent set showmatch set incsearch "latexsuite plugin filetype plugin on filetype indent on set sw=2 set iskeyword+=: "let g:Tex_Env_theorem "\\pspicture(0,0)(,)(,)\<CR>\<CR>\\endpspicture" let g:Tex_DefaultTargetFormat='pdf' let g:Tex_CompileRule='latex $*' let g:Tex_CompileRule_ps='dvips -Ppdf -o $*.ps $*.dvi' let g:Tex_CompileRule_pdf='ps2pdf $*.ps' let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf' let g:Tex_IgnoredWarnings=' \"Underfull\n". \"Overfull\n". \"specifier changed to\n". \"You have requested\n". \"Missing number, treated as zero.\n". \"There were undefined references\n". \"Citation %.%# undefined\n" \"Unused global option"' augroup MyIMAPs au! au VimEnter * call IMAP('FIG',"\\begin{figure}[h]\\begin{center}\<CR>< ++>\<CR>\\caption{<++>}\<CR>\\end{center}\\end{figure}\<CR><++>",'tex') augroup END -- Max Hoffmann <max...@we...> |
From: Srinath A. <sri...@gm...> - 2006-03-06 18:51:22
|
Hi, On 3/6/06, Cristian Rigamonti <cr...@li...> wrote: > Hi, I've got several abbreviations in my .vimrc such as > > ia zzz Whatever > > If in latex-suite I type "z " (a single "z" followed by a space), vim pri= nts the > RHS of my abbreviation (i.e. "Whatever")! > I can reproduce this. I'll work on it as soon as I get time. Thanks, Srinath |
From: Cristian R. <cr...@li...> - 2006-03-06 08:34:25
|
Hi, I've got several abbreviations in my .vimrc such as ia zzz Whatever If in latex-suite I type "z " (a single "z" followed by a space), vim print= s the RHS of my abbreviation (i.e. "Whatever")! Some notes: - The problem arises also when I type z' z' z? z=3D z^ z* z[ (and maybe oth= er "z+special character" combinations) - The problem arises also if the LHS of my abbreviation is "zzzz", or "zz" - If I have many "similar" abbreviations in .vimrc, such as: =20 ia zzz1 First one ia zzz2 Second one ia zzz Whatever when I type "z ", I get the following output: Whatever i zzz2 Second one i zzz1 First one (i.e. the expansion of the last abbreviation, and the _definition_ of the previous ones!) The order of the definitions in .vimrc is relevant, since if I have =20 ia zzz Whatever ia zzz1 Another one ia zzz2 The last one I only get "Whatever", without the other definitions. - The problem stays if I change the UNIX locale - The problem disappears if I let g:Imap_FreezeImap=3D1 I'm using the latest tar.gz package on vim 6.4 (Debian unstable). If you need any help to figure this out just let me know. Cri --=20 GPG/PGP Key-Id 0x943A5F0E - http://www.linux.it/~cri/cri.asc |