Re: [Vim-latex-devel] compiling with wrong cross-references
It occurs to me that something else should probably be committed to the
repo.
As discussed on the vim-mac mailing list, on line 43 of compiler.vim,
there's a line that **SHOULD** be:
if !(has('win32') || has('macunix'))
(!Tex_GetVarValue('Tex_UseMakefile') || (glob('makefile*') == ''
glob('Makefile*') == ''))
In other words, *BOTH* Windows and Mac users should have the ability to
leave their view rules empty because the OS will automatically kick off
an associated viewer for them (using open for OS/X and start for
Windows, as discussed).
Of course, if we added the xdg-open stuff, this line would have to be
modified to allow Linux users to have empty view rules.
--Ted
Till Maas wrote:
I just commited a changeset to improve all this:
http://vim-latex.svn.sourceforge.net/viewvc/vim-latex?view=revrevision=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-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
--
Ted Pavlic [EMAIL PROTECTED]
-
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-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] compiling with wrong cross-references
I just commited a changeset to improve all this: http://vim-latex.svn.sourceforge.net/viewvc/vim-latex?view=revrevision=1039 Regards, Till signature.asc Description: This is a digitally signed message part. - 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] compiling with wrong cross-references
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=revrevision=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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel -- Ted Pavlic [EMAIL PROTECTED] - 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] compiling with wrong cross-references
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 [EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
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 with wrong cross-references
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 [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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 with wrong cross-references
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 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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 with wrong cross-references
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 signature.asc Description: This is a digitally signed message part. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ 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 with wrong cross-references
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 signature.asc Description: This is a digitally signed message part. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ 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 with wrong cross-references
Check out:
http://links.tedpavlic.com/shell_scripts/vimlatex
and/or
http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
LaTeX error messages have an interesting format. They use parentheses to
start a block of error messages. For example...
(file1.tex
(file2.tex included from file1.tex
information message posted from file2.tex)
error from file1.tex
)
When parsing these error messages, the parser has to keep track of which
block it's in. Vim's error parsing engine can handle this up until the
point where there are multiple closing parentheses on one line. That is,
if three blocks are closed at once with ))) on one line, Vim will only
see the first parentheses. So, when an error message from file3 comes
up, sometimes Vim THINKS it's an error message for file2.
The only good Vim fix to this problem is to pipe the LaTeX process
through a filter that prevents parentheses from stacking up. The
vimlatex script above will do that. Unfortunately, I've only had a
chance to implement that script for UNIX-like systems. Your e-mail looks
like it was generated with Thunderbird for Windows, so I'm guessing that
you're a Windows user. If that's the case, then you'll have to find a
Windows-compatible way to do the same thing. One solution would be to
install a few UNIX utilities that have been compiled for Windows. Namely:
*) bash
*) sed
If those two are available, you'll be able to use bash to execute that
vimlatex script.
To reconfigure Vim to use the vimlatex pipe, you'll have to add a line
to your .vimrc. See the LaTeX suite manual:
:help latex-suite
In particular, try:
:help compiler-rules
for more information. You'll have to use a line like...
let g:Tex_CompileRule_dvi = 'vimlatex latex -interaction=nonstopmode $*'
or, if you need to prefix it with bash:
let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex
-interaction=nonstopmode $*'
Does that get you on the right track?
--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/vse012070mrt/direct/01/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
--
Ted Pavlic [EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
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 with wrong cross-references
Hi Ted. Thank you for the detailed reply.
I think I'll keep splitting the vim window so that I can close the .lox
file when it's brought up. (I hear you say, Lazy this guy, eh?... =)
Thanks for the answer, though.
Felipe.
Ted Pavlic wrote:
Check out:
http://links.tedpavlic.com/shell_scripts/vimlatex
and/or
http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
LaTeX error messages have an interesting format. They use parentheses to
start a block of error messages. For example...
(file1.tex
(file2.tex included from file1.tex
information message posted from file2.tex)
error from file1.tex
)
When parsing these error messages, the parser has to keep track of which
block it's in. Vim's error parsing engine can handle this up until the
point where there are multiple closing parentheses on one line. That is,
if three blocks are closed at once with ))) on one line, Vim will only
see the first parentheses. So, when an error message from file3 comes
up, sometimes Vim THINKS it's an error message for file2.
The only good Vim fix to this problem is to pipe the LaTeX process
through a filter that prevents parentheses from stacking up. The
vimlatex script above will do that. Unfortunately, I've only had a
chance to implement that script for UNIX-like systems. Your e-mail looks
like it was generated with Thunderbird for Windows, so I'm guessing that
you're a Windows user. If that's the case, then you'll have to find a
Windows-compatible way to do the same thing. One solution would be to
install a few UNIX utilities that have been compiled for Windows. Namely:
*) bash
*) sed
If those two are available, you'll be able to use bash to execute that
vimlatex script.
To reconfigure Vim to use the vimlatex pipe, you'll have to add a line
to your .vimrc. See the LaTeX suite manual:
:help latex-suite
In particular, try:
:help compiler-rules
for more information. You'll have to use a line like...
let g:Tex_CompileRule_dvi = 'vimlatex latex -interaction=nonstopmode $*'
or, if you need to prefix it with bash:
let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex
-interaction=nonstopmode $*'
Does that get you on the right track?
--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/vse012070mrt/direct/01/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
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 with wrong cross-references
Note that the lox file should be brought up in a new *buffer*. That is,
you should be able to do
:ls
and see both your original source and the old TeX. Issuing the command:
:bd
should delete the new buffer and bring you back to your original TeX (in
most cases). If I'm ever on a machine that doesn't have vimlatex
installed, I find myself issuing :bd over and over again until I get
back to the original TeX.
Alternatively, you can tell Vim to not pay attention to compiler error
messages (or to ignore all but a very very small set of them). Though,
if you like the error messages, then that won't be a good thing to do. :)
--Ted
Felipe G. Nievinski wrote:
Hi Ted. Thank you for the detailed reply. I think I'll keep splitting
the vim window so that I can close the .lox file when it's brought
up. (I hear you say, Lazy this guy, eh?... =) Thanks for the
answer, though. Felipe.
Ted Pavlic wrote:
Check out:
http://links.tedpavlic.com/shell_scripts/vimlatex
and/or
http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
LaTeX error messages have an interesting format. They use
parentheses to start a block of error messages. For example...
(file1.tex
(file2.tex included from file1.tex information message posted from
file2.tex)
error from file1.tex
)
When parsing these error messages, the parser has to keep track of
which block it's in. Vim's error parsing engine can handle this
up until the point where there are multiple closing parentheses on
one line. That is, if three blocks are closed at once with ))) on
one line, Vim will only see the first parentheses. So, when an
error message from file3 comes up, sometimes Vim THINKS it's an
error message for file2.
The only good Vim fix to this problem is to pipe the LaTeX process
through a filter that prevents parentheses from stacking up. The
vimlatex script above will do that. Unfortunately, I've only had
a chance to implement that script for UNIX-like systems. Your
e-mail looks like it was generated with Thunderbird for Windows, so
I'm guessing that you're a Windows user. If that's the case, then
you'll have to find a Windows-compatible way to do the same thing.
One solution would be to install a few UNIX utilities that have
been compiled for Windows. Namely:
*) bash *) sed
If those two are available, you'll be able to use bash to execute
that vimlatex script.
To reconfigure Vim to use the vimlatex pipe, you'll have to add a
line to your .vimrc. See the LaTeX suite manual:
:help latex-suite
In particular, try:
:help compiler-rules
for more information. You'll have to use a line like...
let g:Tex_CompileRule_dvi = 'vimlatex latex
-interaction=nonstopmode $*'
or, if you need to prefix it with bash:
let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex
-interaction=nonstopmode $*'
Does that get you on the right track?
--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/vse012070mrt/direct/01/
___ Vim-latex-devel
mailing list Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
--
Ted Pavlic [EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
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 with wrong cross-references
Oh, :bd is great!
Thanks,
Felipe.
Ted Pavlic wrote:
Note that the lox file should be brought up in a new *buffer*. That is,
you should be able to do
:ls
and see both your original source and the old TeX. Issuing the command:
:bd
should delete the new buffer and bring you back to your original TeX (in
most cases). If I'm ever on a machine that doesn't have vimlatex
installed, I find myself issuing :bd over and over again until I get
back to the original TeX.
Alternatively, you can tell Vim to not pay attention to compiler error
messages (or to ignore all but a very very small set of them). Though,
if you like the error messages, then that won't be a good thing to do. :)
--Ted
Felipe G. Nievinski wrote:
Hi Ted. Thank you for the detailed reply. I think I'll keep splitting
the vim window so that I can close the .lox file when it's brought
up. (I hear you say, Lazy this guy, eh?... =) Thanks for the
answer, though. Felipe.
Ted Pavlic wrote:
Check out:
http://links.tedpavlic.com/shell_scripts/vimlatex
and/or
http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
LaTeX error messages have an interesting format. They use
parentheses to start a block of error messages. For example...
(file1.tex
(file2.tex included from file1.tex information message posted from
file2.tex)
error from file1.tex
)
When parsing these error messages, the parser has to keep track of
which block it's in. Vim's error parsing engine can handle this
up until the point where there are multiple closing parentheses on
one line. That is, if three blocks are closed at once with ))) on
one line, Vim will only see the first parentheses. So, when an
error message from file3 comes up, sometimes Vim THINKS it's an
error message for file2.
The only good Vim fix to this problem is to pipe the LaTeX process
through a filter that prevents parentheses from stacking up. The
vimlatex script above will do that. Unfortunately, I've only had
a chance to implement that script for UNIX-like systems. Your
e-mail looks like it was generated with Thunderbird for Windows, so
I'm guessing that you're a Windows user. If that's the case, then
you'll have to find a Windows-compatible way to do the same thing.
One solution would be to install a few UNIX utilities that have
been compiled for Windows. Namely:
*) bash *) sed
If those two are available, you'll be able to use bash to execute
that vimlatex script.
To reconfigure Vim to use the vimlatex pipe, you'll have to add a
line to your .vimrc. See the LaTeX suite manual:
:help latex-suite
In particular, try:
:help compiler-rules
for more information. You'll have to use a line like...
let g:Tex_CompileRule_dvi = 'vimlatex latex
-interaction=nonstopmode $*'
or, if you need to prefix it with bash:
let g:Tex_CompileRule_dvi = 'bash \path\to\vimlatex latex
-interaction=nonstopmode $*'
Does that get you on the right track?
--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/vse012070mrt/direct/01/
___ Vim-latex-devel
mailing list Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
