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*') == ''
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
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
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
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:
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
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
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
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
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:
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
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
12 matches
Mail list logo
