Re: [Vim-latex-devel] "jump to error" doesn't jump

[Martin Sander]

Hey list.
Like others I have been annoyed by the non-working "jump 
to error" behaviour in the quickfix window, and although I 
am not a hacker I found a workaround (it hasn't undergone 
any testing yet, but it works for my little project now).

I do
:let g:Tex_CompileRule_dvi='latex -interaction=nonstopmode 
-file-line-error $*'

(the difference to the default is the -file-line-error)
this gives output like this:

...
./foo.tex:8: Undefined control sequence.
l.8   \foo
...

instead of
! Undefined control sequence.
l.8 \foo

So one does not need all that pushing and popping 
filenames at all, just another statement in 
compiler/tex.vim to match the new format:

--- /usr/share/vim/addons/compiler/tex.vim  2007-06-12 
15:32:12.0 +0200
+++ tex.vim 2007-06-12 15:44:27.0 +0200
@@ -202,6 +202,7 @@
  
 setlocal efm+=%E!\ LaTeX\ %trror:\ %m
 setlocal efm+=%E!\ %m
+   setlocal efm+=%E%f:%l:\ %m
  
 setlocal efm+=%+WLaTeX\ %.%#Warning:\ %.%#line\ 
%l%.%#
 setlocal efm+=%+W%.%#\ at\ lines\ %l--%*\\d


I guess one can get rid of some other rules that are not 
needed anymore.
This could be a good simplification, but I don't know how 
portable it is (maybe not every "latex" has 
-file-line-error ..).

btw. I am using version 20060325-1 on ubuntu edgy eft.

Cheers Martin

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] same target file, different ways to compile?

[Martin Sander]

If you use some *nix, you can do what I did with a similar problem.
You may know that when you use more than one source file, you can
specify the main (lets say its foo.tex) file by creating an empty
foo.tex.latexmain file.
So just create this file, and put a string in it describing your change,
e.g. "beamer".
Then put something like this in your ~/.vim/after/ftplugin/tex.vim

if ( system("echo -n `cat *.tex.latexmain`") =~ 'beamer' )
unlet g:Tex_FormatDependency_pdf
let g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*'
endif

This is very fragile (you should only have one latexmain file, it should
only contain this one word, it has to be in the directory where you
started vim, etc etc), but it works for me.
I know there are certainly are a lot of much more elegant ways to parse
a file though..


Martin
P.S.: why don't you use dvi for all you previewing and ONE call of
dvips/ pstopdf in the end when you want to print your doc?

On Sun, Jun 17, 2007 at 10:53:48AM +0800, anhnmncb wrote:
> hello list,
> I prefer the way "dvi->dvips->pdf" to generate my ordinary document, 
> I find in this way the size of pdf i
> s small. But latex-suite compiles pdf using pdflatex by default, So I have to 
> set:
> let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
> let g:Tex_DefaultTargetFormat = 'pdf'
> let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'
> 
> When I prepare my slides using  beamer class, I prefer pdflatex to 
> latex because I find the graphics qual
> ity is higher than dvips. As you know, I have set the compilerule for pdf, so 
> I can't generate pdf using pdflatex
>  conventionally. I want to know how to resolve such problem?

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] jump to error suggestion explained in detail

[Martin Sander]

Hey. I'm glad that somebody read my mail.

On Wed, Aug 29, 2007 at 01:06:59AM -0400, Jushan Bai wrote:
> I notice that  you proposed a solution to the "jump to error" problem.
> But I'm a novice about the latexsuite setups and environment variables
> etc. I'm using vim78.0 + miktex 2.5 + windows xp.

Note that I only tested my suggestion with Ubuntu Linux and tetex, so it
might not work with miktex at all. Maybe you should consider reading the
miktex documentation if their latex command supports the
-file-line-error flag.
If you get it to work in windows please let the vim-latex mailinglist
know about it so that others can profit, too.

> In which latexsuite script I should make the suggested changes?

For testing purposes, you can just do a

:let g:Tex_CompileRule_dvi='latex -interaction=nonstopmode -file-line-error $*'

in vim.
If it all works, you can add that statement without the : in your vimrc,
or somewhere else, e.g. ~/.vim/after/ftplugin/tex.vim, thats where I
have put it.
(Your path might be different, I don't know about windows. The vim
documentation about paths should be a good place to start reading about
it, also :help compiler-rules is not a bad idea)

> and where do I add or change or delete the following statement?  I
> have no idea what they mean at all:

The statement that you meant: 
--- 8< -

--- /usr/share/vim/addons/compiler/tex.vim  2007-01-29
13:39:58.0 +0100
+++ /home/lennox/.vim/compiler/tex.vim  2007-06-14 23:33:33.0
+0200
@@ -202,6 +202,7 @@ function! SetLatexEfm()
 
setlocal efm+=%E!\ LaTeX\ %trror:\ %m
setlocal efm+=%E!\ %m
+   setlocal efm+=%E%f:%l:\ %m
 
setlocal efm+=%+WLaTeX\ %.%#Warning:\ %.%#line\ %l%.%#
setlocal efm+=%+W%.%#\ at\ lines\ %l--%*\\d

 >8 

Is a patch made with the command
diff -u /usr/share/vim/addons/compiler/tex.vim ~/.vim/compiler/tex.vim

It shows the difference between the official
/usr/share/vim/addons/compiler/tex.vim 
and the one that I changed and put in my home directory
(~/.vim/compiler/tex.vim), with some context to improve readability.
so lines with blanks in the first column mean unchanged lines (context),
lines with "+" have to be added, lines with "-" have to be erased. See [1].

On any *nix you could use the "patch" [2] command to make these changes, but
as its just one line you can just add it with your favourite text editor
(I'd suggest vim, but as you use windows you may be a masochist and want
to use notepad instead ;-)...).

It basically just means that you have to add the line that begins with
the "+" in the shown context (btw. the 202 is a line number, so :202
will get you there in vim).
If you have installed the latex-suite like described here:
http://vim-latex.sourceforge.net/index.php?subject=download&title=Download
the file that you have to edit should be:
vimfiles\compiler\tex.vim

> Thanks for your help.

You're welcome. I hope you can understand my lengthy description.
If you want to know what it all means look for documentation on
-file-line-error in miktex, and maybe do a :help efm in vim.

Cheers

Martin

[1] http://en.wikipedia.org/wiki/Diff#Context_format
[2] http://en.wikipedia.org/wiki/Patch_%28Unix%29

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[Martin Sander]

Do you have a file called "makefile" or "Makefile" in your working
directory? If so, do a 

:let Tex_UseMakefile=0

in vim and try again.
See :help Tex_UseMakefile

Cheers

Martin

On Mon, Nov 12, 2007 at 02:29:55PM +0100, Kai Lessmann wrote:
> Hello, I'm looking for help with invoking latex from VIM-LaTeX
> using the "\ll" shortcut.
> 
> I've tried to narrow down the problem following the FAQ on
> http://vim-latex.sourceforge.net and I'm listing my answers
> to the question asked there below in this mail.
> 
> The short story is that calling latex from within vim works
> fine (using :!latex -interaction=nonstopmode %)
> but calling :call Tex_RunLaTeX() does not work, its output is
> 
> Running 'bibtex' ...
> Ran latex 1 time(s)
> 
> but the dvi file does not change.
> 
> Thanks in advance,Kai

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] output of xdvi shows in tex-file

[Martin Sander]

Hey.
Workarounds:

a) use gvim. Usuallally I use terminal-vim all the time, but for LaTeX I
prefer gvim because it does not show console output  and because I found
it easier to set up forward and backward searching.

b) $ head .Xdefaults

xdvi.hushStdout: true

some other useful (for me at last) settings for .Xdefaults:

xdvi.editor: gvim --servername %f --remote-silent +%l %f

xdvi.wheelTranslations: : forward-page()\n \
:back-page()\n

xdvi.mainTranslations: #override \
Ctrl: source-special()\n \
: do-href()drag(+)\n 
!: magnifier(*3)\n

xdvi.keepPosition: true

see xdvi(1) for all these cryptic settings.

happy vimming

Martin

On Fri, Nov 16, 2007 at 12:14:52PM +0100, Qiuye Wang wrote:
> Hello list,
> 
> when i press \lv or \ls in vim, ie launch the xdvi i always got the
> output info of xdvi in the line of my tex file, where the cursor were.
> It's really annoying although they just show temporary (they will
> disappear if i move the cursor down or up till they are out of the
> sight).
> 
> i know this is the issue of xdvi, but is there any way that i can
> prevent the output of appearing in my tex ie vim window?
> 
> Thank you.
> 
> Cheers
> QY

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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] text clobbered in vim (but not gvim)

[Martin Sander]

Hey, this annoyed me to (a lot). I don't remember that this has always
been like this, maybe it has been introduced by vim 7.1.
Anyways, my workaround was using gvim, but now you got me motivated to
search for a real solution, and I found it:

$ tail -2 .vim/after/ftplugin/tex.vim
"refresh after compiling..
:nnoremap  Tex_Compile :call Tex_RunLaTeX()\|redraw!

(I found that in latex-suite/compiler.vim:796).
A caveat is that you won't see the "compiled latex  times" message.

Bye

Martin

On Sun, Nov 18, 2007 at 11:14:43PM +, Stephen Wilkinson wrote:
> Hello everyone,
> 
> I normally use gvim with vim-latex, but I recently I tried vim (i.e.
> without the GUI), and when compiling with \ll or opening the viewer
> with \lv, messages from the external programs clobber the text in the
> vim window.
> 
> For instance when compiling, I get:
> This is BibTeX, Version 0.99c (Web2C 7.5.4)
> The top-level auxiliary file: test.aux
> The style file: plain.bst
> Database file #1: test.bib
> 
> at the bottom of the Vim window, and the text in the buffer
> "disappears"... it's still there and I can move the cursor over it,
> but it's invisible. If I use :redraw! all is well again (or else if I
> change buffer, or split the window, or invoke help, any of these
> probably cause redraw to be called and make the text reappear).
> 
> Does anyone else have this problem? Can anyone suggest how I can make
> the redraw automatic? I thought of adding :redraw! at the end of the
> Tex_RunLaTeX and Tex_ViewLaTeX functions in
> ftplugin/latex-suite/compiler.vim but I would prefer not to edit the
> vim-latex files (as I'll lose changes at the next upgrade).
> 
> Any suggestions welcome!
> Thanks, Steve

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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] text clobbered in vim (but not gvim)

[Martin Sander]

On Tue, Nov 20, 2007 at 01:29:41PM +, Stephen Wilkinson wrote:
> I don't know how to > test for "if not" so I've put the statement in
> the "else" part

 if !has("gui_running")
 :nnoremap  Tex_Compile :call Tex_RunLaTeX()\|redraw!
 endif

by the way, I added another  to the end of the line because I got
one of these annoying "Press ENTER or type command to
continue"-prompts..

> Martin, I saw your reply to the thread "output of xdvi shows in tex file" -
> and thought maybe the same trick would apply. I get the same problem with
> xdvi writing its output into my tex file

Well, I guess you have seen the

xdvi.hushStdout: true

Setting for .Xdefaults already. If xdvi still writes to stderr, you could
try

$ alias xdvi="xdvi 2>/dev/null"

This should work as
 
  $ xdvi 2>/dev/null somefilethatisnotdvi

does not print anything (while it does without redirection). You are on
a *nix system, aren't you?

> Thanks for your help,

You're welcome. I have profited so much from the FLOSS community that I
am glad I can help some other people myself. Good for my Karma (not that
I am a Buddhist, rather a fan of "My Name is Earl").

Martin

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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] Installation on Ubuntu

[Martin Sander]

On Wed, Dec 19, 2007 at 11:55:43AM +0100, Sebastian Menge wrote:
> the version is outdated. Current version in
> Ubuntu (and probably Debian) is "20060325-3".

No it is not, see [1]:
Latest version of Latex-Suite:
* latexSuite20060325.tar.gz (212.3 Kb; March 25, 2006)

> Is there no active package maintainer for a debianized vim-latex-suite?

Actually debian even patched latex-suite, I don't know if these patches
are going upstream though. The latest patch in the changelog that is not
debian-specific is from jan 16th.

Happy vimming

Martin

[1] http://vim-latex.sourceforge.net/index.php?subject=download&title=Download


-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] F9 bibtex completion

[Martin Sander]

> I have some trouble with the F9 completition of my bibtex items under Ubuntu
> 7.10.
> When I write \cite{ and F9 an empty preview window comes up. (My bib file is
> setup correctly)
> For the \ref{ command it works.
> 
> I also installed the latest version in my .vim folder (removing the ubuntu
> package before) but this didn't change anything.
> Can anyone reproduce this?

Works perfectly for me.
How are you including your .bib-file, with extension or without?

By the way it would be nice if you started a new thread when you ask a
question that is unrelated to the ones that was asked before (okay, you
are also using Ubuntu 7.10, but that one was not about bibtex at all).

Happy vimming

Martin

-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] annoying press-enter-or-command message when inverse searching

[Martin Sander]

Hey list.

I have spent some time now and it is really annoying.
When I do inverse searching from xdvi (which was hard to set up in the
first place..), I get this awful annoying 

"Press ENTER or type command to continue"

message most of the time, although there is no long message shown.
I have done all that is suggested in ":help press-enter".

It seems to me that vim does something like ":file" when you call
--remote-silent, and I can't find a way to turn that off..

Does anybody have any ideas?

Sorry if I don't make any sense, its late..


Martin

-
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] Extra double quote within align environments

[Martin Sander]

On Fri, Mar 07, 2008 at 05:19:27PM -0600, Rhys Ulerich wrote:
> Is anyone else experiencing an extra double quote within align*
> environments?  E.g.,
>   \begin{align*}
>   "
>   \end{align*}<++>
> after the environment insertion ends.
> 
> It occurs when hitting F5 and selecting align or align* (options 7/8) from
> the list. Typing either environment name first and hitting F5 doesn't
> behave the same way.  Vim version 7.1 off the latest CVS.

Its does not only affect align environments, it affects all I have
tried. $$ gives even stranger results:

\begin{document}
"`$$$X
\end{document}

if there are jumpmarks the behaviour is even worse.
Vim 7.1.56, ubuntu 7.10.

Martin

-
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] calling makeindex during compilation

[Martin Sander]

If you are familiar with make(1) and Makefiles, I would recommend giving
them a try.  It should't be to big of a hassle to write one, and
latex-suite automatically uses the Makefile if it exists in your working
directory.

I think your Makefile would look like this (I did not test it, never
used nomenclature before):

all: mydoc.dvi

mydoc.dvi: mydoc.nls
latex -interaction=nonstopmode mydoc.tex

mydoc.nls: mydoc.nlo nomencl.ist
makeindex mydoc.nlo -s nomencl.ist -o mydoc.nls

mydoc.nlo: mydoc.tex
latex -interaction=nonstopmode mydoc.tex

clean:
-rm -rf mydoc.dvi

.PHONY: clean

(don't just copy and paste, there has to be a TAB in front of every
rule, not a number of SPACES (if you don't know what I am talking about,
read an introduction to Makefiles).
Of course you could write the Makefile much more generally, but that
wouldn't help readability. There are tons of documentation on Makefiles
on the internet..

I guess you could do something similar with latex-suites compiler
dependency stuff (see :help compiler-dependency), setting the chain to
nlo,nls,dvi and setting compilation rules for .nls and .nlo. That would
be your homework.

Happy hacking (and vimming)

Martin


On Thu, Apr 10, 2008 at 05:28:26PM -0300, Felipe G. Nievinski wrote:
> Hi.
> 
> I'm using the "nomenclature" latex package [1].
> 
> It requires the following command
> 
>  makeindex mydoc.nlo -s nomencl.ist -o mydoc.nls
> 
> in between latex runs.
> 
> Could you give me a hint on how I could use the Vim-Latex suite to
> automatize that intermediary call to makeindex, please? I'd like to keep 
> doing simply \ll, then.
> 
> I've tried searching at the mailing list archive, to no avail.
> 
> Thanks,
> Felipe.
> 
> [1] 
> A snippet:
> The creation of the nomenclature list is very similar to the creation of
> an index [6, App. A]. You need to:
>  o  Put \usepackage[hoptionsi]{nomencl} in the preamble of your
> document.
>  o  Put \makenomenclature in the preamble of your document.
>  o  Issue the \nomenclature command (see Section 2.2) for each
> symbol you want to have included in the nomenclature list.
>  o  Put \printnomenclature at the place you want to have your
> nomenclature list.
> 
> Now put your file through LATEX. The command \makenomenclature will
> instruct LATEX to open the nomenclature file .nlo
> corresponding to your LATEX file .tex and to write the
> information from your \nomenclature commands to this file.
> 
> The next step is to invoke MakeIndex. You should instruct MakeIndex to
> use .nlo as your input file, use nomencl.ist as your style
> file, and write output to the file .nls. How to do this
> depends on your implementation of MakeIndex. For most UNIX
> implementations you should write something like
>  makeindex .nlo -s nomencl.ist -o .nls
> 
> Now you have the file .nls that contains your nomenclature
> list properly ordered. The last step is to invoke LATEX on your master
> file .tex once more. It will input your .nls file and process
> it accordingly to the current options. That’s all!
> 
> 
> -
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> ___
> 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 the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
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

[Martin Sander]

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

-
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

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

[Martin Sander]

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

-
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] [ vim-latex-Bugs-1997889 ] `[, `(, `{ shortcuts mess up identation

[Martin Sander]

On Thu, Jun 19, 2008 at 02:02:09PM +, SourceForge.net wrote:
> Summary: `[,`(,`{ shortcuts mess up identation
> 
> Initial Comment:
> this is a matrix i tried to add parentheses or brackets to

Thanks for the minimal example...

Anyways, just wanted to mention that the bug disappears using :set paste
(which obviously is no solution).

Cheers

Martin

-
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] Compilation

[Martin Sander]

On Wed, Jun 18, 2008 at 01:14:10PM -0400, Ted Pavlic wrote:
> >>> :map \lz \ll\lv
>
> By putting that  in there, it should get you passed some of the
> "Press enter to continue" prompts after compilations. I don't use this
> method. It's just a guess.

In .vim/after/ftplugin/tex.vim:

if !has("gui_running")
  :nnoremap  Tex_Compile :call Tex_RunLaTeX()\|
endif

But it worked a lot better in vim 7.0, now I have to press enter once in
a while.

Also, the earlier mentioned

>> call Tex_MakeMap(s:ml."lz", "Tex_SaveCompileView", 'n',
>> '')

Is not necessary, see:
:help autowrite

Happy vimming

Martin


-
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