[Vim-latex-devel] Forward search with okular

[Filip Kadlec]

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-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Forward search with okular

[Filip Kadlec]

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.texand
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  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-latex-devel@lists.sourceforge.net
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-latex-devel@lists.sourceforge.net
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-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Forward search with okular

[Filip Kadlec]

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  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  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 insta

Re: [Vim-latex-devel] Forward search with okular

[Filip Kadlec]

Hello Peter,

 I think the problem is resolved now. The clue was in the line:
let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode $*'

instead of which I had

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 
$*"

coming from one of your posts. I think the synctex option was missing 
most. Now the forward search works.


Though, I had one more problem: both the forward and backward searches 
always launched a new instance of viewer / gvim. To resolve this, I have 
searched some older mailing list archives and modified my .vimrc lines as 
follows:


let g:Tex_ViewRule_pdf = 'okular --unique'
let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode $* 
-inverse-search "gvim --servername GVIM --remote +\%l \%f"'

These options enforce the use of already running okular / gvim, hopefully 
this will help somebody. I wonder why these options are not included in 
the latest vim-latex version which I had installed. The only detail still 
remaining is that the windows don't get the KDE focus, I am not sure this 
has a solution.


Filip



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  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  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 repo

Re: [Vim-latex-devel] Pressing "u" only undoes one character at a time

[Filip Kadlec]

Hello Bernhard,

  I don't have a solution to your problem, just want to note that in my
case "u" undoes the whole word (or typing sequence) straight, no
letter-by-letter behavior occurs. My version of vim is 7.3, too. This
works regardless of whether the latex suite is loaded.

Hope this helps, Filip

On Tue, 23 Jul 2013, Bernhard Bliem wrote:

> Hello,
>
> Suppose I start vim, enter insert mode, write the text "foobar" and
> exit insert mode. Then pressing "u" should undo this change, i.e.,
> remove "foobar". This works as expected in "plain" vim, but not after
> vim-latex has been loaded (say when I open a *.tex file and vim
> recognizes that vim-latex needs to be loaded). What happens then is
> that "u" only undoes one character at a time, i.e., it removes only
> "r"; when pressing it again it removes "a", and so on.
>
> To reproduce:
> 1. Start vim and load some *.tex file such that vim-latex is loaded.
> 2. Insert "foobar" somewhere in that buffer.
> 3. Press u.
> (I have tried this with a .vimrc only conaining "filetype plugin on".)
>
> Interestingly, closing the LaTeX file and opening any other buffer
> (say with the :new command) does not make the problem go away. Even if
> you start vim and open a *.tex file in a new tab, then the problem
> suddenly appears also in the first ("virgin") tab.
>
> Clearly, this behavior is not desired, but I can't make sense of it.
> It used to work fine some time ago but might have been broken during
> an update. I'm using Arch Linux with the vim-latexsuite package, but
> the problem persists when using the latest version from Git. Vim has
> version 7.3.
>
> Hope this is not due to a silly mistake on my part. Thanks for the help.
>
> Best regards
> Bernhard
>
> --
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> ___
> Vim-latex-devel mailing list
> Vim-latex-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] foldcolumn disappeared

[Filip Kadlec]

Hello everyone,

  after a distribution upgrade, my vim-latex still works as before, but I 
have noticed that in the .tex files, the foldcolumn does not appear 
although the folds exist. Previously, I did not modify my personal 
settings for folds since everything worked normally. I have tried to look 
into the vim-latex suite FAQ and manual but I found no simple solution. 
Can anybody help me please about the best way to proceed. Of course, I 
could set foldcolumn=4 but this would affect all open files, not only 
.tex, which I do not wish.

Best regards,
Filip

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] foldcolumn disappeared

[Filip Kadlec]

Hello Ruthard,

 thank you for this elegant solution. It now works as before.

Best regards,
Filip


On Sat, 20 Dec 2014, Ruthard Baudach wrote:


Date: Sat, 20 Dec 2014 09:39:23
From: Ruthard Baudach 
To: vim-latex-devel 
Subject: Re: [Vim-latex-devel] foldcolumn disappeared


== Auszüge aus der Nachricht von  Filip Kadlec vom 2014-12-19 09:56:
Hello everyone,

  after a distribution upgrade, my vim-latex still works as before, but I
have noticed that in the .tex files, the foldcolumn does not appear
although the folds exist. Previously, I did not modify my personal
settings for folds since everything worked normally. I have tried to look
into the vim-latex suite FAQ and manual but I found no simple solution.
Can anybody help me please about the best way to proceed. Of course, I
could set foldcolumn=4 but this would affect all open files, not only
.tex, which I do not wish.

 Best regards,
 Filip



Hello Filip,

I don't know a latex-suite-ish solution to this, but local
custumizations to vim should be put in `.vim/after/` – these files are
loaded _after_ the main configuration files are loaded, thus overriding
them.

The `ftplugin` directories are for FileTypePLUGINs (hence the name), the
name of the files in this directory should start with the file type's
name.

Thus, putting a file named `tex.vim` in the directory
`.vim/after/ftplugin/` containing the line
`set foldcolumn=4` would set foldcolumn to 4 only for tex files and
would not be overridden by updates.

Best regards,

Ruthard

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] Forward search

[Filip Kadlec]

Dear all,

  after a distribution upgrade, I am experiencing a strange problem with 
the forward search. I use pdflatex and pdf target format for both 
compiling and viewing. When I input \lv , Okular with the pdf file is 
activated. (By the way, Okular 0.21 now supports document tabbing, and 
each time a new tab is opened... slightly annoying). However, when I 
attempt a forward search via \ls, this fails; Okular will say: "Could not 
open /home/path/yourfile.dvi". It obviously can't open it, but I would 
like it to open the pdf. I don't know why this happens nor where to change 
this behaviour.

  Thanks in advance for your help.
Filip

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] A Bug in Smart Quote Feature in vim 7.4.640

[Filip Kadlec]

Hello,
  unfortunately, I don't have a solution to your problem, I just can state
that smart quotes work in my vim-latex installation. After hitting "
twice, I get ``''<++> as expected. Rather than vim-version, I think it is
a matter of version of the vim-latex suite; mine comes from the OpenSuSE
13.2 distribution.
  Unfortunately, it seems to me that some of such minor functionalities 
fail in some cases, depending on distribution, and are quite hard to track 
if one does not understand quite deeply how vim-latex works. Otherwise, 
vim-latex is a nice piece of work.

Best,
Filip

On Wed, 5 Aug 2015, Mani Bastani Parizi wrote:

>Date: Wed, 5 Aug 2015 15:14:57
>From: Mani Bastani Parizi 
>To: vim-latex-devel@lists.sourceforge.net
>Subject: [Vim-latex-devel] A Bug in Smart Quote Feature in vim 7.4.640
>
> Dear Developers,
>
> The Smart Quote feature seems not to be working properly in vim
> 7.4.640 (on Fedora 22).
>
> Instead of replacing double-quote (") with `` and '' accordingly, it
> is replaced with "``" and "''" (i.e., the corresponding two back-ticks
> or two apostrophes are enclosed in an extra pair of double-quotes
> themselves).
>
> I was wondering if there exists a solution for the issue.
>
> Thanks,
> Mani
>
>
>
>
 
--  
Upozorneni: Neni-li v teto zprave vyslovne uvedeno jinak, neni tato e-mailova 
zprava navrhem na uzavreni smlouvy ani prijetim pripadneho navrhu na uzavreni 
smlouvy a nezaklada predsmluvni odpovednost FZU AV CR, v. v. i.
Disclaimer: If not expressly stated otherwise, this e-mail message cannot be 
considered as a proposal to conclude a contract, neither the acceptance of a 
proposal to conclude a contract, nor does it create any pre-contractual 
liability on the part of FZU AV CR, v. v. i.


--
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] spell problem

[Filip Kadlec]

Hi PierrO,

 I had a similar problem with .tex files some time ago. The behavior has 
much improved when I added to my .vimrc these lines:


set spell linebreak
syntax spell toplevel

Since then, spelling stops working only exceptionally in some longer files
with several hundred lines, and this may have something to do with
folding.  Often, re-loading the file or reformatting restores the
spelling.

Hope this will help you.

Filip


On Wed, 17 Aug 2016, Le Cocq wrote:


Date: Wed, 17 Aug 2016 19:10:16
From: Le Cocq 
To: vim-latex-devel@lists.sourceforge.net
Subject: [Vim-latex-devel] spell problem

Hi,

I activated in vain : spell spelllang=fr

But when I am working with several files, spelling is activated in some
of them, or only in comments or inside a command in the first loaded
file. I do not remember if a keyword is defined and do not know where is
the configuration file.

Could you help a beginner since 2 years ;)


Upozornění / Disclaimer --
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Aux completion

[Filip Kadlec]

Hi, Gerd,

 I second Laszlo's point of view; for me, using labels with well chosen
names is clearly the best choice, and I think that the latex-suite should
keep this behavior by default. To me, the -completion works quite well
and it would maybe need some improvements (it does not work for me with
\includegraphics, and if the vim-window is split when invoking  in
\cite, it oftentimes fails...) but not a complete change of logic.

 Your idea to scan the .aux files could be useful for someone, though. I
don't know if it is feasible, but I would suggest an implementation via a
command, something like

 let g:Tex_completion_scanfile = tex / aux

whereby everyone would have the choice.

This would does not imply less code nor less maintenance, though.

Best regards,
Filip

On Thu, 26 Jan 2017, N Laszlo Frazer wrote:


Date: Thu, 26 Jan 2017 21:33:44
From: N Laszlo Frazer 
To: "vim-latex-devel@lists.sourceforge.net"
   
Subject: Re: [Vim-latex-devel] Aux completion

Please do not remove the current functionality.  I think it would be very
annoying to rely on the aux file being up-to-date.

Well-chosen keys are much easier to remember than numbers, and they do not
change when you expand the document.

On Fri, 27 Jan 2017 00:52:25 +1100, Gerd Wachsmuth
 wrote:


Hi,

in my version of latex-suite (https://github.com/gerw/vim-latex-suite),
I have changed the mechanism of \ref-completions. The current version of
latex-suite greps through the tex-file for \labels. My version greps
through the aux-file. This has the advantage, that one does not have to
memorize the keys within the \labels for completion, but can use the
actual labels in the compiled document.

Hence, you get the following expansions (given that the tex-file has the
corresponding labels):

theorem.1.3   =>   \autoref{thm:bar}
section.2 =>   \autoref{sec:foo}
(1.9  =>   \eqref{eq:baz}
(1.9) =>   \eqref{eq:baz}

(You can also reconfigure an option to use \cref (or anything else)
instead of \autoref)

This is quite convenient, because you can look in the pdf to get the
appropriate number of the thing you want to refer to and use this for
the completion. No need for packages like showkeys.

The only disadvantage is that you get the labels from the aux-file.
Hence, if the aux-file is not up-to-date or you use the numbers from a
print-out (and the aux-file is more recent), you might get unexpected
results.

My question is: Can I replace the current style of the completion with
this aux-based completion in the official repository? This would result
in less code (less maintenance) and is therefore desirable. However, I
can understand if someone would like to stay with the current behavior.

The stage is open for discussion, see also
https://github.com/vim-latex/vim-latex/issues/55


Best regards,
Gerd


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Upozornění / Disclaimer --
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Aux completion

[Filip Kadlec]

Hello,

 things start to be clearer to me and it seems to me that the new version
could, indeed, supersede the old one in functionality. To summarize, in
the new version:

- F9 works only after the first compilation (not too restrictive)
- F9 completes based on either labels or current reference numbers. 
- The labels method works almost as before, except that the outline window

does not show a preview of the relevant part of the .tex file.

For the "new" method, how does your algorithm detect which numbers to
scan? Is it sensitive to a keyword like section, part, theorem, eq, fig,
etc. when F9 is hit? And depending on this keyword, it enters various
commands like \autoref, \eqref... right? But in plain LaTeX, just \ref{}
should suffice, maybe with options \ref{sec:}, \ref{fig:}, \ref{eq:} etc.,
I think. How about the \cite command? As far as I understand, its
functionality would stay as before.

Filip

On Fri, 27 Jan 2017, Gerd Wachsmuth wrote:


Date: Fri, 27 Jan 2017 19:42:28
From: Gerd Wachsmuth 
To: Filip Kadlec ,
   "vim-latex-devel@lists.sourceforge.net"
   
Subject: Re: [Vim-latex-devel] Aux completion

Thank you for your comments.

I think I was not precise at one point: You still can use labels for 
completion (as long as they are already in the aux file).


To given an example:

\documentclass{article}
\usepackage{hyperref}
\begin{document}
\begin{equation}
\label{eq:einstein}
E = m \, c^2
\end{equation}
\begin{equation}
a^2 + b^2 = c^2
\label{eq:pythagoras}
\end{equation}
\end{document}


The current version produces the following outline window:


 eq:einstein

:

 eq:pythagoras  

:a^2 + b^2 = c^2

You can only use the labels for completion and you see some of the surrounding 
text.


The new, aux-based version produces:


eq:einstein

:  (1)

eq:pythagoras

:  (2)

Here, you can use both, the label and the actual number, with the new aux 
completion. However, you do not see some of the text.



Moreover, the old mechanism fails to detect if you input some other files via 
macros, e.g.,

 \newcommand{\myinput}[1]{\input{#1}}
and then
 \myinput{test}.
Since the labels of the file test.tex still appear in the aux file, the aux 
based completion also find those labels.



In my opinion, the only regress is that you have to compile (once) after 
entering a new \label{} and before you will be able to complete a reference to 
exactly this label.



Best regards,
Gerd


On 2017-01-27 10:05, Filip Kadlec wrote:

Hi, Gerd,

 I second Laszlo's point of view; for me, using labels with well chosen
names is clearly the best choice, and I think that the latex-suite should
keep this behavior by default. To me, the -completion works quite well
and it would maybe need some improvements (it does not work for me with
\includegraphics, and if the vim-window is split when invoking  in
\cite, it oftentimes fails...) but not a complete change of logic.

 Your idea to scan the .aux files could be useful for someone, though. I
don't know if it is feasible, but I would suggest an implementation via a
command, something like

 let g:Tex_completion_scanfile = tex / aux

whereby everyone would have the choice.

This would does not imply less code nor less maintenance, though.

Best regards,
Filip

On Thu, 26 Jan 2017, N Laszlo Frazer wrote:


Date: Thu, 26 Jan 2017 21:33:44
From: N Laszlo Frazer 
To: "vim-latex-devel@lists.sourceforge.net"
   
Subject: Re: [Vim-latex-devel] Aux completion

Please do not remove the current functionality.  I think it would be very
annoying to rely on the aux file being up-to-date.

Well-chosen keys are much easier to remember than numbers, and they do
not
change when you expand the document.

On Fri, 27 Jan 2017 00:52:25 +1100, Gerd Wachsmuth
 wrote:


Hi,

in my version of latex-suite (https://github.com/gerw/vim-latex-suite),
I have changed the mechanism of \ref-completions. The current version of
latex-suite greps through the tex-file for \labels. My version greps
through the aux-file. This has the advantage, that one does not have to
memorize the keys within the \labels for completion, but can use the
actual labels in the compiled document.

Hence, you get the following expansions (given that the tex-file has the
corresponding labels):

theorem.1.3   =>   \autoref{thm:bar}
section.2 =>   \autoref{sec:foo}
(1.9  =>   \eqref{eq:baz}
(1.9) =>   \eqref{eq:baz}

(You can also reconfigure an option to use \cref (or anything else)
instead of \autoref)

This is quite convenient, because you can look in the pdf to get the
appropriate number of the thing you want to refer to and use this for
the compl

[Vim-latex-devel] compiling multiple times - how to debug

[Filip Kadlec]

Hello all,

since years, I have been using successfully the LaTeX suite under OpenSUSE 
Linux. Having configured the compilation to pdf format, it has always 
worked straightforwardly. Since recently, however, I have problems with 
the multiple compilation feature, described in part 6.3 of :h 
latex-suite.txt.  In situations, where the required routine pdflatex - 
bibtex - pdflatex - pdflatex would be triggered automatically by a single 
compilation command, now only a single pdflatex compilation appears to 
occur. This is obviously annoying.


In my ~/.vimrc, I have the following settings:

let g:tex_flavor='latex'
let g:Tex_DefaultTargetFormat='pdf' 
let g:Tex_MultipleCompileFormats='pdf' 
let g:Tex_ViewRule_pdf = 'okular --unique' 
let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode -file-line-error $* -inverse-search "gvim --servername GVIM --remote +\%l \%f"'


I reused documents which I compiled earlier; currently, swapping some 
citations in the .tex file leads to a wrong order of their numbering in 
the output pdf file if just a single compilation command is triggered.


I suspect the reason that the multiple compilation has stopped working is 
some update in texlive; or perhaps an update of vim-latex? Anyway, I 
wonder how I can debug this problem. Any help would be appreciated.


By the way, since this forum has been quite inactive, I thought of posting 
this elsewhere, but I am not sure what the best place would be.


Best regards, Filip


___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] compiling multiple times - how to debug

[Filip Kadlec]

Hi, Mirko,

 thank you for your reply. Having explored the two hints you suggested,
first I think you are right that the synctex option should only be
preceded by a single dash; that is in agreement with the man page. I do
not know exactly why the double dash was there; someone has advised me
this line a long time ago, but I cannot exclude I later accidentally added
a second dash without noticing. So I have fixed this in my .vimrc file.

As for the debugging procedure, I have done as you advised, and the result
is the following:

comp : +Tex_RunLaTeX, b:fragmentFile = 0
comp : Tex_RunLaTeX: compiling to target [pdf]
comp : Tex_RunLaTeX: getting dependency chain = [pdf]
comp : +Tex_SetTeXCompilerTarget: setting target to [pdf] for Compiler
comp : Tex_RunLaTeX: setting target to pdf
comp : Tex_RunLaTeX: compiling file multiple times via Tex_CompileMultipleTimes
comp : Tex_CompileMultipleTimes: latex run number : 1
comp : Tex_CompileLatex: getting mainfname = [NbN-ver1.tex] from 
Tex_GetMainFileName
comp : Tex_CompileLatex: execing [make! NbN-ver1.tex]
comp : Tex_CompileMultipleTimes: errors = []
comp : Tex_CompileMultipleTimes: Ran latex 1 time(s)
comp : Tex_RunLaTeX: errlist = [
 1:  ]
comp : Tex_SetupErrorWindow: mfnlog = NbN-ver1.log
comp : -Tex_RunLaTeX

I was not able to find any suspicious message there. The .bbl file is
still not updated when I recompile the main file after a change in the
order of references. It seems the Tex_CompileMultipleTimes procedure does
not notice there was a change in the .aux file.

 Otherwise, there is a workaround I found in some discussion list, which
consists in running
:!latexmk -pdf %

on the command line. This will update also the bibliography as one would 
wish, but, unfortunately, the produced pdf file then does not support the 
inverse search feature. At least it kind of proves BibTeX is functional. 
By the way, also my forward search has problems, which is quite an old 
issue but off-topic here.


 Thank you for your effort,

 Filip

On Tue, 23 Feb 2021, Mirko Hessel-von Molo wrote:



Dear Filip,

since noone else who is more competent than me seems to be here to answer, let 
us try it together.
I'm just an "ordinary vim-latexsuite user" with no particular experience in 
writing or debugging vim addons,
but let's see how far we get.

You could try adding

let g:Tex_Debug=1

to your vimrc file. This enables debugging function within latex-suite.
Then when a compilation run is done (and multiple compilation has not worked)
issue the command

:call Tex_PrintDebug()

within vim. What results does this give?

Besides, I'm a bit puzzled by the value given in your vimrc to the 
g:Tex_CompileRule_pdf variable.
Are you quite sure that it should read "--synctex=1" and not "-synctex=1" ? 
(Two dashes versus one?)

Best regards, Mirko

Am Freitag, den 19.02.2021, 16:56 +0100 schrieb Filip Kadlec:

Hello all,

since years, I have been using successfully the LaTeX suite under OpenSUSE 

Linux. Having configured the compilation to pdf format, it has always 

worked straightforwardly. Since recently, however, I have problems with 

the multiple compilation feature, described in part 6.3 of :h 

latex-suite.txt.  In situations, where the required routine pdflatex - 

bibtex - pdflatex - pdflatex would be triggered automatically by a single 

compilation command, now only a single pdflatex compilation appears to 


occur. This is obviously annoying.

In my ~/.vimrc, I have the following settings:

let g:tex_flavor='latex'

let g:Tex_DefaultTargetFormat='pdf' 

let g:Tex_MultipleCompileFormats='pdf' 

let g:Tex_ViewRule_pdf = 'okular --unique' 


let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode 
-file-line-error $* -inverse-search "gvim --servername GVIM --remo
te +\%l \%f"'

I reused documents which I compiled earlier; currently, swapping some 

citations in the .tex file leads to a wrong order of their numbering in 


the output pdf file if just a single compilation command is triggered.

I suspect the reason that the multiple compilation has stopped working is 

some update in texlive; or perhaps an update of vim-latex? Anyway, I 


wonder how I can debug this problem. Any help would be appreciated.

By the way, since this forum has been quite inactive, I thought of posting 


this elsewhere, but I am not sure what the best place would be.

Best regards, Filip

___

Vim-latex-devel mailing list

Vim-latex-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/vim-latex-devel






___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] compiling multiple times - how to debug

[Filip Kadlec]

Dear Marko,

 thanks for this enquiry. In my system, the file compiler.vim is located 
elsewhere, namely in the directory 
/usr/share/vim/site/ftplugin/latex-suite/. But this is not important, I 
guess. The file header is as follows:


"=
"   File: compiler.vim
"  Author: Srinath Avadhanula
" Created: Tue Apr 23 05:00 PM 2002 PST
"
"  Description: functions for compiling/viewing/searching latex documents
"=

and it has a total of 875 lines. I am not quite sure we are comparing the 
same versions, since I found the lines you mention slightly elsewhere. 
Instead of the code located around lines 608 and 617, I think you mean 
these lines:


580 " If the .bbl file changed after running bibtex, we need to
581 " latex again.
582 if biblinesAfter != biblinesBefore 
583 echomsg 'Need to rerun because bibliography file changed...'

584 call Tex_Debug('Tex_CompileMultipleTimes: Need to rerun 
because bibliography file changed...', 'comp')
585 let needToRerun = 1

589 " check if latex asks us to rerun
590 let auxlinesAfter = Tex_GetAuxFile(auxFileName)
591 if auxlinesAfter != auxlinesBefore
592 echomsg "Need to rerun because the AUX file changed..."
593 call Tex_Debug("Tex_CompileMultipleTimes: Need to rerun to get 
cross-references right...", 'comp')
594 let needToRerun = 1
595 endif

One question is whether these two criteria are well chosen and sufficient; 
as you wrote, it seems that swapping two citations is a sufficient reason 
for triggering BibTeX but may not necessarily change the number of lines 
in the .aux file.


Another question is whether these tests in the procedure work as they were 
intended. In this respect, I have doubts. I checked that when I compile my 
.tex file, and this compilation _does_ produce an .aux file with a number 
of lines different from before the compilation, I get anyway the message 
in gvim:


Ran latex 1 time(s)

and BibTeX is not run (no new .bbl file is produced).

As for the other test concerning the number of lines in the .bbl files, I 
could not verify because BibTeX is not triggered in this way.


Debugging the .vim script does not seem easy to me, so I don't know how to 
proceed now.


 All the best,

Filip


On Wed, 24 Feb 2021, Mirko Hessel-von Molo wrote:



Dear Filip,

from lines 608 and 617 of 
/usr/share/vim/addons/ftplugin/latex-suite/compiler.vim I gather that
a second (or further) run of pdflatex is issued when either the _number of 
lines_ of the bib file or of the aux file
has changed during the first run.

So when you just rearrange the cite commands in your file, this presumably 
won't change the number of lines of either of those files.
In that way, the multiple compile function is not adapted to bibliography 
styles which number references by the order of first appearance.

You could check what happens when you add a new citation to your tex file.

Best regards, Mirko



Am Mittwoch, den 24.02.2021, 11:36 +0100 schrieb Filip Kadlec:

Hi, Mirko,

  thank you for your reply. Having explored the two hints you suggested,

first I think you are right that the synctex option should only be

preceded by a single dash; that is in agreement with the man page.. I do

not know exactly why the double dash was there; someone has advised me

this line a long time ago, but I cannot exclude I later accidentally added

a second dash without noticing. So I have fixed this in my .vimrc file.

As for the debugging procedure, I have done as you advised, and the result

is the following:

comp : +Tex_RunLaTeX, b:fragmentFile = 0

comp : Tex_RunLaTeX: compiling to target [pdf]

comp : Tex_RunLaTeX: getting dependency chain = [pdf]

comp : +Tex_SetTeXCompilerTarget: setting target to [pdf] for Compiler

comp : Tex_RunLaTeX: setting target to pdf

comp : Tex_RunLaTeX: compiling file multiple times via Tex_CompileMultipleTimes

comp : Tex_CompileMultipleTimes: latex run number : 1

comp : Tex_CompileLatex: getting mainfname = [NbN-ver1.tex] from 
Tex_GetMainFileName

comp : Tex_CompileLatex: execing [make! NbN-ver1.tex]

comp : Tex_CompileMultipleTimes: errors = []

comp : Tex_CompileMultipleTimes: Ran latex 1 time(s)

comp : Tex_RunLaTeX: errlist = [

  1:  ]

comp : Tex_SetupErrorWindow: mfnlog = NbN-ver1.log

comp : -Tex_RunLaTeX

I was not able to find any suspicious message there. The .bbl file is

still not updated when I recompile the main file after a change in the

order of references. It seems the Tex_CompileMultipleTimes procedure does

not notice there was a change in the .aux file.

  Otherwise, there is a workaround I fou