vim-latex-devel Mailing List for Vim-Latex (Page 18)
Brought to you by:
srinathava,
tmaas
Menu
▾
▴
vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project
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: Ted P. <te...@te...> - 2012-05-23 17:30:30
|
> let g:Tex_ViewRule_pdf = 'zathura $*/tmp' Do you mean: let g:Tex_ViewRule_pdf = 'zathura /tmp/$*' ? Did you try that? --Ted -- Ted Pavlic <te...@te...> |
|
From: Ted P. <te...@te...> - 2012-05-23 17:29:37
|
Hm. I wonder if a space is being added. Have you tried using: Tex_ViewRuleComplete_format instead? See: :help Tex_ViewRuleComplete_format I have a feeling that that will be your answer. Best -- Ted On Wed, May 23, 2012 at 1:16 PM, Marijan Svalina <mar...@gm...> wrote: > Just tried that, and also no luck :/ > > > On Wed, May 23, 2012 at 7:08 PM, Ted Pavlic <te...@te...> wrote: >> >> > let g:Tex_ViewRule_pdf = 'zathura $*/tmp' >> >> Do you mean: >> >> let g:Tex_ViewRule_pdf = 'zathura /tmp/$*' >> >> ? Did you try that? >> >> --Ted >> >> -- >> Ted Pavlic <te...@te...> > > > > > -- > http://www.google.com/profiles/marijan.svalina -- Ted Pavlic <te...@te...> |
|
From: Marijan S. <mar...@gm...> - 2012-05-23 17:16:53
|
Just tried that, and also no luck :/ On Wed, May 23, 2012 at 7:08 PM, Ted Pavlic <te...@te...> wrote: > > let g:Tex_ViewRule_pdf = 'zathura $*/tmp' > > Do you mean: > > let g:Tex_ViewRule_pdf = 'zathura /tmp/$*' > > ? Did you try that? > > --Ted > > -- > Ted Pavlic <te...@te...> > -- http://www.google.com/profiles/marijan.svalina |
|
From: Marijan S. <mar...@gm...> - 2012-05-23 12:35:35
|
Hi to all, first of all I just want to thank you for great vim latex plugin. I have a problem with setting right path for Tex_ViewRule_pdf after modifying let g:Tex_CompileRule_pdf = 'pdflatex -output-directory=/tmp -interaction=nonstopmode $* calling \lv wont automaticly open .pdf because it searchs it home dir rather then in /tmp I tryed this options, but nothing works: let g:Tex_ViewRule_pdf = 'zathura' let g:Tex_ViewRule_pdf = 'zathura $*/tmp' let g:Tex_ViewRule_pdf = 'zathura -d /tmp' let g:Tex_ViewRuleComplete_pdf = 'zathura $*/tmp/ &' I appreciate any help. Ty, Marijan Svalina -- http://www.google.com/profiles/marijan.svalina |
|
From: Peter V. <mai...@pe...> - 2012-05-20 11:39:32
|
Hi Filip, If you have something like this i your vimrc set grepprg=grep\ -nH\ $* let g:tex_flavor='latex' let g:Tex_DefaultTargetFormat = 'pdf' let g:Tex_ViewRule_pdf = 'okular' let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode $*' and have a ...synctex.gz (this is the file with all information needed for forward searching) file in your project folder after compiling the document, I have no clue why forward search would not work. I use Okular version 0.14.2. Sorry if I cant help you more. Peter On Thu, May 17, 2012 at 4:46 PM, Filip Kadlec <ka...@fz...> wrote: > Dear Peter, > > thanks so much for your description. I have updated vim-latex to the latest > version; installed and activated pathogen, un-installed the distribution > system-wide vim-latex, and then installed the latest vim-latex: > > ~>cd ~/.vim/bundle > > ~/.vim/bundle> git clone > git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex > Cloning into vim-latex... > remote: Counting objects: 4161, done. > remote: Compressing objects: 100% (1469/1469), done. > remote: Total 4161 (delta 2718), reused 4045 (delta 2665) > Receiving objects: 100% (4161/4161), 1003.90 KiB | 774 KiB/s, done. > Resolving deltas: 100% (2718/2718), done. > > After restarting vim, the scripts appear to be active; :scriptnames > provides: > > ... > 18: /home/kadlecf/.vim/bundle/vim-latex/plugin/SyntaxFolds.vim > 19: /home/kadlecf/.vim/bundle/vim-latex/plugin/filebrowser.vim > 20: /home/kadlecf/.vim/bundle/vim-latex/plugin/imaps.vim > 21: /home/kadlecf/.vim/bundle/vim-latex/plugin/libList.vim > 22: /home/kadlecf/.vim/bundle/vim-latex/plugin/remoteOpen.vim > ... > > Also, \ll and \lv work as expected. Alas, \ls still does not work. It only > states: > :call Tex_ForwardSearchLaTeX() > > but the okular window does not open. The situation is the same if I source > the files you sent in the previous post. Not sure if I am not doing > something wrong... > > With best regards, > > Filip > > > On Thu, 17 May 2012, Peter Vasil wrote: >> >> On Thu, May 17, 2012 at 1:00 PM, Filip Kadlec <ka...@fz...> wrote: >>> >>> Peter, >>> thanks for your reply. >>> >>> Having sourced the lines below into vim, there is some progress. Now, >>> when I >>> type \ls , three new okular instances will open; one contains the >>> compiled >>> file while the other two are empty. Each provides an error box, like >>> this: >>> >>> Could not open /home/kadlecf/Documents/path/file.tex and >>> Could not open /home/kadlecf/Documents/path/40 >>> >>> where 40 corresponds to the current line in the .tex source. >> >> This could be the thing with the old version of vim-latex. I just can >> say for the latest vim-latex version from the git-repository that >> forward search works because I made some fixes regarding okular which >> then went into the vim-latex source. Which vim-latex version do you >> use? >> >>> >>> Concerning the option "-synctex=1", sorry for my ignorance, but I don't >>> know >>> where to set it. What exactly does it influence? >> >> If you have put all lines in your vimrc which I posted in my previous >> email, then the synctex option is already there. This option generates >> the necessary data for forward search. Without this option forward >> search doesn't work and not only in vim-latex. All latex editors use >> the synctex option for forward search. >> >>> >>> Also, I would be ready to install the latest version using the >>> git-repository, but I do not know how to proceed... >> >> I use vim-pathogen [1] for managing my vim plugins. Simply clone the >> vim-latex repository into the bundle directory. >> If you read [1] then you will probably know what I mean with the >> bundle directory. >> The clone command is: >> git clone git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex >> >> You could also clone the repoository and copy all files manually to >> ~/.vim/ folder. There is also some help on the vim-latex download page >> [2], where to put all files. But the description is without the >> pathogen plugin. >> >> [1]: http://www.vim.org/scripts/script.php?script_id=2332 >> [2]: http://vim-latex.sourceforge.net/index.php?subject=download >> >> >> Hope this helps, >> Peter >> >> >>> >>> Filip >>> >>> >>> On Thu, 17 May 2012, Peter Vasil wrote: >>> >>>> Hi, >>>> >>>> I use vim-latex with okular and forward search works like a charm. >>>> >>>> I have this in my .vimrc >>>> >>>> set grepprg=grep\ -nH\ $* >>>> let g:tex_flavor='latex' >>>> let g:Tex_DefaultTargetFormat = 'pdf' >>>> let g:Tex_ViewRule_pdf = 'okular' >>>> let g:Tex_CompileRule_pdf = "/usr/local/bin/latexmk -e >>>> '$pdflatex=q/pdflatex -interaction=nonstopmode -file-line-error >>>> -halt-on-error -synctex=1/' -pdf -bibtex $*" >>>> >>>> I use latexmk for compilation and you have to set "-synctex=1" >>>> somewhere in the compile rules. >>>> >>>> Also, did you try to use the latest vim-latex from the git repository? >>>> I dont know which version is in the OpenSUSE repositories but okular >>>> forward search is working with the latest vim-latex version from the >>>> git repository. >>>> >>>> Peter >>>> >>>> >>>> On Thu, May 17, 2012 at 11:40 AM, Filip Kadlec <ka...@fz...> wrote: >>>>> >>>>> >>>>> Hello, >>>>> I would appreciate if someone could help me to resolve this problem. >>>>> >>>>> I have installed vim-latex from the OpenSuSE distribution. Most of its >>>>> features work correctly. \ll will start latex translation, and \lv >>>>> launches the viewer. However, \ls , instead of launching the forward >>>>> search, does nothing. I have tried to make it work by entering, in vim: >>>>> >>>>> :let g:Tex_CompileRule_dvi = 'let'atex -src-specials >>>>> -interaction=nonstopmode $*' ' >>>>> >>>>> and >>>>> >>>>> TCTarget dvi >>>>> >>>>> as found in the FAQ. However, this does not help. I understand from the >>>>> mailing list there were some quite recent patches to this behavior, >>>>> also >>>>> in order to get a single instance of okular, but I am not sure how it >>>>> is >>>>> best to proceed. >>>>> >>>>> Thanks in advance for your assistance. >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Live Security Virtual Conference >>>>> Exclusive live event will cover all the ways today's security and >>>>> threat landscape has changed and how IT managers can respond. >>>>> Discussions >>>>> will include endpoint security, mobile security and the latest in >>>>> malware >>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>> _______________________________________________ >>>>> Vim-latex-devel mailing list >>>>> Vim...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Live Security Virtual Conference >>>> Exclusive live event will cover all the ways today's security and threat >>>> landscape has changed and how IT managers can respond. Discussions will >>>> include endpoint security, mobile security and the latest in malware >>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>> _______________________________________________ >>>> Vim-latex-devel mailing list >>>> Vim...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Vim-latex-devel mailing list >>> Vim...@li... >>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >>> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and threat >> landscape has changed and how IT managers can respond. Discussions will >> include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
|
From: Filip K. <ka...@fz...> - 2012-05-17 14:46:33
|
Dear Peter, thanks so much for your description. I have updated vim-latex to the latest version; installed and activated pathogen, un-installed the distribution system-wide vim-latex, and then installed the latest vim-latex: ~>cd ~/.vim/bundle ~/.vim/bundle> git clone git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex Cloning into vim-latex... remote: Counting objects: 4161, done. remote: Compressing objects: 100% (1469/1469), done. remote: Total 4161 (delta 2718), reused 4045 (delta 2665) Receiving objects: 100% (4161/4161), 1003.90 KiB | 774 KiB/s, done. Resolving deltas: 100% (2718/2718), done. After restarting vim, the scripts appear to be active; :scriptnames provides: ... 18: /home/kadlecf/.vim/bundle/vim-latex/plugin/SyntaxFolds.vim 19: /home/kadlecf/.vim/bundle/vim-latex/plugin/filebrowser.vim 20: /home/kadlecf/.vim/bundle/vim-latex/plugin/imaps.vim 21: /home/kadlecf/.vim/bundle/vim-latex/plugin/libList.vim 22: /home/kadlecf/.vim/bundle/vim-latex/plugin/remoteOpen.vim ... Also, \ll and \lv work as expected. Alas, \ls still does not work. It only states: :call Tex_ForwardSearchLaTeX() but the okular window does not open. The situation is the same if I source the files you sent in the previous post. Not sure if I am not doing something wrong... With best regards, Filip On Thu, 17 May 2012, Peter Vasil wrote: > On Thu, May 17, 2012 at 1:00 PM, Filip Kadlec <ka...@fz...> wrote: >> Peter, >> thanks for your reply. >> >> Having sourced the lines below into vim, there is some progress. Now, when I >> type \ls , three new okular instances will open; one contains the compiled >> file while the other two are empty. Each provides an error box, like this: >> >> Could not open /home/kadlecf/Documents/path/file.tex and >> Could not open /home/kadlecf/Documents/path/40 >> >> where 40 corresponds to the current line in the .tex source. > This could be the thing with the old version of vim-latex. I just can > say for the latest vim-latex version from the git-repository that > forward search works because I made some fixes regarding okular which > then went into the vim-latex source. Which vim-latex version do you > use? > >> >> Concerning the option "-synctex=1", sorry for my ignorance, but I don't know >> where to set it. What exactly does it influence? > If you have put all lines in your vimrc which I posted in my previous > email, then the synctex option is already there. This option generates > the necessary data for forward search. Without this option forward > search doesn't work and not only in vim-latex. All latex editors use > the synctex option for forward search. > >> >> Also, I would be ready to install the latest version using the >> git-repository, but I do not know how to proceed... > I use vim-pathogen [1] for managing my vim plugins. Simply clone the > vim-latex repository into the bundle directory. > If you read [1] then you will probably know what I mean with the > bundle directory. > The clone command is: > git clone git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex > > You could also clone the repoository and copy all files manually to > ~/.vim/ folder. There is also some help on the vim-latex download page > [2], where to put all files. But the description is without the > pathogen plugin. > > [1]: http://www.vim.org/scripts/script.php?script_id=2332 > [2]: http://vim-latex.sourceforge.net/index.php?subject=download > > > Hope this helps, > Peter > > >> >> Filip >> >> >> On Thu, 17 May 2012, Peter Vasil wrote: >> >>> Hi, >>> >>> I use vim-latex with okular and forward search works like a charm. >>> >>> I have this in my .vimrc >>> >>> set grepprg=grep\ -nH\ $* >>> let g:tex_flavor='latex' >>> let g:Tex_DefaultTargetFormat = 'pdf' >>> let g:Tex_ViewRule_pdf = 'okular' >>> let g:Tex_CompileRule_pdf = "/usr/local/bin/latexmk -e >>> '$pdflatex=q/pdflatex -interaction=nonstopmode -file-line-error >>> -halt-on-error -synctex=1/' -pdf -bibtex $*" >>> >>> I use latexmk for compilation and you have to set "-synctex=1" >>> somewhere in the compile rules. >>> >>> Also, did you try to use the latest vim-latex from the git repository? >>> I dont know which version is in the OpenSUSE repositories but okular >>> forward search is working with the latest vim-latex version from the >>> git repository. >>> >>> Peter >>> >>> >>> On Thu, May 17, 2012 at 11:40 AM, Filip Kadlec <ka...@fz...> wrote: >>>> >>>> Hello, >>>> I would appreciate if someone could help me to resolve this problem. >>>> >>>> I have installed vim-latex from the OpenSuSE distribution. Most of its >>>> features work correctly. \ll will start latex translation, and \lv >>>> launches the viewer. However, \ls , instead of launching the forward >>>> search, does nothing. I have tried to make it work by entering, in vim: >>>> >>>> :let g:Tex_CompileRule_dvi = 'let'atex -src-specials >>>> -interaction=nonstopmode $*' ' >>>> >>>> and >>>> >>>> TCTarget dvi >>>> >>>> as found in the FAQ. However, this does not help. I understand from the >>>> mailing list there were some quite recent patches to this behavior, also >>>> in order to get a single instance of okular, but I am not sure how it is >>>> best to proceed. >>>> >>>> Thanks in advance for your assistance. >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Live Security Virtual Conference >>>> Exclusive live event will cover all the ways today's security and >>>> threat landscape has changed and how IT managers can respond. Discussions >>>> will include endpoint security, mobile security and the latest in malware >>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>> _______________________________________________ >>>> Vim-latex-devel mailing list >>>> Vim...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and threat >>> landscape has changed and how IT managers can respond. Discussions will >>> include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Vim-latex-devel mailing list >>> Vim...@li... >>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
|
From: Peter V. <mai...@pe...> - 2012-05-17 14:04:03
|
On Thu, May 17, 2012 at 1:00 PM, Filip Kadlec <ka...@fz...> wrote: > Peter, > thanks for your reply. > > Having sourced the lines below into vim, there is some progress. Now, when I > type \ls , three new okular instances will open; one contains the compiled > file while the other two are empty. Each provides an error box, like this: > > Could not open /home/kadlecf/Documents/path/file.tex and > Could not open /home/kadlecf/Documents/path/40 > > where 40 corresponds to the current line in the .tex source. This could be the thing with the old version of vim-latex. I just can say for the latest vim-latex version from the git-repository that forward search works because I made some fixes regarding okular which then went into the vim-latex source. Which vim-latex version do you use? > > Concerning the option "-synctex=1", sorry for my ignorance, but I don't know > where to set it. What exactly does it influence? If you have put all lines in your vimrc which I posted in my previous email, then the synctex option is already there. This option generates the necessary data for forward search. Without this option forward search doesn't work and not only in vim-latex. All latex editors use the synctex option for forward search. > > Also, I would be ready to install the latest version using the > git-repository, but I do not know how to proceed... I use vim-pathogen [1] for managing my vim plugins. Simply clone the vim-latex repository into the bundle directory. If you read [1] then you will probably know what I mean with the bundle directory. The clone command is: git clone git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex You could also clone the repoository and copy all files manually to ~/.vim/ folder. There is also some help on the vim-latex download page [2], where to put all files. But the description is without the pathogen plugin. [1]: http://www.vim.org/scripts/script.php?script_id=2332 [2]: http://vim-latex.sourceforge.net/index.php?subject=download Hope this helps, Peter > > Filip > > > On Thu, 17 May 2012, Peter Vasil wrote: > >> Hi, >> >> I use vim-latex with okular and forward search works like a charm. >> >> I have this in my .vimrc >> >> set grepprg=grep\ -nH\ $* >> let g:tex_flavor='latex' >> let g:Tex_DefaultTargetFormat = 'pdf' >> let g:Tex_ViewRule_pdf = 'okular' >> let g:Tex_CompileRule_pdf = "/usr/local/bin/latexmk -e >> '$pdflatex=q/pdflatex -interaction=nonstopmode -file-line-error >> -halt-on-error -synctex=1/' -pdf -bibtex $*" >> >> I use latexmk for compilation and you have to set "-synctex=1" >> somewhere in the compile rules. >> >> Also, did you try to use the latest vim-latex from the git repository? >> I dont know which version is in the OpenSUSE repositories but okular >> forward search is working with the latest vim-latex version from the >> git repository. >> >> Peter >> >> >> On Thu, May 17, 2012 at 11:40 AM, Filip Kadlec <ka...@fz...> wrote: >>> >>> Hello, >>> I would appreciate if someone could help me to resolve this problem. >>> >>> I have installed vim-latex from the OpenSuSE distribution. Most of its >>> features work correctly. \ll will start latex translation, and \lv >>> launches the viewer. However, \ls , instead of launching the forward >>> search, does nothing. I have tried to make it work by entering, in vim: >>> >>> :let g:Tex_CompileRule_dvi = 'let'atex -src-specials >>> -interaction=nonstopmode $*' ' >>> >>> and >>> >>> TCTarget dvi >>> >>> as found in the FAQ. However, this does not help. I understand from the >>> mailing list there were some quite recent patches to this behavior, also >>> in order to get a single instance of okular, but I am not sure how it is >>> best to proceed. >>> >>> Thanks in advance for your assistance. >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Vim-latex-devel mailing list >>> Vim...@li... >>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and threat >> landscape has changed and how IT managers can respond. Discussions will >> include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
|
From: Filip K. <ka...@fz...> - 2012-05-17 11:00:16
|
Peter, thanks for your reply. Having sourced the lines below into vim, there is some progress. Now, when I type \ls , three new okular instances will open; one contains the compiled file while the other two are empty. Each provides an error box, like this: Could not open /home/kadlecf/Documents/path/file.tex and Could not open /home/kadlecf/Documents/path/40 where 40 corresponds to the current line in the .tex source. Concerning the option "-synctex=1", sorry for my ignorance, but I don't know where to set it. What exactly does it influence? Also, I would be ready to install the latest version using the git-repository, but I do not know how to proceed... Filip On Thu, 17 May 2012, Peter Vasil wrote: > Hi, > > I use vim-latex with okular and forward search works like a charm. > > I have this in my .vimrc > > set grepprg=grep\ -nH\ $* > let g:tex_flavor='latex' > let g:Tex_DefaultTargetFormat = 'pdf' > let g:Tex_ViewRule_pdf = 'okular' > let g:Tex_CompileRule_pdf = "/usr/local/bin/latexmk -e > '$pdflatex=q/pdflatex -interaction=nonstopmode -file-line-error > -halt-on-error -synctex=1/' -pdf -bibtex $*" > > I use latexmk for compilation and you have to set "-synctex=1" > somewhere in the compile rules. > > Also, did you try to use the latest vim-latex from the git repository? > I dont know which version is in the OpenSUSE repositories but okular > forward search is working with the latest vim-latex version from the > git repository. > > Peter > > > On Thu, May 17, 2012 at 11:40 AM, Filip Kadlec <ka...@fz...> wrote: >> Hello, >> I would appreciate if someone could help me to resolve this problem. >> >> I have installed vim-latex from the OpenSuSE distribution. Most of its >> features work correctly. \ll will start latex translation, and \lv >> launches the viewer. However, \ls , instead of launching the forward >> search, does nothing. I have tried to make it work by entering, in vim: >> >> :let g:Tex_CompileRule_dvi = 'let'atex -src-specials >> -interaction=nonstopmode $*' ' >> >> and >> >> TCTarget dvi >> >> as found in the FAQ. However, this does not help. I understand from the >> mailing list there were some quite recent patches to this behavior, also >> in order to get a single instance of okular, but I am not sure how it is >> best to proceed. >> >> Thanks in advance for your assistance. >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
|
From: Peter V. <mai...@pe...> - 2012-05-17 10:38:10
|
Hi, I use vim-latex with okular and forward search works like a charm. I have this in my .vimrc set grepprg=grep\ -nH\ $* let g:tex_flavor='latex' let g:Tex_DefaultTargetFormat = 'pdf' let g:Tex_ViewRule_pdf = 'okular' let g:Tex_CompileRule_pdf = "/usr/local/bin/latexmk -e '$pdflatex=q/pdflatex -interaction=nonstopmode -file-line-error -halt-on-error -synctex=1/' -pdf -bibtex $*" I use latexmk for compilation and you have to set "-synctex=1" somewhere in the compile rules. Also, did you try to use the latest vim-latex from the git repository? I dont know which version is in the OpenSUSE repositories but okular forward search is working with the latest vim-latex version from the git repository. Peter On Thu, May 17, 2012 at 11:40 AM, Filip Kadlec <ka...@fz...> wrote: > Hello, > I would appreciate if someone could help me to resolve this problem. > > I have installed vim-latex from the OpenSuSE distribution. Most of its > features work correctly. \ll will start latex translation, and \lv > launches the viewer. However, \ls , instead of launching the forward > search, does nothing. I have tried to make it work by entering, in vim: > > :let g:Tex_CompileRule_dvi = 'let'atex -src-specials > -interaction=nonstopmode $*' ' > > and > > TCTarget dvi > > as found in the FAQ. However, this does not help. I understand from the > mailing list there were some quite recent patches to this behavior, also > in order to get a single instance of okular, but I am not sure how it is > best to proceed. > > Thanks in advance for your assistance. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
|
From: Filip K. <ka...@fz...> - 2012-05-17 09:40:26
|
Hello,
I would appreciate if someone could help me to resolve this problem.
I have installed vim-latex from the OpenSuSE distribution. Most of its
features work correctly. \ll will start latex translation, and \lv
launches the viewer. However, \ls , instead of launching the forward
search, does nothing. I have tried to make it work by entering, in vim:
:let g:Tex_CompileRule_dvi = 'let'atex -src-specials
-interaction=nonstopmode $*' '
and
TCTarget dvi
as found in the FAQ. However, this does not help. I understand from the
mailing list there were some quite recent patches to this behavior, also
in order to get a single instance of okular, but I am not sure how it is
best to proceed.
Thanks in advance for your assistance.
|
|
From: Danilo <ge...@gm...> - 2012-05-10 12:23:19
|
Hi Alessandro > :set paste | TTemplate | set nopaste Oh, that looks like a nice workaround :) > I don't know if it qualifies as a bug, i.e. if vim-latex should check > if the paste option is enabled before inserting a template. I think it should, as the functionality of the command is imo not to paste some file into your current buffer, but to load a default template, in which case you don't want to worry about your paste configuration. Danilo |
|
From: Alessandro P. <ale...@la...> - 2012-05-10 08:07:17
|
Hello to you, I don't know if it qualifies as a bug, i.e. if vim-latex should check if the paste option is enabled before inserting a template, but you could work around it by either mapping the following ex command :set paste | TTemplate | set nopaste or by writing a function in your .vimrc, like function LatexTemplate () :set paste :TTemplate :set nopaste endfunction Note that I haven't tested this code, though. You could also put it in a file and load it only for .tex files with an autocommand (see ":help function" in vim). Alessandro -- If God had intended for email to be written in HTML, then the traditional signoff of prayers would be </amen> -- Tom Liston |
|
From: Danilo <ge...@gm...> - 2012-05-10 07:30:55
|
Sorry for the confusion, of course I meant that I enabled auto indentation by default and that paste mode should be enabled before pasting, not disabled :) Danilo On 10.05.2012 09:24, Danilo wrote: > Hi there > > First of all, thanks for your work! But here a little bug(?) report: > > When pasting a template containing indentation using :TTemplate, the > indentation breaks because I enabled paste mode by default. > > Is there a way to disable paste mode before pasting, and to re-enable > the previous setting afterwards? > > http://vim-latex.git.sourceforge.net/git/gitweb.cgi?p=vim-latex/vim-latex;a=blob_plain;f=ftplugin/latex-suite/templates.vim;hb=HEAD > > Danilo |
|
From: Danilo <ge...@gm...> - 2012-05-10 07:24:14
|
Hi there First of all, thanks for your work! But here a little bug(?) report: When pasting a template containing indentation using :TTemplate, the indentation breaks because I enabled paste mode by default. Is there a way to disable paste mode before pasting, and to re-enable the previous setting afterwards? http://vim-latex.git.sourceforge.net/git/gitweb.cgi?p=vim-latex/vim-latex;a=blob_plain;f=ftplugin/latex-suite/templates.vim;hb=HEAD Danilo |
|
From: SourceForge.net <no...@so...> - 2012-04-26 02:57:50
|
Bugs item #3521476, was opened at 2012-04-25 19:57 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3521476&group_id=52322 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: naught101 () Assigned to: Nobody/Anonymous (nobody) Summary: \citeauthor and \citeyear not recognised as citation command Initial Comment: This is mostly a problem with the tex ftplugin, I think: if I type \citeyear{citation_99}, then only the first five characters are correctly hilighted - the remainder are not hilighted, and the underscores in the citation key show up with error hilighting. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3521476&group_id=52322 |
|
From: Alessandro P. <ale...@la...> - 2012-04-17 07:38:02
|
Actually, I was hoping the developers used the sourceforge bugtracker more than they seem to be using this maling list. You can try opening a new topic with subject starting with something like "Bug report:". You're welcome. Alessandro -- If God had intended for email to be written in HTML, then the traditional signoff of prayers would be </amen> -- Tom Liston |
|
From: Alex X. A. S. <ber...@gm...> - 2012-04-17 03:10:29
|
Alright, I'll submit bug report, but I'm not sure how. From the project's page: http://vim-latex.sourceforge.net/index.php?subject=contact&title=Contact it's said bugs should be reported on this mailing list, but how? Just open a new topic and report the bug? Thanks for helping. On 17 April 2012 01:50, Alessandro Pezzoni <ale...@la...>wrote: > > Gred's solution worked for me. > > I'm sorry. I was still a bit dizzy this morning and thought that > Gerd's solution was your reply to my question. > I never had to do with .cls or .lco files, but if they they are latex > files and are in latex-suite's scope, maybe you could file a bug > report to include those autocmds (it has one for .sty files). > > Best regards, > Alessandro > > -- > If God had intended for email to be written in HTML, then the > traditional signoff of prayers would be </amen> -- Tom Liston > > -- Terima Kasih, Alex Xandra Albert Sim |
|
From: Alessandro P. <ale...@la...> - 2012-04-16 18:50:55
|
> Gred's solution worked for me. I'm sorry. I was still a bit dizzy this morning and thought that Gerd's solution was your reply to my question. I never had to do with .cls or .lco files, but if they they are latex files and are in latex-suite's scope, maybe you could file a bug report to include those autocmds (it has one for .sty files). Best regards, Alessandro -- If God had intended for email to be written in HTML, then the traditional signoff of prayers would be </amen> -- Tom Liston |
|
From: Alex X. A. S. <ber...@gm...> - 2012-04-16 08:02:12
|
Gred's solution worked for me. I'm not sure how, but I just copy paste his filetype.vim to my $HOME/vimfiles/ and it works! Thanks everyone. On 16 April 2012 14:38, Alessandro Pezzoni <ale...@la...>wrote: > > I've put > > > > augroup filetypedetect > > " Some LaTeX types > > au! BufRead,BufNewFile *.cls setfiletype tex > > au! BufRead,BufNewFile *.lco setfiletype tex > > augroup END > > > > in my ".vim/filetype.vim" and > > > > syntax on > > filetype plugin on > > > > in my ".vimrc". > > Then I'm at a loss... does latex-suite get loaded if you open one of > those files and manually set the filetype? If it does, than probably > those lines aren't executed. > For what it's worth, I've tested that autocmd on my machine and it works > fine. > > Alessandro > > -- > If God had intended for email to be written in HTML, then the > traditional signoff of prayers would be </amen> -- Tom Liston > > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > -- Terima Kasih, Alex Xandra Albert Sim |
|
From: Alessandro P. <ale...@la...> - 2012-04-16 07:38:51
|
> I've put > > augroup filetypedetect > " Some LaTeX types > au! BufRead,BufNewFile *.cls setfiletype tex > au! BufRead,BufNewFile *.lco setfiletype tex > augroup END > > in my ".vim/filetype.vim" and > > syntax on > filetype plugin on > > in my ".vimrc". Then I'm at a loss... does latex-suite get loaded if you open one of those files and manually set the filetype? If it does, than probably those lines aren't executed. For what it's worth, I've tested that autocmd on my machine and it works fine. Alessandro -- If God had intended for email to be written in HTML, then the traditional signoff of prayers would be </amen> -- Tom Liston |
|
From: Gerd W. <ger...@ma...> - 2012-04-16 07:07:18
|
In my personal copy of the latex-suite (https://github.com/gerw/vim-latex-suite) I used the following change in ftplugin/latex-suite/texviewer.vim to avoid those empty buffers. Regards Gerd @@ -855,7 +856,8 @@ function! Tex_FindBibFiles() call Tex_Debug(":Tex_FindBibFiles: ", "view") let mainfname = Tex_GetMainFileName(':p') - exec 'new ' . fnameescape(mainfname) + split + exec 'silent! e '.fnameescape(mainfname) if search('\\\(no\)\?bibliography{', 'w') On 02/23/2012 11:49 AM, Peter Vasil wrote: > Ok, found out that the empty buffers are not generated from compiling. > > The empty buffers appear after opening quickfix window for cite completion. > > Peter > > On Sat, Feb 11, 2012 at 4:02 PM, Peter Vasil > <mai...@pe...> wrote: >> It is strange, but I can't reproduce the problem anymore. Somehow the >> compilation doesn't create empty buffers anymore. Maybe it was some >> other setting which caused this. And yes I always create a file which >> has .latexmain as extension. i.e if my main file is main.tex then I >> create a file which is called main.tex.latexmain and everything works. >> >> Sorry for the noise, but the empty buffers were quite annoying. >> >> Peter >> >> >> On Wed, Feb 8, 2012 at 9:45 PM, Ted Pavlic<te...@te...> wrote: >>> Peter -- >>> >>> Can you give a minimal working example? >>> >>> Also, let's say you have a file called: >>> >>> test.tex >>> >>> and you created a latexmain called: >>> >>> test.latexmain >>> >>> It is known that Vim-LaTeX will create an empty buffer called "test." To >>> get around this, name your latexmain: >>> >>> test.tex.latexmain >>> >>> This is the name that Vim-LaTeX expects. It just happens that getting >>> rid of the "tex" mostly works... >>> >>> --Ted >>> >>> On 01/27/2012 06:58 AM, Peter Vasil wrote: >>>> Hi, >>>> >>>> I dont know if its just me but compilation creates an empty buffer >>>> with the same name as the .tex file I compile. >>>> >>>> Peter >>>> >>>> ------------------------------------------------------------------------------ >>>> Try before you buy = See our experts in action! >>>> The most comprehensive online learning library for Microsoft developers >>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >>>> Metro Style Apps, more. Free future releases when you subscribe now! >>>> http://p.sf.net/sfu/learndevnow-dev2 >>>> _______________________________________________ >>>> Vim-latex-devel mailing list >>>> Vim...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >>> >>> -- >>> Ted Pavlic<te...@te...> > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
|
From: Gerd W. <ger...@ma...> - 2012-04-16 07:06:42
|
I've put augroup filetypedetect " Some LaTeX types au! BufRead,BufNewFile *.cls setfiletype tex au! BufRead,BufNewFile *.lco setfiletype tex augroup END in my ".vim/filetype.vim" and syntax on filetype plugin on in my ".vimrc". Best Regards Gerd On 04/11/2012 10:47 AM, Alessandro Pezzoni wrote: > I'm not sure exactly. I had an issue where .sty files were assigned > filetype "tex", but I didn't get any syntax highlighting. I had the > "filetype plugin on" instruction in a separate rc file, which was > sourced in my vimrc, after an autocommand for the "tex" filetype. > Putting that line before the autocommand fixed my issue. > > Hope this helps, > Alessandro > |
|
From: Alessandro P. <ale...@la...> - 2012-04-11 08:47:35
|
I'm not sure exactly. I had an issue where .sty files were assigned filetype "tex", but I didn't get any syntax highlighting. I had the "filetype plugin on" instruction in a separate rc file, which was sourced in my vimrc, after an autocommand for the "tex" filetype. Putting that line before the autocommand fixed my issue. Hope this helps, Alessandro -- If God had intended for email to be written in HTML, then the traditional signoff of prayers would be </amen> -- Tom Liston |
|
From: Alex X. A. S. <ber...@gm...> - 2012-04-11 08:19:04
|
Yes, I put the "filetype plugin on" but somehow it doesn't work. What should I check? On 8 April 2012 14:14, Alessandro Pezzoni <ale...@la...>wrote: > Hello, > did you put "filetype plugin on" before any autocmd in your .vimrc? > > Alessandro > > -- > If God had intended for email to be written in HTML, then the > traditional signoff of prayers would be </amen> -- Tom Liston > > -- Terima Kasih, Alex Xandra Albert Sim |
|
From: Alessandro P. <ale...@la...> - 2012-04-11 08:15:42
|
I never did but I think you should have a look at the "Handling dependencies in compilation" manual section [1], which describes how to chain multiple compilation formats. In your case I think you should do something like this: let g:Tex_DefaultTargetFormat = 'pdf' let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf' let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*' let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi' let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps' Regards, Alessandro 1: http://vim-latex.sourceforge.net/documentation/latex-suite/compiler-dependency.html -- If God had intended for email to be written in HTML, then the traditional signoff of prayers would be </amen> -- Tom Liston |
34 messages has been excluded from this view by a project administrator.
