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
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
I just commited a changeset to improve all this:
http://vim-latex.svn.sourceforge.net/viewvc/vim-latex?view=rev&revision=1039
Regards,
Till
signature.asc
Description: This is a digitally signed message part.
-
Check out the
>> 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
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
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
> 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-
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
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 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 the
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 wou
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 anywher
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 yo
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 yo
If you find yourself ":bd"ing very often (for example, for some reason
your TeX file gets buried or you :bd the wrong window or something like
that, you might want to use some of the other buffer commands.
Check out:
:help :b
In particular, try things like:
:b file
where "file" is enough of
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 b
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
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_scri
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 i
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
20 matches
Mail list logo
