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

[Vim-latex-devel] Extra double quote within align environments

[Rhys U. <rhy...@gm...>]

Hi all,

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.

- Rhys

Re: [Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

[Christian E. <bla...@gm...>]

Hi Ted,

* Ted Pavlic on Friday, March 07, 2008 at 17:00:04 -0500
> Check out the solution at:
> 
> http://links.tedpavlic.com/shell_scripts/vimlatex

Very neat.

> I implemented the sed scripts with single quotes to help make the 
> "trick" documented on that page a little more clear.

Yup. You beat me to it. Single quotes are much easier to handle
as long as you don't /have/ to use double quotes.

> The "trick" puts a "\" at the end of the sed script and then inserts a 
> NEWLINE right in the middle of the string. The "\" somehow tells the 
> shell (or sed) to continue to the next line before assembling the string.
> 
> So, really all you need is something like...
> 
> sed -e 's/blah/\'$'\n''stuff/'
> 
> which will replace "blah" with a newline and then "stuff".

Thanks for clarifying.

> Hopefully that will do it.

Works like a charm with both Apple shipped sed and gsed.

> Side notes:
> 
> 1. The OS/X sed has no trouble MATCHING a newline with \n)

Ah, right.

> 2. I changed the ORDER of the search strings. I also added a SECOND 
> search string for catching numbers split across lines. It's meant to 
> catch lines like:
> 
> things 12
> 34 stuff 56
> 78 other things
> 
> Now, if that pattern continues, it will miss a few. I'm hoping that just 
> catching three lines in a row will be sufficient. A better solution 
> would be to use perl... but I don't know what's included with OS/X 
> without installing the developer tools. :(

Python and Perl are included; the libs are in a non-standard
location: /Library/Perl/... But for for executing scripts you
should be fine. Still for these tasks sed and awk are way cooler
and faster.

c
-- 
__   _    _         _  __  _               _    
\ \ | |__| |__ _ __| |_\ \| |_ _ _ __ _ __| |_  
 \ \| '_ \ / _` / _| / /\ \  _| '_/ _` (_-< ' \   http://www.blacktrash.org/
  \_\_.__/_\__,_\__|_\_\ \_\__|_| \__,_/__/_||_|  Jabber-ID: bla...@gm...

Re: [Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

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

Check out the solution at:

http://links.tedpavlic.com/shell_scripts/vimlatex

I implemented the sed scripts with single quotes to help make the 
"trick" documented on that page a little more clear.

The "trick" puts a "\" at the end of the sed script and then inserts a 
NEWLINE right in the middle of the string. The "\" somehow tells the 
shell (or sed) to continue to the next line before assembling the string.

So, really all you need is something like...

sed -e 's/blah/\'$'\n''stuff/'

which will replace "blah" with a newline and then "stuff".

Hopefully that will do it.


Side notes:

1. The OS/X sed has no trouble MATCHING a newline with \n)

2. I changed the ORDER of the search strings. I also added a SECOND 
search string for catching numbers split across lines. It's meant to 
catch lines like:

things 12
34 stuff 56
78 other things

Now, if that pattern continues, it will miss a few. I'm hoping that just 
catching three lines in a row will be sufficient. A better solution 
would be to use perl... but I don't know what's included with OS/X 
without installing the developer tools. :(


Thanks, again --
Ted

Christian Ebert wrote:
> * Ted Pavlic on Friday, March 07, 2008 at 14:39:10 -0500
>> Here's an interesting solution...
>>
>> http://www.culmination.org/2008/02/10/sed-on-mac-os-x-105-leopard/
> 
> Indeed.
> 
>> Use:
>>
>> \\”$’\n’”\
>>
>> instead.
>>
>> I'll make that change and update.
> 
> I'm eager to know how you do it.
> 
> I get
> ": unescaped newline inside substitute pattern
> 
> Also, IIRC, you have to use [0-9][0-9]* instead of [0-9]\+.
> [0-9]\{1,\} works on MacOS, but breaks on other machines.
> 
> c

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

Re: [Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

[Christian E. <bla...@gm...>]

* Ted Pavlic on Friday, March 07, 2008 at 14:39:10 -0500
> Here's an interesting solution...
> 
> http://www.culmination.org/2008/02/10/sed-on-mac-os-x-105-leopard/

Indeed.

> Use:
> 
> \\”$’\n’”\
> 
> instead.
> 
> I'll make that change and update.

I'm eager to know how you do it.

I get
": unescaped newline inside substitute pattern

Also, IIRC, you have to use [0-9][0-9]* instead of [0-9]\+.
[0-9]\{1,\} works on MacOS, but breaks on other machines.

c
-- 
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>

Re: [Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

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

Here's an interesting solution...

http://www.culmination.org/2008/02/10/sed-on-mac-os-x-105-leopard/

Use:

\\”$’\n’”\

instead.

I'll make that change and update.

Thanks!
--Ted

Ted Pavlic wrote:
>> Note, however, that by using sed you encounter portability
>> issues! For me, on MacOS 10.4.11, the script only works because I
>> have GNU Sed (gsed) installed. Apple shipped sed in /usr/bin
>> can't handle "\n".
>>
>> For portability you might want to wrap this in python or perl.
> 
> Another good point. However, does OS/X ship with python or perl 
> standard? For portability, I think I'd want to use a utility standard 
> with them all.
> 
> I may just have to suck it up and encode a newline (rather than a \n) in 
> the script (and stick with sed). :(
> 
> Thoughts?
> 
> Thanks --
> Ted
> 
> 
> 

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

Re: [Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

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

> Note, however, that by using sed you encounter portability
> issues! For me, on MacOS 10.4.11, the script only works because I
> have GNU Sed (gsed) installed. Apple shipped sed in /usr/bin
> can't handle "\n".
> 
> For portability you might want to wrap this in python or perl.

Another good point. However, does OS/X ship with python or perl 
standard? For portability, I think I'd want to use a utility standard 
with them all.

I may just have to suck it up and encode a newline (rather than a \n) in 
the script (and stick with sed). :(

Thoughts?

Thanks --
Ted



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

Re: [Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

[Christian E. <bla...@gm...>]

Ted,

* Ted Pavlic on Friday, March 07, 2008 at 12:48:46 -0500

[ replace pipe thru sed instances by several -e ]

> That's an EXCELLENT suggestion. I've implemented it and updated all 
> on-line versions (with credit to you in the comments/version history).

Heh, I'm flattered.

Note, however, that by using sed you encounter portability
issues! For me, on MacOS 10.4.11, the script only works because I
have GNU Sed (gsed) installed. Apple shipped sed in /usr/bin
can't handle "\n".

For portability you might want to wrap this in python or perl.

c
-- 
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>

Re: [Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

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

Christian --

	That's an EXCELLENT suggestion. I've implemented it and updated all 
on-line versions (with credit to you in the comments/version history).

	Thanks! --
	Ted

> Instead of piping through several sed instances, repeat -e -- The
> line continuation is personal taste.
> 
> Or have you already tried this, and it breaks?

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

Re: [Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

[Christian E. <bla...@gm...>]

Hi Ted,

* Ted Pavlic on Friday, March 07, 2008 at 10:10:05 -0500
> It's well-known (yet not often discussed) that Vim has a hard time 
> parsing LaTeX error messages because they are nested within parentheses, 
> and multiple nests can closed on a single line (e.g., you can find ")))" 
> on a single line). When these nest closings do not get parsed correctly 
> by Vim, then Vim-LaTeX will open the wrong file when it encounters an 
> error.
> 
> 
> I've put together a wrapper (implemented with bash) to filter latex 
> error messages to fix this problem:
> 
> http://links.tedpavlic.com/shell_scripts/vimlatex

Very neat! Thanks for your efforts at keeping vim-latex alive
anyway.

How about:


--- vimlatex.orig	2008-03-07 18:03:11.000000000 +0100
+++ vimlatex	2008-03-07 18:07:20.000000000 +0100
@@ -41,7 +41,8 @@
 shift
 
 exec 3>&1
-retcode=$( exec 4>&1; { ${texprg} "$@"; echo $? >&4; } | sed -e "s/(/\n(/g" | sed -e "s/)/)\n/g" | sed -e "/[0-9]\+$/{N;s/\n\([0-9]\+\)/\1/;}" >&3)
+retcode=$( exec 4>&1; { ${texprg} "$@"; echo $? >&4; } \
+| sed -e "s/(/\n(/g" -e "s/)/)\n/g" -e "/[0-9]\+$/{N;s/\n\([0-9]\+\)/\1/;}" >&3)
 exec 3>&-
 
 exit ${retcode}



Instead of piping through several sed instances, repeat -e --
The line continuation is personal taste.

Or have you already tried this, and it breaks?

c
-- 
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>

[Vim-latex-devel] [vim-latex - Help] Script to fix compiler error messages for VIM

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=4822389
By: neodore

It's well-known (yet not often discussed) that Vim has a hard time parsing LaTeX
error messages because they are nested within parentheses, and multiple nests
can closed on a single line (e.g., you can find ")))" on a single line). When
these nest closings do not get parsed correctly by Vim, then Vim-LaTeX will
open the wrong file when it encounters an error.


I've put together a wrapper (implemented with bash) to filter latex error messages
to fix this problem:

http://links.tedpavlic.com/shell_scripts/vimlatex

I've also posted this script at vim.org.


I've put some additional information at:

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

At least one other similar script exists on the web. However, because bash pipelines
return the rightmost return code, those scripts often require writing to a temporary
file in order for the wrapper to return whatever latex returns. My script uses
a bash file descriptor trick to get around using temporary files.


I hope this is helpful to someone.
--Ted


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=173627

[Vim-latex-devel] Script to fix compiler error messages for VIM-LaTeX

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

It's well-known (yet not often discussed) that Vim has a hard time 
parsing LaTeX error messages because they are nested within parentheses, 
and multiple nests can closed on a single line (e.g., you can find ")))" 
on a single line). When these nest closings do not get parsed correctly 
by Vim, then Vim-LaTeX will open the wrong file when it encounters an 
error.


I've put together a wrapper (implemented with bash) to filter latex 
error messages to fix this problem:

http://links.tedpavlic.com/shell_scripts/vimlatex

I've also posted this script at vim.org.


I've put some additional information at:

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

At least one other similar script exists on the web. However, because 
bash pipelines return the rightmost return code, those scripts often 
require writing to a temporary file in order for the wrapper to return 
whatever latex returns. My script uses a bash file descriptor trick to 
get around using temporary files.


I hope this is helpful to someone.
--Ted


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

[Vim-latex-devel] [vim-latex - Help] RE: Strange behavior when typing dot or comma

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=4822367
By: polyformal_sp

Hello folks,

i finally got rid of this. The problem comes from the vimspell 
plugin [1] , and i found that since vim >= 7 i don't need this plugin
anymore [2] and [3].

[1] http://www.vim.org/scripts/script.php?script_id=465
[2] http://www.linux.com/articles/54068
[3] http://slip-shod.blogspot.com/2006/05/vim-7-launched.html

My setup was Debian lenny, vim 7.1.245 

best regards

Stefan Pampel


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=173627

[Vim-latex-devel] [vim-latex - Help] RE: Strange behavior when typing dot or comma

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=4822252
By: marvinthepa

First of all, a little bit more information would have been nice, e.g. operating
system, version of vim that you are using, version of latex-suite, if you installed
latex-suite with package-management or by hand, system-wide or in your home
directory.

I vaguely remember having the same problem a long time ago, but I don't know
how I solved it. jfgi found this though:

http://ubuntuforums.org/showthread.php?t=259385

So maybe it is a problem with your version of vim.

Good luck and happy vimming

Martin

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=173627

[Vim-latex-devel] [vim-latex - Help] Strange behavior when typing dot or comma

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=4821789
By: polyformal_sp

Hello,

first, vim-latex ist nice to handle latex documents ;)

But i have an issue when typing documents:

Typing a '.' (dot) or ',' (comma) these signs appears on the right side of the
cursor when continue typing. So i have to use the cursor to right if i want
continue typing on the right side of the dot or comma, otherwise typing continues
on the left side of commy or dot.

This behavior is only in tex documentes  while installed the latexsuite plugin.

some hints?

Thanks and best regards

Stefan Pampel


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=173627

[Vim-latex-devel] Preventing compiler from opening wrong file on error

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

	Vim has a hard time parsing TeX output of the form...

(file
(file
(file
)))

(i.e., nested output where all of the closing parentheses come on one 
line). So, Vim-LaTeX tends to open the wrong file on compiler errors.

I've put together a simple-to-use script to try to fix this. See:

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

and, for the script:

http://links.tedpavlic.com/shell_scripts/vimlatex

Then add "vimlatex" to the front of any compiler command you use. For 
example, if you've been executing:

latex blah blah blah

then execute:

vimlatex latex blah blah blah

instead.

	This isn't a new idea. However, it's an idea that's hard to find on the 
web.

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

Re: [Vim-latex-devel] update header file.

[Daniele A. <d.a...@gm...>]

I believe the following link may help

http://www.vim.org/scripts/script.php?script_id=1172

Best wishes.

Daniele

On Thu, Feb 21, 2008 at 12:57 PM, davide <lis...@gm...> wrote:

> On Wed, Feb 20, 2008 at 3:19 PM, Ted Pavlic <te...@te...> wrote:
> > You should post to the main Vim list, as this is a Vim question and not
> > a vim-latex question. I'm guessing that some of the Vim-experts will
> > have a method (that applies more broadly than to just TeX files).
>
> Ok, thank you very much.
>
> I'll repost in the main Vim list.
>
> -------------------------------------------------------------------------
> 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
>

Re: [Vim-latex-devel] update header file.

[davide <lis...@gm...>]

On Wed, Feb 20, 2008 at 3:19 PM, Ted Pavlic <te...@te...> wrote:
> You should post to the main Vim list, as this is a Vim question and not
> a vim-latex question. I'm guessing that some of the Vim-experts will
> have a method (that applies more broadly than to just TeX files).

Ok, thank you very much.

I'll repost in the main Vim list.

Re: [Vim-latex-devel] update header file.

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

You should post to the main Vim list, as this is a Vim question and not 
a vim-latex question. I'm guessing that some of the Vim-experts will 
have a method (that applies more broadly than to just TeX files).

That being said, revision control systems as old as RCS can look for 
keywords within your files and update them on check-ins. For example:

$Revision: 1.10 $

will get updated automatically by RCS.

--Ted

davide wrote:
> Hi, I would like to know if it is possible to update automagically
> the header of a latex file as the following one.
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -*- Mode: Latex -*-
> %%%%%%%%%%%%%%%%%%%%%%%%%%%% %% file.tex --- %% Author          :
> First Name %% Created On      : Mon Feb 24 03:00 PM 2006 C %% Last
> Modified By: Friend of First Name %% Last Modified On: Tue Feb 29
> 15:28:45 CET 2007 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> 
> 
> I think the header was generated by emacs.
> 
> thank you.
> 
> -------------------------------------------------------------------------
>  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...>

[Vim-latex-devel] update header file.

[davide <lis...@gm...>]

Hi,
I would like to know if it is possible to update automagically the
header of a latex file as the following one.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -*- Mode: Latex -*- %%%%%%%%%%%%%%%%%%%%%%%%%%%%
%% file.tex ---
%% Author          : First Name
%% Created On      : Mon Feb 24 03:00 PM 2006 C
%% Last Modified By: Friend of First Name
%% Last Modified On: Tue Feb 29 15:28:45 CET 2007
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


I think the header was generated by emacs.

thank you.

Re: [Vim-latex-devel] \lv and opening problems in Mac OS

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

>> 2. \lv When using \lv, instead of opening the file it gives a bunch
>> of errors. On the vim-latex documentation, it says that the system
>> should open it automatically (I didn't customize it yet). Why isn't
>> this working? I am using Mac OS X Tiger.
> 
> See:
> 
> http://phaseportrait.blogspot.com/2007/07/vim-latex-modification-forward.html
> 
> Make the modifications described there, and I think you'll be on your way.


NOTE: Those modifications assume that you're using Skim, PDFView, or 
TeXniscope as your viewer.

It *could* be changed to support Preview or Adobe too, but I don't quite 
see the point (especially with Preview).

If you're doing LaTeX work on OSX, you should be using a viewer like 
those. All of them support auto-reloading of PDFs, so your PDF will 
automatically refresh at every change. In Preview, it's difficult to 
even *FORCE* a refresh.

--Ted



>> Thanks in advance, Mars
>>
>>
>> ---
>>
>> Hwasung Mars Lee
>>
>> Mathematical Institute, Oxford University, 24-29 St Giles', Oxford,
>> OX1 3LB, United Kingdom
>>
>> It is by logic that we prove, but by intuition that we discover. -
>> Henri Poincaré
>>
>>
>> _________________________________________________________________ 
>> Share what Santa brought you https://www.mycooluncool.com 
>> -------------------------------------------------------------------------
>>  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] \lv and opening problems in Mac OS

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

> 1. When opening a file When opening a file in Mac OS, I have to press
> enter after vim tells me what file it is opening. After I press
> enter, it finally shows the contents to me. This doesn't happen when
> I am using Linux, what's going wrong? I am using vim 7.1.

This is a problem with the traditional gvim. There are several 
workarounds, but they don't work 100% of the time.

Try MacVim instead:

http://code.google.com/p/macvim/


> 2. \lv When using \lv, instead of opening the file it gives a bunch
> of errors. On the vim-latex documentation, it says that the system
> should open it automatically (I didn't customize it yet). Why isn't
> this working? I am using Mac OS X Tiger.

See:

http://phaseportrait.blogspot.com/2007/07/vim-latex-modification-forward.html

Make the modifications described there, and I think you'll be on your way.

--Ted



> Thanks in advance, Mars
> 
> 
> ---
> 
> Hwasung Mars Lee
> 
> Mathematical Institute, Oxford University, 24-29 St Giles', Oxford,
> OX1 3LB, United Kingdom
> 
> It is by logic that we prove, but by intuition that we discover. -
> Henri Poincaré
> 
> 
> _________________________________________________________________ 
> Share what Santa brought you https://www.mycooluncool.com 
> -------------------------------------------------------------------------
>  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...>

[Vim-latex-devel] \lv and opening problems in Mac OS

[Hwasung M. L. <hwa...@ho...>]

Hello,

With the help of some people, I managed to solve the problem I was having on Linux machines. Now, I want to ask some questions when using Mac OS.

1. When opening a file
When opening a file in Mac OS, I have to press enter after vim tells me what file it is opening. After I press enter, it finally shows the contents to me. This doesn't happen when I am using Linux, what's going wrong? I am using vim 7.1.

2. \lv
When using \lv, instead of opening the file it gives a bunch of errors. On the vim-latex documentation, it says that the system should open it automatically (I didn't customize it yet). Why isn't this working? I am using Mac OS X Tiger.

Thanks in advance,
Mars


---

Hwasung Mars Lee

Mathematical Institute,
Oxford University,
24-29 St Giles',
Oxford, OX1 3LB,
United Kingdom

It is by logic that we prove,
but by intuition that we discover.
- Henri Poincaré


_________________________________________________________________
Share what Santa brought you
https://www.mycooluncool.com

Re: [Vim-latex-devel] How to set default compiler

[Christian E. <bla...@gm...>]

* Hwasung Mars Lee on Tuesday, February 19, 2008 at 17:11:25 +0000
> I have just switched to vim, but I can't configure it to
> compile my tex files into pdf rather than dvi. My tex.vim under
> ~/.vim/ftplugin reads,
> 
> g:Tex_DefaultTargetFormat = 'pdf'

let g:Tex_DefaultTargetFormat = 'pdf'
^^^

or was that just a typo?

c
-- 
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>

[Vim-latex-devel] How to set default compiler

[Hwasung M. L. <hwa...@ho...>]

Hello,

I have just switched to vim, but I can't configure it to compile my tex files into pdf rather than dvi. My tex.vim under ~/.vim/ftplugin reads,


g:Tex_DefaultTargetFormat = 'pdf'


Why is vim-latex macros still compiling it into dvi?

Thanks in advance,
Mars

---
Hwasung Mars Lee

It is by logic that we prove,
but by intuition that we discover.
- Henri Poincaré

_________________________________________________________________
Share what Santa brought you
https://www.mycooluncool.com

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

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

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