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

Re: [Vim-latex-devel] Problem pasting between files

[Bodo G. <ma...@bo...>]

I can confirm something like this.
Usually if I select some text anywhere (in any application), then open
gvim, open a file, I can paste the original selection right into it.
But not so with .tex-files. When those are opened, the copy-paste-buffer
is overwritten with the content of the file. So when it’s a new .tex
file a single empty line would be pasted.

Hope this helps tracking the issue.
best regards,
Bodo

Am Sat, 9 Feb 2013 17:19:48 +0100
schrieb Alessandro Pezzoni <ale...@la...>:

| 2013/2/9 David Woodfall <da...@da...>:
| > On (09/02/13 13:02), David Woodfall <da...@da...> put forth
| > the proposition:
| >>On (09/02/13 13:39), Alessandro Pezzoni
| >><ale...@la...> put forth the proposition:
| >>>> Thanks Alessandro. It's a bit strange how it works with other
| >>>> files without need to add "*, but at least I know how now.
| >>>
| >>>The first thing I can think of is that if you select text with your
| >>>mouse in X11 it usually gets copied to the clipboard right away.
| >>>Note that this works for vim (in a terminal), but not for gvim, so
| >>>one possible explanation would be if you are used to edit files
| >>>with vim, but edit tex files from gvim (which I do).
| >>
| >>No, I'm using only vim commands d and p
| >
| > Make that y and p
| 
| Ok, so if I understand you correctly, usually if you yank (y) some
| text from a file, close vim, then open it on a different file, you can
| paste (p) it back, without using the "* or "+ registers? That sounds
| odd...
| 
| Alessandro
| 
| 
| ------------------------------------------------------------------------------
| Free Next-Gen Firewall Hardware Offer
| Buy your Sophos next-gen firewall before the end March 2013 
| and get the hardware for free! Learn more.
| http://p.sf.net/sfu/sophos-d2d-feb
| _______________________________________________
| Vim-latex-devel mailing list
| Vim...@li...
| https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
| 

Re: [Vim-latex-devel] Problem pasting between files

[Alessandro P. <ale...@la...>]

2013/2/9 David Woodfall <da...@da...>:
> On (09/02/13 13:02), David Woodfall <da...@da...> put forth the proposition:
>>On (09/02/13 13:39), Alessandro Pezzoni <ale...@la...> put forth the proposition:
>>>> Thanks Alessandro. It's a bit strange how it works with other files
>>>> without need to add "*, but at least I know how now.
>>>
>>>The first thing I can think of is that if you select text with your
>>>mouse in X11 it usually gets copied to the clipboard right away. Note
>>>that this works for vim (in a terminal), but not for gvim, so one
>>>possible explanation would be if you are used to edit files with vim,
>>>but edit tex files from gvim (which I do).
>>
>>No, I'm using only vim commands d and p
>
> Make that y and p

Ok, so if I understand you correctly, usually if you yank (y) some
text from a file, close vim, then open it on a different file, you can
paste (p) it back, without using the "* or "+ registers? That sounds
odd...

Alessandro

Re: [Vim-latex-devel] Problem pasting between files

[David W. <da...@da...>]

On (09/02/13 13:02), David Woodfall <da...@da...> put forth the proposition:
>On (09/02/13 13:39), Alessandro Pezzoni <ale...@la...> put forth the proposition:
>>> Thanks Alessandro. It's a bit strange how it works with other files
>>> without need to add "*, but at least I know how now.
>>
>>The first thing I can think of is that if you select text with your
>>mouse in X11 it usually gets copied to the clipboard right away. Note
>>that this works for vim (in a terminal), but not for gvim, so one
>>possible explanation would be if you are used to edit files with vim,
>>but edit tex files from gvim (which I do).
>
>No, I'm using only vim commands d and p

Make that y and p

Re: [Vim-latex-devel] Problem pasting between files

[David W. <da...@da...>]

On (09/02/13 13:39), Alessandro Pezzoni <ale...@la...> put forth the proposition:
>> Thanks Alessandro. It's a bit strange how it works with other files
>> without need to add "*, but at least I know how now.
>
>The first thing I can think of is that if you select text with your
>mouse in X11 it usually gets copied to the clipboard right away. Note
>that this works for vim (in a terminal), but not for gvim, so one
>possible explanation would be if you are used to edit files with vim,
>but edit tex files from gvim (which I do).

No, I'm using only vim commands d and p

Re: [Vim-latex-devel] Problem pasting between files

[Alessandro P. <ale...@la...>]

> Thanks Alessandro. It's a bit strange how it works with other files
> without need to add "*, but at least I know how now.

The first thing I can think of is that if you select text with your
mouse in X11 it usually gets copied to the clipboard right away. Note
that this works for vim (in a terminal), but not for gvim, so one
possible explanation would be if you are used to edit files with vim,
but edit tex files from gvim (which I do).

Alessandro

Re: [Vim-latex-devel] Problem pasting between files

[David W. <da...@da...>]

tOn (09/02/13 11:41), Alessandro Pezzoni <ale...@la...> put forth the proposition:
>>>>On 02/09/2013 10:55 AM, David Woodfall wrote:
>>>>> When I copy lines from one tex file, open a different one and paste
>>>>> I'm not getting a proper paste. Instead it pastes what looks like an
>>>>> escape sequence ^[. On testing it does paste into a filetype other
>>>>> than tex, so the yank line is working, just not the paste.
>>>>>
>>>>> What can I do to paste properly between tex files?
>>
>> I've noticed that it works when using a split window, but not when
>> closing vim and opening the second file, if that's any clue.
>
>When you yank some text in vim, it puts it in a register which gets
>cleared when you close vim. You can do one of two things: either open
>both files in the same session of vim, e.g. with split windows or
>tags, or prepend "* to your yanking command, so that vim puts the
>yanked text in a register shared with the system clipboard. For more
>information on this, have a look look at the relevant help page [1].
>
>Alessandro
>
>[1] http://vimdoc.sourceforge.net/htmldoc/gui_x11.html#x11-selection

Thanks Alessandro. It's a bit strange how it works with other files
without need to add "*, but at least I know how now.

Re: [Vim-latex-devel] Problem pasting between files

[Alessandro P. <ale...@la...>]

>>>On 02/09/2013 10:55 AM, David Woodfall wrote:
>>>> When I copy lines from one tex file, open a different one and paste
>>>> I'm not getting a proper paste. Instead it pastes what looks like an
>>>> escape sequence ^[. On testing it does paste into a filetype other
>>>> than tex, so the yank line is working, just not the paste.
>>>>
>>>> What can I do to paste properly between tex files?
>
> I've noticed that it works when using a split window, but not when
> closing vim and opening the second file, if that's any clue.

When you yank some text in vim, it puts it in a register which gets
cleared when you close vim. You can do one of two things: either open
both files in the same session of vim, e.g. with split windows or
tags, or prepend "* to your yanking command, so that vim puts the
yanked text in a register shared with the system clipboard. For more
information on this, have a look look at the relevant help page [1].

Alessandro

[1] http://vimdoc.sourceforge.net/htmldoc/gui_x11.html#x11-selection

Re: [Vim-latex-devel] Questions about adding options of ps2pdf while Windows

[Alessandro P. <ale...@la...>]

2013/2/9 Hao Fang <all...@gm...>:
> If I use
> " :!ps2pdf -sPAPERSIZE\#letter document.ps document.pdf "
> (adding '\' before '#'), then it works.
> [...]
> However, if I set it in tex.vim, i.e.,
> let g:Tex_CompileRule_pdf = 'ps2pdf -sPAPERSIZE\#letter $*.ps $.pdf'
> It will actually run
> :!ps2pdf -sPAPERSIZE\#letter document.ps document.pdf > C:/Users/...

Dear Hao Fang,
escaping the '#' (i.e. adding '\' in front of it) should be indeed the
way to go. I don't know at which point in the code the substitutions
are made, but you could try changing the quotes with double quotes
(i.e. put " instead of '). You could have to escape some other
characters in that case, though.

If you don't need the .dvi or the .ps, you could also try to bypass
the issue entirely by compiling with pdflatex (this could possibly
require some small tweaks in your source file, though).

Alessandro

Re: [Vim-latex-devel] Problem pasting between files

[David W. <da...@da...>]

On (09/02/13 07:27), David Woodfall <da...@da...> put forth the proposition:
>On (09/02/13 12:44), Devendra Ghate <dev...@gm...> put forth the proposition:
>>Try
>>
>>:set paste
>>
>>and once done pasting,
>>
>>:set nopaste
>
>Tried that first. No luck I'm afraid.
>
>>On 02/09/2013 10:55 AM, David Woodfall wrote:
>>> When I copy lines from one tex file, open a different one and paste
>>> I'm not getting a proper paste. Instead it pastes what looks like an
>>> escape sequence ^[. On testing it does paste into a filetype other
>>> than tex, so the yank line is working, just not the paste.
>>>
>>> What can I do to paste properly between tex files?

I've noticed that it works when using a split window, but not when
closing vim and opening the second file, if that's any clue.

Re: [Vim-latex-devel] Problem pasting between files

[David W. <da...@da...>]

On (09/02/13 12:44), Devendra Ghate <dev...@gm...> put forth the proposition:
>Try
>
>:set paste
>
>and once done pasting,
>
>:set nopaste

Tried that first. No luck I'm afraid.

>On 02/09/2013 10:55 AM, David Woodfall wrote:
>> When I copy lines from one tex file, open a different one and paste
>> I'm not getting a proper paste. Instead it pastes what looks like an
>> escape sequence ^[. On testing it does paste into a filetype other
>> than tex, so the yank line is working, just not the paste.
>>
>> What can I do to paste properly between tex files?

Re: [Vim-latex-devel] Problem pasting between files

[Devendra G. <dev...@gm...>]

Try

:set paste

and once done pasting,

:set nopaste

Devendra


On 02/09/2013 10:55 AM, David Woodfall wrote:
> When I copy lines from one tex file, open a different one and paste
> I'm not getting a proper paste. Instead it pastes what looks like an
> escape sequence ^[. On testing it does paste into a filetype other
> than tex, so the yank line is working, just not the paste.
>
> What can I do to paste properly between tex files?
>

[Vim-latex-devel] Problem pasting between files

[David W. <da...@da...>]

When I copy lines from one tex file, open a different one and paste
I'm not getting a proper paste. Instead it pastes what looks like an
escape sequence ^[. On testing it does paste into a filetype other
than tex, so the yank line is working, just not the paste.

What can I do to paste properly between tex files?

-- 
When all you have is a Swiss Army Knife, every problem looks like email.
    -- Peter da Silva

[Vim-latex-devel] Questions about adding options of ps2pdf while Windows

[Hao F. <all...@gm...>]

Dear Vim Latex-Suite developers:

Currently I'm using the vim-latex-1.8.23.-20130116.788 version and MikTex.
I want to set the paper size of the command ps2pdf, e.g.
(in tex.vim)
let g:Tex_CompileRule_pdf = 'ps2pdf -sPAPERSIZE#letter $*.ps $.pdf'

The "#" instead of "=" has to be used under Windows MikTex,
which leads to the problem.

It seems that the Latex-Suite call "make! document" to compile the PDF file.
However, # is referred to "alternative file name".
So if I compile the ps file, I would get the error
"E194: No alternate file name to substitute for '#'".

The same error message shown up when I use
" :!ps2pdf -sPAPERSIZE#letter document.ps document.pdf "
in vim.

If I use
" :!ps2pdf -sPAPERSIZE\#letter document.ps document.pdf "
(adding '\' before '#'), then it works.
The message shown at the bottom is
:!ps2pdf -sPAPERSIZE#letter document.ps document.pdf
PRESS ENTER or type command to continue

The '\' is automatically removed in this case.

However, if I set it in tex.vim, i.e.,
let g:Tex_CompileRule_pdf = 'ps2pdf -sPAPERSIZE\#letter $*.ps $.pdf'
It will actually run
:!ps2pdf -sPAPERSIZE\#letter document.ps document.pdf > C:/Users/...
(I see this message by running
make! document
after I compile the document)
In this case, '\' is not removed.
Thus, the command does not run correctly.

Currently, I can set the paper type in dvi2ps as
dvi2ps -t letter
and do not use any options in ps2pdf, which would avoid the problem.

But I still want to know is there any other solution to
directly solve the problem about "#"?

Thanks a lot for your kindly help.


Best Regards,
Hao Fang

[Vim-latex-devel] (no subject)

[ahmet n. <ahm...@ya...>]

http://www.killerrents.com/wp-content/plugins/yourpoint.php


-------------------
ahmet nurlu

Re: [Vim-latex-devel] Cannot compile tex file on Windows ( it's OK on Mac)

[YANG L. <lin...@gm...>]

I found one workaround for this
1. Using the TTarget command first to set the pdf format as the compile
target format
2. compile
3. though "E492: Not a editor command: ^ITCLevel 1000" and "E492: Not a
editor command: TCLevel 7" will be prompted, at least the file could be
compiled.
regards

On Tue, Jan 29, 2013 at 5:53 PM, YANG LINCHANG <lin...@gm...>wrote:

> Hi there,
> first, thank you for developing such a good plugin for tex users. It
> worked fine on both of my Windows desktop and Macbook Pro.
> However, I encountered the problem after one update of vim-latex that it
> cannot work on Windows.
> When I press /ll to compile, vim will throw out a series of error messages:
>
> Error detected while processing function Tex_RunLaTeX:
> line 7:
> E121: Undefined variable: s:target
> E15: Invalid expression: s:target
> line 10:
> E121: Undefined variable: s:target
> E116: Invalid arguments for function Tex_Debug
> line 12:
> E121: Undefined variable: s:target
> E116: Invalid arguments for function
> Tex_GetVarValue('Tex_FormatDependency_'.s:t
> arget) != ''
> E15: Invalid expression: Tex_GetVarValue('Tex_FormatDependency_'.s:target)
> != ''
>
> line 21:
> E121: Undefined variable: dependency
> E116: Invalid arguments for function Tex_Debug
> line 25:
> E121: Undefined variable: dependency
> E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) != ''
> E15: Invalid expression: Tex_Strntok(dependency, ',', i) != ''
> line 51:
> E121: Undefined variable: initTarget
> E15: Invalid expression: initTarget
>
> And also the similar error messages of \lv and \ls.
>
> but I can still compile .tex files on Mac. It seems that the malfunction
> is related to the target format and I set the right
> "g:Tex_DefaultTargetFormat" in my .vimrc and it used to work.
> please advise me some possible solutions.
> regards
>
>

[Vim-latex-devel] Cannot compile tex file on Windows ( it's OK on Mac)

[YANG L. <lin...@gm...>]

Hi there,
first, thank you for developing such a good plugin for tex users. It worked
fine on both of my Windows desktop and Macbook Pro.
However, I encountered the problem after one update of vim-latex that it
cannot work on Windows.
When I press /ll to compile, vim will throw out a series of error messages:

Error detected while processing function Tex_RunLaTeX:
line 7:
E121: Undefined variable: s:target
E15: Invalid expression: s:target
line 10:
E121: Undefined variable: s:target
E116: Invalid arguments for function Tex_Debug
line 12:
E121: Undefined variable: s:target
E116: Invalid arguments for function
Tex_GetVarValue('Tex_FormatDependency_'.s:t
arget) != ''
E15: Invalid expression: Tex_GetVarValue('Tex_FormatDependency_'.s:target)
!= ''

line 21:
E121: Undefined variable: dependency
E116: Invalid arguments for function Tex_Debug
line 25:
E121: Undefined variable: dependency
E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) != ''
E15: Invalid expression: Tex_Strntok(dependency, ',', i) != ''
line 51:
E121: Undefined variable: initTarget
E15: Invalid expression: initTarget

And also the similar error messages of \lv and \ls.

but I can still compile .tex files on Mac. It seems that the malfunction is
related to the target format and I set the right
"g:Tex_DefaultTargetFormat" in my .vimrc and it used to work.
please advise me some possible solutions.
regards

Re: [Vim-latex-devel] latexsuite ignores settings of Tex_IgnoreWarnings

[Ingo F. <ma...@in...>]

Thanks Ted and Alessandro,

Your comments have been very helpful. I had a look at rubber and it
seems to be a very interesting tool. The debian package didn't run out
of the box, though and I am under a bit of time pressure. So vimlatex is
doing the job now. It works great. Thanks for the hint, Ted.

Best,

Ingo

On Mon, Jan 28, 2013 at 12:02:53PM +0100, Alessandro Pezzoni wrote:
> >         This issue has been discussed ad nauseum on this mailing list in the
> > past, and several solutions have been suggested. rubber is one of them,
> > but there are other ways to mitigate these problems.
> >
> >         Here is an archive of solutions from 2008:
> >
> > http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
> >
> > It includes
> >
> > * rubber
> >
> > * adjusting your latex compile rule to use "-file-line-error-style"
> > (support for this EFM has already been added to Vim-LaTeX, and so that
> > step can be skipped)
> >
> > * a script like "vimlatex" that wraps latex and attempts to sanitize the
> > multi-line error messages into a form that Vim is happy with.
> >
> > You can actually combine the second and third bullet.
> >
> >         A downside of -file-line-error-style (which is just -file-line-error in
> > newest versions of latex) is that it doesn't help with warnings. Rubber
> > also doesn't help with all warnings. So if you really care about
> > catching warnings, your mileage may vary.
> 
> It probably doesn't fit in the manual, but could we at least add this
> piece of information to the FAQ? This seems to be a fairly common
> issue.
> 
> Alessandro
> 

-- 
Ingo Fründ, Dr. rer. nat.
Elder Lab, Center for Vision Research
York University, Toronto
www.ingofruend.net

Re: [Vim-latex-devel] Forward search in windows with vim and sumatrapdf?

[Jorge R. <sk...@gm...>]

If you are using summatra it now has options
*
*
*-reuse-instance*
-forward-search

that should make it really easy to do forward and inverse search with it.

Best Regards,
Jorge


On Mon, Jan 28, 2013 at 12:24 PM, Winfried Moser
<win...@gm...>wrote:

> Julien Cornebise <julien.cornebise <at> gmail.com> writes:
>
> >
> > Hi Jorge
> >
> > As the co-author of the patch a while ago, I unfortunately can tell
> > you that, if there were a way in vim-latex already, Manuel and I
> > wouldn't have bothered writing it
> >
> > The patch is very short, only adding an extra case-check to allow for
> > sumatrapdf along YAP and the other viewers
> > However, it is 3 years old, so I don't know if it's still working --
> > and I've stopped using vim-latex (let alone windows) a while ago.
> > Since vim-latex is entirely scripted, backing up vimlatex, applying
> > the patch, trying it and reverting if needs be is very easy -- nothing
> > to recompile or reinstall anywhere, just use your local vim folder, so
> > there's really nothing to be afraid of: just make a copy of your vim
> > folder before patching.
> >
> > All the best,
> >
> > Julien
> >
> > On Sun, May 27, 2012 at 12:36 AM, jorge rodrigues <skeept <at> gmail.com
> >
> wrote:
> > > Hi
> > >
> > > I saw some recent messages about setting up forward search with okular
> > > for linux.
> > > I am using vim-latex in windows using sumatra pdf as the viewer.
> > > I can do inverse search (that is I click the pdf and it opens vim in
> > > the location),
> > > but I don't know how to setup forward search.
> > >
> > > Using google I found the page
> > >
> http://william.famille-blum.org/blog/static.php?page=static081010-000413
> > >
> > > that suggests using a patch against vim-latex.
> > >
> > > I don't fell comfortable using patches, so I would like to know if it
> > > this is already in vim-latex
> > > or if there exits a way of doing this in vim-latex without using the
> > > mentioned patch.
> > >
> > > thanks!
> > >
> > >
> ----------------------------------------------------------------------------
> --
> > > Live Security Virtual Conference
> > > Exclusive live event will cover all the ways today's security and
> > > threat landscape has changed and how IT managers can respond.
> Discussions
> > > will include endpoint security, mobile security and the latest in
> malware
> > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > > _______________________________________________
> > > Vim-latex-devel mailing list
> > > Vim-latex-devel <at> lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >
>
>
> Hi Julien,
>
> i am encountering the same Problem als Jorge, wheras: I tried to use your
> patch,
> as mentioned in your Readme.file.
>
> I get the following message:
> _____________________________________________________________
>
> Assertion failed. hunk, file .\src\patch\2.5.9\patch-2.5.9-src\patch.c
> line 354
>
> This application has requested the Runtime to terminate it in an unusual
> way.
> Please contact the application's support team for more information.
> _____________________________________________________________
>
> I tried the patch in Windows, and in Cygwin and get the same message.
>
> I would appreciate it very much, if you could help me!
>
> Thanks in advance
>
> Winfried
>
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnnow-d2d
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] Vim-Latex Crash on WinXP machines

[J S <drs...@go...>]

Hi there,

GVim and Vim just crash on WinXP as soon as there is a \begin{} statement
in a .tex file.

Since nobody answered my initial mail, maybe someone could least tell me
whether the issue is known and unresolvable or whether there is a fix for
it?

Thanks,
John

-- 
http://dynamic.xkcd.com/random/comic/

Re: [Vim-latex-devel] Forward search in windows with vim and sumatrapdf?

[Winfried M. <win...@gm...>]

Julien Cornebise <julien.cornebise <at> gmail.com> writes:

> 
> Hi Jorge
> 
> As the co-author of the patch a while ago, I unfortunately can tell
> you that, if there were a way in vim-latex already, Manuel and I
> wouldn't have bothered writing it 
> 
> The patch is very short, only adding an extra case-check to allow for
> sumatrapdf along YAP and the other viewers
> However, it is 3 years old, so I don't know if it's still working --
> and I've stopped using vim-latex (let alone windows) a while ago.
> Since vim-latex is entirely scripted, backing up vimlatex, applying
> the patch, trying it and reverting if needs be is very easy -- nothing
> to recompile or reinstall anywhere, just use your local vim folder, so
> there's really nothing to be afraid of: just make a copy of your vim
> folder before patching.
> 
> All the best,
> 
> Julien
> 
> On Sun, May 27, 2012 at 12:36 AM, jorge rodrigues <skeept <at> gmail.com> 
wrote:
> > Hi
> >
> > I saw some recent messages about setting up forward search with okular
> > for linux.
> > I am using vim-latex in windows using sumatra pdf as the viewer.
> > I can do inverse search (that is I click the pdf and it opens vim in
> > the location),
> > but I don't know how to setup forward search.
> >
> > Using google I found the page
> > http://william.famille-blum.org/blog/static.php?page=static081010-000413
> >
> > that suggests using a patch against vim-latex.
> >
> > I don't fell comfortable using patches, so I would like to know if it
> > this is already in vim-latex
> > or if there exits a way of doing this in vim-latex without using the
> > mentioned patch.
> >
> > thanks!
> >
> > ----------------------------------------------------------------------------
--
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim-latex-devel <at> lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> 


Hi Julien,

i am encountering the same Problem als Jorge, wheras: I tried to use your patch, 
as mentioned in your Readme.file. 

I get the following message:
_____________________________________________________________

Assertion failed. hunk, file .\src\patch\2.5.9\patch-2.5.9-src\patch.c line 354

This application has requested the Runtime to terminate it in an unusual way. 
Please contact the application's support team for more information.
_____________________________________________________________

I tried the patch in Windows, and in Cygwin and get the same message.

I would appreciate it very much, if you could help me!

Thanks in advance

Winfried

Re: [Vim-latex-devel] latexsuite ignores settings of Tex_IgnoreWarnings

[Alessandro P. <ale...@la...>]

>         This issue has been discussed ad nauseum on this mailing list in the
> past, and several solutions have been suggested. rubber is one of them,
> but there are other ways to mitigate these problems.
>
>         Here is an archive of solutions from 2008:
>
> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html
>
> It includes
>
> * rubber
>
> * adjusting your latex compile rule to use "-file-line-error-style"
> (support for this EFM has already been added to Vim-LaTeX, and so that
> step can be skipped)
>
> * a script like "vimlatex" that wraps latex and attempts to sanitize the
> multi-line error messages into a form that Vim is happy with.
>
> You can actually combine the second and third bullet.
>
>         A downside of -file-line-error-style (which is just -file-line-error in
> newest versions of latex) is that it doesn't help with warnings. Rubber
> also doesn't help with all warnings. So if you really care about
> catching warnings, your mileage may vary.

It probably doesn't fit in the manual, but could we at least add this
piece of information to the FAQ? This seems to be a fairly common
issue.

Alessandro

Re: [Vim-latex-devel] latexsuite ignores settings of Tex_IgnoreWarnings

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

Alessandro/Ingo --

> Dear Ingo,
> as I recently wrote on this mailing list [1] vim's quickfix doesn't
> really like latex's multi-linear error messages.

	This issue has been discussed ad nauseum on this mailing list in the
past, and several solutions have been suggested. rubber is one of them,
but there are other ways to mitigate these problems.

	Here is an archive of solutions from 2008:

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

It includes

* rubber

* adjusting your latex compile rule to use "-file-line-error-style"
(support for this EFM has already been added to Vim-LaTeX, and so that
step can be skipped)

* a script like "vimlatex" that wraps latex and attempts to sanitize the
multi-line error messages into a form that Vim is happy with.

You can actually combine the second and third bullet.

	A downside of -file-line-error-style (which is just -file-line-error in
newest versions of latex) is that it doesn't help with warnings. Rubber
also doesn't help with all warnings. So if you really care about
catching warnings, your mileage may vary.

	--Ted

P.S.

	I'm mulling over making "-file-line-error-style" the default compile
rule in Vim-LaTeX now that most distributions should support it.

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

Re: [Vim-latex-devel] latexsuite ignores settings of Tex_IgnoreWarnings

[Alessandro P. <ale...@la...>]

> Any suggestions what else I could try to see only those warnings I want
> to see?

Dear Ingo,
as I recently wrote on this mailing list [1] vim's quickfix doesn't
really like latex's multi-linear error messages.
Therefore, you could start trying to use a latex wrapper like 'rubber'
[2], which is able to sanitize latex's error and warning messages.
This should at least prevent vim from switching to the wrong file on
some compilation errors.

For example, I have the following lines in an ftplugin,
~/.vim/ftplugin/tex.vim , which you could put in your .vimrc, if you
prefer:

let g:Tex_DefaultTargetFormat = "pdf"
let g:Tex_CompileRule_pdf = "rubber -s --pdf $*"

Hope this helps,
Alessandro

[1] http://sourceforge.net/mailarchive/message.php?msg_id=30365813
[2] https://launchpad.net/rubber/

[Vim-latex-devel] latexsuite ignores settings of Tex_IgnoreWarnings

[Ingo F. <ma...@in...>]

Dear latex-suite developers and users,

I have been using latex-suite for a relatively long time now and it
generally served me very well. With one exception, though: I have never
really managed to get the compilation to work. That is, I always had to
switch back to the terminal and run

pdflatex nameofytexfile && fg

This works but is not convenient. I finally managed to get rid of the
'Undefined variable: s:target' type of warnings by adding a line to
explicitely reset the target format when opening a tex file:

autocmd FileType tex call Tex_SetTeXCompilerTarget('Compile','pdf')

This seems to do the job, although it doesn't feel like it is supposed
to work like this.

Another an much more annoying point is that I always get stuck in a
quickfix buffer. This is exactly where I would like to go for errors.
But not for every "Overfull \hbox"-Warning. As far as I understand from
the documentation, the variables Tex_IgnoreLevel and Tex_IgnoredWarnings
should cover this issue. Neither leaving them at their default values,
nor setting them explicitely results in any change in behavior. Yet,
explicitely echoing the values of the respective variables shows that
they have values that (in my understanding) should suppress "Overfull
\hbox"-Warnings:

:echo Tex_IgnoreLevel
7

:echo Tex_IgnoredWarnings
Underfull
Overfull
specifier changed to
You have requested
Missing number, treated as zero.
There were undefined references
Citation %.%# undefined

Any suggestions what else I could try to see only those warnings I want
to see?

Thank you very much in advance,

Ingo

Re: [Vim-latex-devel] show warnings after compiling

[Andreas G. <and...@tu...>]

Hi again,

I edited .vim/compiler/tex.vim where I added patterns for "Package ... 
Warning"-like warnings. Hence, I extended the recognised error format

setlocal efm+=%+WPackage\ %.%#Warning:\ %.%#line\ %l%.%#
setlocal efm+=%+WPackage\ %.%#Warning:\ %m

This does the job. Now undefined citation warnings from natbib are shown.

But is there a way to extend the error format by changing a local 
variable in my .vimrc instead of hacking the tex.vim file?

Best

Andreas


On 01/21/2013 10:06 AM, Andreas Groh wrote:
> Hello,
>
> I figured out that the missing of the undefined citation warnings
> depends on my used bibliography package. I use the package natbib which
> produces a warning starting with "Package natbib Warning: Citation ...
> on page ... undefined". This warning is not shown by the latex-suite. If
> I disable natbib the warning looks like "Latex Warning: Citation ...."
> and this warning is recognised an display by the latex-suite.
>
> Is there a way the make the latex-suite sensitive for these kind of
> warnings (e.g. editing .vim/compiler/tex.vim)?
>
> Cheers
>
> Andreas
>
> On 01/17/2013 05:59 PM, Andreas Groh wrote:
>> Hello list,
>>
>> I am new to the vim latex-suite. I set everything up and it works fine
>> so far. But I can not figure out how to show latex warning after
>> compiling the document using \ll. If there are errors they are shown in
>> thw "Quickfix list" with a preview window below. But in the case of
>> warnings (e.g. undefined references) I end up in the normal vim window
>> without having the warnings shown. I set "TCLevel strict" which sets
>> Tex_IgnoreLevel to 0, but it doesn't change anything.
>>
>> Any ideas what I am doing wrong? Or is it the normal way that warnings
>> are not shown? Any help is appreciated.
>>
>> Thanks and best regards.
>>
>> Andreas
>>
>

-- 
------------------------------------------------------------------------
Andreas Groh                       phone : +49-351-463.34974
Institut fuer Planetare Geodaesie  fax   : +49-351-463.37063
Technische Universitaet Dresden    email : and...@tu...
D-01062 Dresden, Germany           web   : tpg.geo.tu-dresden.de
------------------------------------------------------------------------