vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

Re: [Vim-latex-devel] Compilation (Correction)

[Till M. <ope...@ti...>]

On Wed June 18 2008, Simon Friedberger wrote:
> let g:Tex_ViewRuleComplete_pdf = 'evince $* &'
> didn't work I had to add a ".pdf"
> let g:Tex_ViewRuleComplete_pdf = 'evince $*.pdf &'

Btw, This beheavior is documented in:
vimfiles/ftplugin/latex-suite/texrc

Regards,
Till

Re: [Vim-latex-devel] Compilation

[Till M. <ope...@ti...>]

On Wed June 18 2008, Simon Friedberger wrote:

> I have two issues.
>
> a) I set "let g:Tex_ViewRuleComplete_pdf = 'evince $* &'" but it is not
> automatically opened after compilation, is that the desired behavior?

Iirc it should be enough to set it to 'evince' on UNIX/Linux systems, the 
filename and ampersand are added by default. But it is not ViewRuleComplete 
but ViewRule that you need to change to 'evince'.

Regards,
Till

Re: [Vim-latex-devel] Compilation (Correction)

[Simon F. <sim...@a-...>]

let g:Tex_ViewRuleComplete_pdf = 'evince $* &'
didn't work I had to add a ".pdf"
let g:Tex_ViewRuleComplete_pdf = 'evince $*.pdf &'

[Vim-latex-devel] Compilation

[Simon F. <sim...@a-...>]

Hi Listmembers,

I have two issues.

a) I set "let g:Tex_ViewRuleComplete_pdf = 'evince $* &'" but it is not
automatically opened after compilation, is that the desired behavior?

b) Sometimes after compilation I get a "press a Button" message. So far
only happened in conjunction with "latex ran once". So it doesn't seem
to happen if latex runs multiple times.


My entire tex.vim:
let g:tex_flavor = "latex"
let g:Tex_MultipleCompileFormats = 'pdf'
let g:Tex_ViewRuleComplete_pdf = 'evince $* &'
let g:Tex_DefaultTargetFormat = 'pdf'


Thanks in advance
	Simon

Re: [Vim-latex-devel] Spell-check not working with latex-suite

[Ted P. <te...@te...>]

If you find out it isn't something that you did but a problem that 
others could experience, be sure to post your solution. :)

--Ted

Eyolf Østrem wrote:
> I think it's something in my tweaked syntax file. I thought I had been
> careful enough when I wrote it, but apparently I hadn't. Sorry for the
> noise (and thanks for the help).

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Spell-check not working with latex-suite

[Eyolf Ø. <ey...@oe...>]

On 13.06.2008 (18:06), Ted Pavlic wrote:
> >> It works for me.
> > 
> > Hm. OK, I'll have to check my configuration then. 
> 
> I've been trying to think of anything special I had to do to get spell 
> checking to work, but I just can't come up with anything. I've scanned 
> through my .vimrc, but I don't see anything...
> 
> Now, for Vim7, I did have to do a...
> 
> let g:tex_flavor='latex'

Hey -- thanks! That solved another of my annoyances, but not this one.

I think it's something in my tweaked syntax file. I thought I had been
careful enough when I wrote it, but apparently I hadn't. Sorry for the
noise (and thanks for the help).

Eyolf

-- 
Scientists were preparing an experiment to ask the ultimate question.
They had worked for months gathering one each of every computer that was
built. Finally the big day was at hand.  All the computers were linked
together.  They asked the question, "Is there a God?".  Lights started
blinking, flashing and blinking some more.  Suddenly, there was a loud
crash, and a bolt of lightning came down from the sky, struck the
computers, and welded all the connections permanently together.  "There
is now", came the reply.

Re: [Vim-latex-devel] Spell-check not working with latex-suite

[Ted P. <te...@te...>]

>> It works for me.
> 
> Hm. OK, I'll have to check my configuration then. 

I've been trying to think of anything special I had to do to get spell 
checking to work, but I just can't come up with anything. I've scanned 
through my .vimrc, but I don't see anything...

Now, for Vim7, I did have to do a...

let g:tex_flavor='latex'

However, I assume that that's already the case for you (or else you 
wouldn't be seeing Vim-LaTeX at all).


>> Are you sure you have something like...
>>
>> set spell
>> set spelllang=en_us
>>
>> in your .vimrc?
> 
> Yes, I do. Also, if I set the filetype to anything other than "tex",
> everything works as expected, but if I change it  to tex, the spelling
> highlighting disappears, and none of the mistakes are found (so it's not
> just a matter of missing/overridden highlighting). 

Try misspelling a word. If you cursor over the word, can you type:

z=

to get suggestions? What happens?

--Ted


-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Spell-check not working with latex-suite

[Eyolf Ø. <ey...@oe...>]

On 13.06.2008 (11:17), Ted Pavlic wrote:
> It works for me.

Hm. OK, I'll have to check my configuration then. 

> Are you sure you have something like...
>
> set spell
> set spelllang=en_us
>
> in your .vimrc?

Yes, I do. Also, if I set the filetype to anything other than "tex",
everything works as expected, but if I change it  to tex, the spelling
highlighting disappears, and none of the mistakes are found (so it's not
just a matter of missing/overridden highlighting). 

Eyolf

-- 
  Thank God I'm an atheist.

Re: [Vim-latex-devel] Spell-check not working with latex-suite

[Ted P. <te...@te...>]

It works for me.

Note that I also use the engspchk plugin, which seems to do a better job 
  when syntax highlighting is turned on. That being said, "]s" has 
nothing to do with that plugin, and it works for me whether or not I 
load it.

Are you sure you have something like...

set spell
set spelllang=en_us

in your .vimrc?

--Ted

Eyolf Østrem wrote:
> I've discovered that the built-in spell checker in vim doesn't work if
> ft=tex is set. It's not just the syntax highlighting -- ]s doesn't jump to
> the next spelling mistake.. I've searched through the source files for
> "spell", without finding anything that looked suspicious, but I'm no
> vimscript guru so I may have missed something. 
> Anyone else having this problem, or should I review my own configuration?
> I've tried it from a clean slate too, different user, no .vimrc file, but
> same result.
> 
> Eyolf
> 

-- 
Ted Pavlic <te...@te...>

[Vim-latex-devel] Spell-check not working with latex-suite

[Eyolf Ø. <ey...@oe...>]

I've discovered that the built-in spell checker in vim doesn't work if
ft=tex is set. It's not just the syntax highlighting -- ]s doesn't jump to
the next spelling mistake.. I've searched through the source files for
"spell", without finding anything that looked suspicious, but I'm no
vimscript guru so I may have missed something. 
Anyone else having this problem, or should I review my own configuration?
I've tried it from a clean slate too, different user, no .vimrc file, but
same result.

Eyolf

-- 
Alright, you!!  Imitate a WOUNDED SEAL pleading for a PARKING SPACE!!

Re: [Vim-latex-devel] compiling with wrong cross-references

[Ted P. <te...@te...>]

Hm. You make a good point about "xdg-open" in the help file. I wonder if
Vim should be changed so that empty ViewRules execute xdg-open just like
"open" and "start" are called in OS/X and Windows... <?>

Is xdg-open pretty universal on Linux distributions?

--Ted

Till Maas wrote:
> I just commited a changeset to improve all this:
> 
> http://vim-latex.svn.sourceforge.net/viewvc/vim-latex?view=rev&revision=1039
> 
> Regards,
> Till
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] compiling with wrong cross-references

[Till M. <ope...@ti...>]

I just commited a changeset to improve all this:

http://vim-latex.svn.sourceforge.net/viewvc/vim-latex?view=rev&revision=1039

Regards,
Till

[Vim-latex-devel] SumatraPDF -- Windows PDF viewer with reload and pdfsync support

[Ted P. <te...@te...>]

I saw this on CTT (comp.text.tex):

	http://blog.kowalczyk.info/software/sumatrapdf/

Sumatra PDF has

	*) automatic reload support (i.e., PDF is refreshed each time PDF is 
regenerated)

	*) pdfsync integration (i.e., supports forward/inverse searching (both?))

It's also a very tiny open source viewer. It reminds me of Yap, but it's 
for PDFs.

It doesn't match Skim (for OS/X), but it's nice to have around on 
Windows if you don't want to install an Adobe product.

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] compiling with wrong cross-references

[Ted P. <te...@te...>]

>> Patch at:
>> http://links.tedpavlic.com/patch/VIM-LaTeX-osx-inverse-search-compiler.patc
>> h
> 
> I added some documentation for the new options, can you please take a look, 
> whether this is correct?
> http://vim-latex.sourceforge.net/vim-latex-forward-backard-search.patch

The documentation looks good. However, it's important to note that you 
can use *ANY* viewer you want by setting the appropriate variables.

It's also important to note that the ONLY way you can get forward 
searching on OS/X is to turn on the "g:TreatMacViewerAsUNIX" flag on and 
  provide a UNIX-like ViewRule that accepts the command line syntax:

viewer TARGET_FILE LINE_NUMBER SOURCE_FILE

for example:

skim blah.pdf 28 blah.tex

Finally, something that has not changed (but was not well documented) is 
that on Windows and Mac, if you leave your ViewRule EMPTY, the *OS* will 
open whatever is associated with that type of file. Again, forward 
searching won't work, but \lv'ing will.


> In your blogpost you write that only TeXniscope supports source specials but 
> the patch looks like Skim and PDFView support Forward searching, too.

Skim and PDFView support both forward and *INVERSE* searching as long as 
you build your document with the pdfsync package.

"Source specials" only exist for DVI files. PDFsync emulates something 
LIKE source specials by dumping them into a third file that the other 
programs can read.

To get source specials with DVIs, you add "-source-specials" to your 
latex build line. To add pdfsync to your PDFs (and DVIs, actually), you 
add "\usepackage{pdfsync}" to your TeX source and don't bother changing 
anything in your latex build line.

--Ted

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] compiling with wrong cross-references

[Till M. <ope...@ti...>]

On Sat May 31 2008, Ted Pavlic wrote:

> Some additional patches that should definitely be included:
>
> *) Fixes forward searching/viewing to actually work on OS/X
> http://phaseportrait.blogspot.com/2007/07/vim-latex-modification-forward.ht
>ml
>
> Patch at:
> http://links.tedpavlic.com/patch/VIM-LaTeX-osx-inverse-search-compiler.patc
>h

I added some documentation for the new options, can you please take a look, 
whether this is correct?
http://vim-latex.sourceforge.net/vim-latex-forward-backard-search.patch

In your blogpost you write that only TeXniscope supports source specials but 
the patch looks like Skim and PDFView support Forward searching, too.

I will look at the other patch later, but now I have to do some other stuff 
than maintaining vim-latex.

Regards,
Till

Re: [Vim-latex-devel] compiling with wrong cross-references

[Eyolf Ø. <ey...@oe...>]

 
I just wanted to chime in in this thread and say "Yes, Yes, Yes!" I'd be
eternally grateful if the thread could turn into a reopening of development
of latex-suite. I know, so far it's mostly limited to gathering and applying
patches from here and there, but I hope that that "Someday..." will
be soon. :)

My own abilities in vim scripting are very limited, but I do spend most of
my day in front of the thing (and half of that with the suite), so I guess
I owe it to the community to contribute. I'll see what I can do (and think
about what I think needs to be done).

Until then, just this little note to let you all know that your work is
appreciated.

Eyolf


-- 
The big cities of America are becoming Third World countries.
		-- Nora Ephron

Re: [Vim-latex-devel] compiling with wrong cross-references

[Ted P. <te...@te...>]

> Here is a list of the debian patches:

Some additional patches that should definitely be included:

*) Fixes forward searching/viewing to actually work on OS/X
http://phaseportrait.blogspot.com/2007/07/vim-latex-modification-forward.html

Patch at: 
http://links.tedpavlic.com/patch/VIM-LaTeX-osx-inverse-search-compiler.patch

*) Of course, the subject of this thread:
http://linuxwisdom.blogspot.com/2007/08/fixing-latex-suites-jump-to-error.html

The patch is included. The "setlocal efm" should be added, and you could 
argue that the -file-line-error (the -style is deprecated in most cases) 
is overkill because old LaTeX implementations might not support it. It 
PROBABLY should be added to the help files though.

I have several personal fixes that allow me to do a lot more with 
Vim-LaTeX (like automatically run makeindex/authorindex to generate 
several different types of indexes/glossaries/etc.), but I haven't 
cleaned them up and released patches.... Someday....

--Ted

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] fixing bugs in vim-latex

[Till M. <ope...@ti...>]

On Sat May 31 2008, Martin Sander wrote:

> We should find a way to organize our efforts, maybe we should use the
> sourceforge bugtracker at:
>
> http://sourceforge.net/tracker/?group_id=52322&atid=466456
>
> It seems that some debian bugs have been forwarded there some time ago.
> I had a look into Debian bug #254619 (overwriting of F1 mapping) because
> it is something that I found annoying, too. I think I can find a way to
> fix this, and I also already know a workaround.
> I think it would also be a good idea to search the mailing list
> archieves for bugs, and file them there.
>
> Let me know what you think.

All this sounds good.

Regards,
Till

Re: [Vim-latex-devel] compiling with wrong cross-references

[Till M. <ope...@ti...>]

On Fri May 30 2008, Till Maas wrote:

> - disabledby.dpatch
> The patch seems to make it possible to disable vim-latex somehow without
> uninstalling it. This seems to be a debian specific patch to me, but it is
> not. But there should be a more elegant solution to this problem I guess.

The patch is needed to make the vim-addon-manager work in debian. Afaics this 
patch should not be included upstream, because it would interfer when one 
does not want to use the version from debian, but a local version, e.g. 
because one does not have root permissions or wants to use a different 
version.

Regards,
Till

[Vim-latex-devel] fixing bugs in vim-latex

[Martin S. <fo...@un...>]

On Sat, May 31, 2008 at 12:20:33AM +0200, Till Maas wrote:
> Hi Martin,
> 
> About the bug I asked you to reproduce:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460555
> 
> I can reproduce it, when I use these settings:
> se showcmd" and "se columns=50"

It gets stranger by the minute.
I remember now that I the code that did the completion, tried entering
the commands by hand and the bug did not appear.

> also I looked through the bugs except for the "Outstanding bugs -- Normal 
> bugs; Unclassified", therefore it would be better if you only check these to 
> avoid duplicate work.

Okay, I'll look at them. I already had a look at some of them yesterday.

We should find a way to organize our efforts, maybe we should use the
sourceforge bugtracker at:

http://sourceforge.net/tracker/?group_id=52322&atid=466456

It seems that some debian bugs have been forwarded there some time ago.
I had a look into Debian bug #254619 (overwriting of F1 mapping) because
it is something that I found annoying, too. I think I can find a way to
fix this, and I also already know a workaround.
I think it would also be a good idea to search the mailing list
archieves for bugs, and file them there.

Let me know what you think.

Martin

Re: [Vim-latex-devel] compiling with wrong cross-references

[Till M. <ope...@ti...>]

On Fri May 30 2008, Till Maas wrote:

> - fname_outline.dpatch
> This is a python patch with a little bug description. It should be easily
> possible to understand what the problem is if one know what outline.py is
> used for.

> - insertitem.dpatch
> This is very simple but I do not understand the problem it solves.

I should have looked into the repository first: These two patches where 
already merged into svn around two years ago,

Regards,
Till

Re: [Vim-latex-devel] compiling with wrong cross-references

[Till M. <ope...@ti...>]

On Wed May 28 2008, Martin Sander wrote:

> Ted Pavlic wrote:

> > What we should do is get the source repository active again and get
> > people submitting to it.  Incrementally, we'd collect all of the nice
> > improvements made over the years.
>
> I think I'd like to be part of that. I think there are already some
> debian patches that are not in upstream. The problem is that I know next
> to nothing about vim-scripting, but I am willing to learn.

I am in, too. Actually I already got commit access, but I do know only a 
little more than you about vim-scripting. I also noticed that there are 
already some changes in the svn repository, that were not in the latest 
released tarball. The first debian patch is also already merged in a modified 
way btw. My plan is to merge all patches that I find and then go through the 
debian bug reports and see what I can do. Maybe you can also try to 
understand one debian patch, i.e. understand which problem it should solve 
and see whether it works, and then I will commit it so svn.

Here is a list of the debian patches:

- changelog.dpatch
The changelog needs only to be generated for the next release, therefore this 
can be checked later, imho.

- disabledby.dpatch
The patch seems to make it possible to disable vim-latex somehow without 
uninstalling it. This seems to be a debian specific patch to me, but it is 
not. But there should be a more elegant solution to this problem I guess.

- fname_outline.dpatch
This is a python patch with a little bug description. It should be easily 
possible to understand what the problem is if one know what outline.py is 
used for.

- foldingfix.dpatch
This is merged.

- insertitem.dpatch
This is very simple but I do not understand the problem it solves.


Regards,
Till

Re: [Vim-latex-devel] compiling with wrong cross-references

[Martin S. <fo...@un...>]

Felipe G. Nievinski wrote:
>> I was wondering if it wouldn't be a good idea to have the vim-latex
>> suite incorporating that?

We'd have to take into account portability, too. I don't know if all
versions of latex support -file-line-error.

Ted Pavlic wrote:
> Personally, I think it definitely would be a good idea.

+1. Maybe we should all donate some money to children in Uganda and ask
for a fix of in vim, though..

> What we should do is get the source repository active again and get
> people submitting to it.  Incrementally, we'd collect all of the nice
> improvements made over the years.

I think I'd like to be part of that. I think there are already some
debian patches that are not in upstream. The problem is that I know next
to nothing about vim-scripting, but I am willing to learn.

> Unfortunately, there's just enough starting friction to keep momentum
> from building up. :(

Engineers talk... ;-)

Additionally, I'd like to tell everybody here that Ted made some more changes to
his vimlatex script, and I wrote a python version, see:

http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html

Happy vimming

Martin

Re: [Vim-latex-devel] compiling with wrong cross-references

[Ted P. <te...@te...>]

Personally, I think it definitely would be a good idea.

However, the maintainers of the Vim-LaTeX suite have been silent for 
years (?) now, and so I have a feeling that Vim-LaTeX might be in its 
terminal state. Every once in a while someone flirts with taking it up, 
but that hasn't gone anywhere yet.

What we should do is get the source repository active again and get 
people submitting to it. Incrementally, we'd collect all of the nice 
improvements made over the years. Unfortunately, there's just enough 
starting friction to keep momentum from building up. :(

--Ted

Felipe G. Nievinski wrote:
> Thanks a lot, Ted.
> 
> I was wondering if it wouldn't be a good idea to have the vim-latex 
> suite incorporating that?
> 
> Felipe.
> 
> Ted Pavlic wrote:
>> Felipe --
>> 
>> One last note. It turns out that the most recent versions of many 
>> latex implementations have a flag that can fix this problem for
>> you.
>> 
>> Check out:
>> 
>> http://linuxwisdom.blogspot.com/2007/08/fixing-latex-suites-jump-to-error.html
>> 
>> 
>> 
>> In short, you add:
>> 
>> -file-line-error
>> 
>> to your LaTeX build line. You then add:
>> 
>> setlocal efm+=%E%f:%l:\ %m
>> 
>> to your .vim/compiler/tex.vim
>> 
>> file around line 202 (see the link for the exact location).
>> 
>> --Ted
>> 
>> Felipe G. Nievinski wrote:
>>> Hi.
>>> 
>>> When I'm compiling a .tex file with wrong cross-references
>>> (\label{} followed by \ref{}), I get a warning message indicating
>>> the offending reference (which I find useful) but then my .tex
>>> file gets replaced in vim with the corresponding .lox file (which
>>> I find annoying).
>>> 
>>> - Is that a bug or a feature? =)
>>> 
>>> Thanks, Felipe.
>>> 
>>> -------------------------------------------------------------------------
>>>  This SF.net email is sponsored by: Microsoft Defy all
>>> challenges. Microsoft(R) Visual Studio 2008. 
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
>>> _______________________________________________ Vim-latex-devel
>>> mailing list Vim...@li... 
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>> 
> 
> 

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] compiling with wrong cross-references

[Felipe G. N. <fgn...@te...>]

Thanks a lot, Ted.

I was wondering if it wouldn't be a good idea to have the vim-latex 
suite incorporating that?

Felipe.

Ted Pavlic wrote:
> Felipe --
> 
>     One last note. It turns out that the most recent versions of many 
> latex implementations have a flag that can fix this problem for you.
> 
>     Check out:
> 
> http://linuxwisdom.blogspot.com/2007/08/fixing-latex-suites-jump-to-error.html 
> 
> 
> In short, you add:
> 
> -file-line-error
> 
> to your LaTeX build line. You then add:
> 
> setlocal efm+=%E%f:%l:\ %m
> 
> to your .vim/compiler/tex.vim
> 
> file around line 202 (see the link for the exact location).
> 
>     --Ted
> 
> Felipe G. Nievinski wrote:
>> Hi.
>>
>> When I'm compiling a .tex file with wrong cross-references (\label{} 
>> followed by \ref{}), I get a warning message indicating the offending 
>> reference (which I find useful) but then my .tex file gets replaced in 
>> vim with the corresponding .lox file (which I find annoying).
>>
>> - Is that a bug or a feature? =)
>>
>> Thanks,
>> Felipe.
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft Defy all challenges. 
>> Microsoft(R) Visual Studio 2008. 
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>