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

[Vim-latex-devel] [PATCH] Forward (and backward) search with SumatraPDF

[Julien C. <jul...@gm...>]

Dear all

Please find enclosed a patch (.diff, additional python file, and
README) to make Forward search work with SumatraPDF for Windows.
The README also details how to set up the Backward search.
This is joint work with Manuel Pégourié-Gonnard (also on the
vim-latex-devel list).

We tried to follow the conventions from the rest of the code,
specially regarding the call to Python which is mimicked from the call
to outline.py which takes place in texviewer.vim.

Besides, the call to a Python script is required as SumatraPDF only
accepts communication from DDE.

Any feedback welcome, and please include it to the official
latex-suite repository if you find it useful !
Best,

Julien

Re: [Vim-latex-devel] RemoteOpen and acctentuated "é" mapping

[Julien C. <jul...@gm...>]

Dear all

I found my final mistake in this "RemoteOpen supresses e-accent
remapping" thing. Mea maxima culpa: I had put the "imap <buffer>
blablabla" command in my .vimrc, not in my "~/.vim/ftplugin/tex.vim"
(though the FAQ clearly says to put it there).
That was a good occasion for me to understand that the .vimrc is not
sourced when a file is opened via the clientserver way that RemoteOpen
uses (makes sense, as Vim was already started), and to discover
"hasmap".

Dumb I. Sorry for the noise on the list.

Julien


On Sun, Feb 15, 2009 at 2:24 PM, Julien Cornebise
<jul...@gm...> wrote:
> Investigating further, I think the problem may lie in lines 109--114
> of remoteOpen.vim (quoted below)
>
>        " If none of the servers have the file open, then open this file in the
>        " first server. This has the advantage if yap tries to make vim open
>        " multiple vims, then at least they will all be opened by the same gvim
>        " server.
>        call remote_send(targetServer,
>                \ "\<C-\>\<C-n>".
>                \ ":let g:Remote_Server = 1\<CR>".
>                \ ":drop ".filename."\<CR>".
>                \ ":".linenum."\<CR>zv"
>                \ )
>
> Could it be that the opening of a LaTeX file with this call differs to
> the "classical" opnening is such a way that latex-suite mappings
> overwrite the mapping
> imap <buffer> <mapleader>i <Plug>Tex_InsertItemOnThisLine
> (which I now fully understand) in my .vimrc ? Or, more precisely,
> could it be that latex-suite as remotely loaded for the new file *does
> not check* that such a mapping is already set ??
>
> Thanks for any idea !
>
> Julien
>

Re: [Vim-latex-devel] bug in launching the viewer on Mac OS X

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

This is a good fix. I recommend you resubmit it with

[PATCH]

in the subject so that someone with commit access can get into into SVN.

Locally, I've patched my Vim-LaTeX to have a "Tex_TreatMacViewerAsUNIX" 
variable that I turn on. That lets me avoid "open" entirely. This is 
convenient as it lets me do forward searching. Forward searching is 
supported in Skim via an AppleScript call (which can be put inside a 
command line script that exec's osascript).

--Ted


On 2/17/09 5:24 PM, William (B.J.) Snow Orvis wrote:
> I believe I have run into a bug in the Tex_ViewLaTeX function under Mac
> OS X. Each time Tex_ViewLaTeX() runs on a macunix system, it prepends an
> additional '-a ' to the s:viewer variable. If Tex_ViewLaTeX is called
> multiple times in a given session, (using '\lv', for example) it only
> successfully runs the viewer every other time it is called.
>
> This leads to Tex_PrintDebug() output along the lines of:
>
> comp : Tex_ViewLaTeX: execString = open -a /Applications/Skim.app thesis.pdf
> comp : Tex_ViewLaTeX: execString = open -a -a /Applications/Skim.app thesis.pdf
> comp : Tex_ViewLaTeX: execString = open -a -a -a /Applications/Skim.app thesis.pdf
>
> Attached is a patch I created as a workaround to this problem. The patch
> inserts a '-a ' in execString if s:viewer is nonempty, rather than
> modifying s:viewer each time Tex_ViewLaTeX() is called. This ensures
> that there is only ever a single '-a' in execString, if a viewer program
> is specified.
>
> I had this problem with latexSuite20060325, but it looks like it may
> still exist in the subversion trunk.
>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

   Please visit my ALS association page:
         http://web.alsa.org/goto/tedpavlic
   My family appreciates your support in the fight to defeat ALS.

[Vim-latex-devel] bug in launching the viewer on Mac OS X

[William (B.J.) S. O. <aet...@gm...>]

I believe I have run into a bug in the Tex_ViewLaTeX function under Mac
OS X. Each time Tex_ViewLaTeX() runs on a macunix system, it prepends an
additional '-a ' to the s:viewer variable. If Tex_ViewLaTeX is called
multiple times in a given session, (using '\lv', for example) it only
successfully runs the viewer every other time it is called.

This leads to Tex_PrintDebug() output along the lines of:

comp : Tex_ViewLaTeX: execString = open -a /Applications/Skim.app thesis.pdf
comp : Tex_ViewLaTeX: execString = open -a -a /Applications/Skim.app thesis.pdf
comp : Tex_ViewLaTeX: execString = open -a -a -a /Applications/Skim.app thesis.pdf

Attached is a patch I created as a workaround to this problem. The patch
inserts a '-a ' in execString if s:viewer is nonempty, rather than
modifying s:viewer each time Tex_ViewLaTeX() is called. This ensures
that there is only ever a single '-a' in execString, if a viewer program
is specified.

I had this problem with latexSuite20060325, but it looks like it may
still exist in the subversion trunk.

-- 
......................................................................
William (B.J.) Snow Orvis     PGP Fingerprint:
aet...@gm...        E6DC E687 EBB7 E99C 1BCE
http://ouroboros.homedns.org  D04F 057B 0CD0 8A49 3E98

Random link:
Electronic Frontier Foundation: http://www.eff.org

Re: [Vim-latex-devel] RemoteOpen and acctentuated "é" mapping

[Julien C. <jul...@gm...>]

Investigating further, I think the problem may lie in lines 109--114
of remoteOpen.vim (quoted below)

	" If none of the servers have the file open, then open this file in the
	" first server. This has the advantage if yap tries to make vim open
	" multiple vims, then at least they will all be opened by the same gvim
	" server.
	call remote_send(targetServer,
		\ "\<C-\>\<C-n>".
		\ ":let g:Remote_Server = 1\<CR>".
		\ ":drop ".filename."\<CR>".
		\ ":".linenum."\<CR>zv"
		\ )

Could it be that the opening of a LaTeX file with this call differs to
the "classical" opnening is such a way that latex-suite mappings
overwrite the mapping
imap <buffer> <mapleader>i <Plug>Tex_InsertItemOnThisLine
(which I now fully understand) in my .vimrc ? Or, more precisely,
could it be that latex-suite as remotely loaded for the new file *does
not check* that such a mapping is already set ??

Thanks for any idea !

Julien

On Sun, Feb 15, 2009 at 12:05 PM, Julien Cornebise
<jul...@gm...> wrote:
> Dear all,
>
> As a french user, I have redefined the "e acute" mapping in my .vimrc
> with the line :
> imap <buffer> <mapleader>i <Plug>Tex_InsertItemOnThisLine
> This is perfect, I can type "é" without any problem, fine.
>
> However, when I'm doing backward search from my viewer, which calls
> the classical
> gvim -c ":RemoteOpen +%l %f"
> then the "é" maps back to "\item" -- whereas the rest of my .vimrc
> file is taken into account.
>
> Would you please know how I can prevent RemoteOpen.vim to overwrite
> the item insert ? To be fully honest, as have already been discussed
> on this list a few days ago, I do not entirely understand the
> "<mapleader>i <Plug>" part of the above command.
>
> Thanks for any help !
>
> Julien
>

[Vim-latex-devel] RemoteOpen and acctentuated "é" mapping

[Julien C. <jul...@gm...>]

Dear all,

As a french user, I have redefined the "e acute" mapping in my .vimrc
with the line :
imap <buffer> <mapleader>i <Plug>Tex_InsertItemOnThisLine
This is perfect, I can type "é" without any problem, fine.

However, when I'm doing backward search from my viewer, which calls
the classical
gvim -c ":RemoteOpen +%l %f"
then the "é" maps back to "\item" -- whereas the rest of my .vimrc
file is taken into account.

Would you please know how I can prevent RemoteOpen.vim to overwrite
the item insert ? To be fully honest, as have already been discussed
on this list a few days ago, I do not entirely understand the
"<mapleader>i <Plug>" part of the above command.

Thanks for any help !

Julien

Re: [Vim-latex-devel] compiling error

[Julien C. <jul...@gm...>]

Glad to help :)
Julien

On Wed, Feb 11, 2009 at 4:48 PM, Julia Albath <jul...@gm...> wrote:
> That did it. there was a journalECDS.tex.latexmain hanging around my home
> folder, several levels above my current working dir. Thanks for the help.
>
> On Wed, Feb 11, 2009 at 2:52 AM, Julien Cornebise
> <jul...@gm...> wrote:
>>
>> Hi Julia
>>
>> This is a naive idea, but the first that crosses my mind : have you
>> checked for the existence of a trailing journalECDS.tex.latexmain which
>> would be situated anywhere in the parents folders of the file you're
>> currently trying to compile ? (maybe in the root of your home)
>> See
>> http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html#latex-project-example
>>
>> Best,
>>
>> Julien
>>
>> On Wed, Feb 11, 2009 at 1:01 AM, Julia Albath <jul...@gm...>
>> wrote:
>>>
>>> I hadn't thought of that, but unfortunately, I wasn't using a makefile,
>>> the file I'm currently working with is very bare bones.
>>>
>>> Any other ideas?
>>>
>>> On Tue, Feb 10, 2009 at 3:19 PM, Mirko Hessel-von Molo
>>> <mi...@ma...> wrote:
>>>>
>>>> On Tue, 10 Feb 2009, Julia Albath wrote:
>>>>
>>>>> Whenever I try to compile a document using \ll in gvim, I receive the
>>>>> following error:
>>>>>
>>>>> || I can't find file `journalECDS.tex'. journalECDS.tex
>>>>> || Emergency stop.
>>>>>
>>>>> journalECDS.tex is a document of mine, but not one I am editing at that
>>>>> point. It's not even in the same location, I haven't looked at the file
>>>>> in
>>>>> ages, yet no matter what I try to compile, I will get that error.
>>>>
>>>> Do you maybe use a makefile which somehow refers to journalECDS.tex?
>>>> I once had a similar problem where I copied and edited a makefile from
>>>> an
>>>> earlier project, but overlooked one rule -- that took me ages to figure
>>>> out...
>>>>
>>>> Mirko
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Create and Deploy Rich Internet Apps outside the browser with
>>> Adobe(R)AIR(TM)
>>> software. With Adobe AIR, Ajax developers can use existing skills and
>>> code to
>>> build responsive, highly engaging applications that combine the power of
>>> local
>>> resources and data with the reach of the web. Download the Adobe AIR SDK
>>> and
>>> Ajax docs to start building applications
>>> today-http://p.sf.net/sfu/adobe-com
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>
>>
>
>

Re: [Vim-latex-devel] compiling error

[Julia A. <jul...@gm...>]

That did it. there was a journalECDS.tex.latexmain hanging around my home
folder, several levels above my current working dir. Thanks for the help.

On Wed, Feb 11, 2009 at 2:52 AM, Julien Cornebise <
jul...@gm...> wrote:

> Hi Julia
>
> This is a naive idea, but the first that crosses my mind : have you checked
> for the existence of a trailing journalECDS.tex.latexmain which would be
> situated anywhere in the parents folders of the file you're currently trying
> to compile ? (maybe in the root of your home)
> See
> http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html#latex-project-example
>
> Best,
>
> Julien
>
> On Wed, Feb 11, 2009 at 1:01 AM, Julia Albath <jul...@gm...>wrote:
>
>> I hadn't thought of that, but unfortunately, I wasn't using a makefile,
>> the file I'm currently working with is very bare bones.
>>
>> Any other ideas?
>>
>> On Tue, Feb 10, 2009 at 3:19 PM, Mirko Hessel-von Molo <
>> mi...@ma...> wrote:
>>
>>> On Tue, 10 Feb 2009, Julia Albath wrote:
>>>
>>>  Whenever I try to compile a document using \ll in gvim, I receive the
>>>> following error:
>>>>
>>>> || I can't find file `journalECDS.tex'. journalECDS.tex
>>>> || Emergency stop.
>>>>
>>>> journalECDS.tex is a document of mine, but not one I am editing at that
>>>> point. It's not even in the same location, I haven't looked at the file
>>>> in
>>>> ages, yet no matter what I try to compile, I will get that error.
>>>>
>>>
>>> Do you maybe use a makefile which somehow refers to journalECDS.tex?
>>> I once had a similar problem where I copied and edited a makefile from an
>>> earlier project, but overlooked one rule -- that took me ages to figure
>>> out...
>>>
>>> Mirko
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Create and Deploy Rich Internet Apps outside the browser with
>> Adobe(R)AIR(TM)
>> software. With Adobe AIR, Ajax developers can use existing skills and code
>> to
>> build responsive, highly engaging applications that combine the power of
>> local
>> resources and data with the reach of the web. Download the Adobe AIR SDK
>> and
>> Ajax docs to start building applications today-
>> http://p.sf.net/sfu/adobe-com
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>>
>

[Vim-latex-devel] PDF forward search (using SyncTex), and DDE

[Julien C. <jul...@gm...>]

Hi all

I am trying to tweak vim-latex' Tex_ForwardSearchLaTeX  so that it can
forward-search with SumatraPDF. I have 2 questions :

1. do you know how to obtain the line of the next synchronization
point set by synctex ? (synctex used to be the package pdfsync, but is
now included in pdflatex using command line arguments --synctex=1)
2. do you know a way to use DDE from a VIM script ? or is there no
other way than calling an external python script ? (which I am in the
way of coding, DDE in Python is very simple) -- in which case the
feature would *require* python to be set up.
2bis. If having to call a python script, what is the best way to do it
from compiler.vim ? I assume there is some standard way to do, as
outline.py is often called -- I can have a look.

Thanks for any info !

Update for the inverse-search with SumatraPDF, also based on
synctex/pdfsync: the -inverse-search option is persistent in
SumatraPDF, so a lazy way would be to call once and for all SumatraPDF
from the commadn line with the -inverse-search rightly set, and no
need to modify g:Tex_ViewRule_pdf, then.

Julien

[Vim-latex-devel] SumatraPDF and inverse search

[Julien C. <jul...@gm...>]

Dear all

Just to help people who will be looking for the answer in the future
(as I was this morning), the way to setup the Inverse search (i.e.
from the PDF to the latex) with vim-latex is to
1. add the following line to your .vimrc, beware of the slashes

let g:Tex_ViewRule_pdf = '"c:\Program Files\SumatraPDF\SumatraPDF.exe"
-inverse-search "gvim -c \":RemoteOpen +\%l \%f\""'

2. add  \usepackage{pdfsync}  (as Ted advises on his blog when setting
up the same for simk) to the preamble of your latex document.

My next step will now be to set up the forward search by tweaking
compiler.vim for SumatraPDF as Ted did for Simk. Thanks Ted for your
blog entries which are very helpful.

For windows users latexing PDF files, SumatraPDF is very useful, as it
has an autoreload that ghostview doesn't have.

Julien

Re: [Vim-latex-devel] compiling error

[Julien C. <jul...@gm...>]

Hi Julia

This is a naive idea, but the first that crosses my mind : have you checked
for the existence of a trailing journalECDS.tex.latexmain which would be
situated anywhere in the parents folders of the file you're currently trying
to compile ? (maybe in the root of your home)
See
http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html#latex-project-example

Best,

Julien

On Wed, Feb 11, 2009 at 1:01 AM, Julia Albath <jul...@gm...>wrote:

> I hadn't thought of that, but unfortunately, I wasn't using a makefile, the
> file I'm currently working with is very bare bones.
>
> Any other ideas?
>
> On Tue, Feb 10, 2009 at 3:19 PM, Mirko Hessel-von Molo <
> mi...@ma...> wrote:
>
>> On Tue, 10 Feb 2009, Julia Albath wrote:
>>
>>  Whenever I try to compile a document using \ll in gvim, I receive the
>>> following error:
>>>
>>> || I can't find file `journalECDS.tex'. journalECDS.tex
>>> || Emergency stop.
>>>
>>> journalECDS.tex is a document of mine, but not one I am editing at that
>>> point. It's not even in the same location, I haven't looked at the file
>>> in
>>> ages, yet no matter what I try to compile, I will get that error.
>>>
>>
>> Do you maybe use a makefile which somehow refers to journalECDS.tex?
>> I once had a similar problem where I copied and edited a makefile from an
>> earlier project, but overlooked one rule -- that took me ages to figure
>> out...
>>
>> Mirko
>>
>
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code
> to
> build responsive, highly engaging applications that combine the power of
> local
> resources and data with the reach of the web. Download the Adobe AIR SDK
> and
> Ajax docs to start building applications today-
> http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

Re: [Vim-latex-devel] compiling error

[Julia A. <jul...@gm...>]

I hadn't thought of that, but unfortunately, I wasn't using a makefile, the
file I'm currently working with is very bare bones.

Any other ideas?

On Tue, Feb 10, 2009 at 3:19 PM, Mirko Hessel-von Molo <
mi...@ma...> wrote:

> On Tue, 10 Feb 2009, Julia Albath wrote:
>
>  Whenever I try to compile a document using \ll in gvim, I receive the
>> following error:
>>
>> || I can't find file `journalECDS.tex'. journalECDS.tex
>> || Emergency stop.
>>
>> journalECDS.tex is a document of mine, but not one I am editing at that
>> point. It's not even in the same location, I haven't looked at the file in
>> ages, yet no matter what I try to compile, I will get that error.
>>
>
> Do you maybe use a makefile which somehow refers to journalECDS.tex?
> I once had a similar problem where I copied and edited a makefile from an
> earlier project, but overlooked one rule -- that took me ages to figure
> out...
>
> Mirko
>

[Vim-latex-devel] compiling error

[Julia A. <jul...@gm...>]

Whenever I try to compile a document using \ll in gvim, I receive the
following error:

|| I can't find file `journalECDS.tex'. journalECDS.tex
|| Emergency stop.

journalECDS.tex is a document of mine, but not one I am editing at that
point. It's not even in the same location, I haven't looked at the file in
ages, yet no matter what I try to compile, I will get that error.

I check my installation using the items suggested in the FAQ's, here are the
details:

 :echo Tex_CompileRule_dvi
 latex -interaction=nonstopmode $* (works fine for me)

!latex -interaction=nonstopmode % (also worked and compiled the proper
document, without any reference to journalECDS.tex)

:set makeprg? gives the same output as above (which it should)

:verbose set makeprg? Last set from ~/.vim/ftplugin/latex-suite/compiler.vim

:call Tex_RunLaTeX() gives: E117: Unknown function: Tex_RunLaTeX() which
according to the FAQ indicates that I should upgrade, however checked and I
have the most current version 20060325.

i'm glad I found a way to compile using !latex -interaction=nonstopmode %
but I would greatly appreciate if someone could tell me how to fix this.

[Vim-latex-devel] Compiling on winxp execute commnads like split and type

[Milan B. <mil...@gm...>]

Dear users and devs,

using MikTeX up-to-date on WinXP OS, latex-suite SVN #1046, vim 7.2.101.

running latex 3times and bibtex after the first latex on the command line,
gives a superb result, a great dvi is created, no error message.

I cleaned the working directory, only *.tex and *.bib files left.
Opening a/any of the *.tex files by vim.
Compiling the file by "\ll"
- the command window shows "latex mainfile.tex -and-some-commands" as
expected and it runs for a while, first .log file is created.
- bibtex runs, output OK.
- many quick cmd windows flash up and disappear afterwards, but they are not
the expected second latex command.
- "set verbosity=16" gave a feeling what's happening inside: "type" and
"split" commands are executed on some *.tmp files.
But I do not understand why they are executed (they are not win32 commands,
tried to find them, failed to).

Might I miss some exe files to compile using vim-latex correctly?

Thanks for any hint or advice in advance.

Z

[Vim-latex-devel] BibTeX support (e.g.) for ConTeXt from Vim-LaTeX

[J.A.J. P. <jaj...@gm...>]

Hello again,

I would like to use some elements from Vim-LaTeX when editing a ConTeXt 
file, like for instance the marvellous BibTeX support!

Would that be possible?

Is it possible to load some stuff from the Vim-LaTeX suite
while still having ConTeXt support for highlighting and the other things 
the context.vim plugin does.

Or should I try to search out what code is responsible for instance for 
the F9 citing and try to reimplement it in context.vim?
Which would be a lot of work and requires some Vim programming skills of 
which I have none.

Is there a description of the Vim-LaTeX suite?

Like: what file does what, why that file needed, which
functions/variables are defined in it etc..
So I could get an overview of how the Vim-LaTeX suite works on a source
code level.

Thanks in advance,

Adriaan.

Re: [Vim-latex-devel] ConTeXt support and LaTeX Suite

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

> Or would it be better to recode the LaTeX suite into a ConTeXt suite?
> So that the LaTeX suite is not used at all and an other vimplugin is
> used?

Have you tried

	:set ft=context

?

Vim7 has ConTeXt support, and I *THINK* it attempts to use the first 
hundred lines of your TeX files to detect the file type (it's possible 
that it only uses those lines to find LaTeX and otherwise figures its 
plain TeX). If it detects LaTeX, Vim-LaTeX gets called. If it detects 
ConTeXt, the ConTeXt support (at least syntax highlighting) should be 
called. Alternatively, if your file starts with the line

	%&context

then I believe it will force ConTeXt detection.

The autodetection is disabled if you have

	:set g:tex_flavor='latex'

in your .vimrc. If you do have that there, try removing it. See if you 
like the results.


IF NONE OF THAT WORKS, then try adding a modeline:

	% vim: set ft=context:

to the start or end of your ConTeXt source. See

	:help modeline

for more information (modeline recognition can be disabled, and so if 
modelines aren't working for you, you should make sure they're turned 
on. See the help for more details). You can drop modelines in text files 
to set file-specific settings for Vim.

--Ted

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

   Please visit my ALS association page:
         http://web.alsa.org/goto/tedpavlic
   My family appreciates your support in the fight to defeat ALS.

[Vim-latex-devel] ConTeXt support and LaTeX Suite

[J.A.J. P. <jaj...@gm...>]

As a user of the LaTeX suite I'm switching to ConTeXt for at least some 
projects.

I always liked the LaTeX suite and some features would be usable in
ConTeXt, although a lot of commands in ConTeXt are different.
Other features of the suite would be inconvenient when using ConTeXt.

Would there be a possibility to program the suite in such a way that I
could implement (some) ConTeXt support, for instance the suite
recognizes the .tex file is a ConTeXt file and switches of some macro
and switches on some others?
 
Or would it be better to recode the LaTeX suite into a ConTeXt suite?
So that the LaTeX suite is not used at all and an other vimplugin is
used?

Thanks in advance,

Adriaan.

Re: [Vim-latex-devel] utf

[Sergius <dai...@gm...>]

while this changes english chars there may be a way to force a suite
to stop filtering cyr chars.

2009/1/24 Guido Milanese <gui...@un...>:
> On Tuesday 20 January 2009 08:01:40 Sergius wrote:
>> how to input cyrillic utf-8 characters?
> Sorry for answering late, I hope the answer may be useful anyway. It
> depends from the configuration. In my case (vim on linux Ubuntu) all
> what I need is:
> set keymap=russian-jcukenwin
>
> best regards,
> gm
> --
> Guido Milanese - Professor of Latin Language and Literature
> The Catholic University, Milan and Brescia, Italy
> http://docenti.unicatt.it/milanese_guido
> http://www.arsantiqua.org
>

Re: [Vim-latex-devel] utf

[Guido M. <gui...@un...>]

On Tuesday 20 January 2009 08:01:40 Sergius wrote:
> how to input cyrillic utf-8 characters?
Sorry for answering late, I hope the answer may be useful anyway. It 
depends from the configuration. In my case (vim on linux Ubuntu) all 
what I need is:
set keymap=russian-jcukenwin

best regards,
gm
-- 
Guido Milanese - Professor of Latin Language and Literature
The Catholic University, Milan and Brescia, Italy
http://docenti.unicatt.it/milanese_guido
http://www.arsantiqua.org

Re: [Vim-latex-devel] [PATCH] Update errorformat to support (pdf)latex -file-line-error

[Till M. <ope...@ti...>]

On Wed January 14 2009, Ted Pavlic wrote:
> I fear that Thunderbird was sending with format=flowed, and so I
> attached the below as patches.

Thanks, the patches are applied in changeset 1046.

Regards,
Till

[Vim-latex-devel] utf

[Sergius <dai...@gm...>]

how to input cyrillic utf-8 characters?

Re: [Vim-latex-devel] \cite completion doesn't work as described in help file

[Julien C. <jul...@gm...>]

I'm not sure if this can help, but did you try :
1. Installing vim in a folder without any space in it (like "c:\vim",
unlinke "c:\program files\vim")
2. Installing Python (also in a folder without any space)

This solved a problem I had with the completion of \ref (not \cite), maybe
that can help too.

Julien

On Fri, Jan 16, 2009 at 1:09 PM, Roberto Saltini <hou...@gm...> wrote:

> Hi,
> if after writing \cite{ i press <F9> I don't get the windows described
> in the help file.
> I get two windows: the first one, named Quickfix, where, for each row,
> is shown only the first row of each bibtex item; in the second window
> is shown the relative file .bib.
>
> In addition, while the cursor is in Quickfix window, I press n I get
> these error message: "E486: Expression not found: F9" and also f key
> doesn't work at all.
>
> I am using gvim 7.1 on windows xp.
>
> Thank you.
>
> --
> Saltini Roberto
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] \cite completion doesn't work as described in help file

[Roberto S. <hou...@gm...>]

Hi,
if after writing \cite{ i press <F9> I don't get the windows described
in the help file.
I get two windows: the first one, named Quickfix, where, for each row,
is shown only the first row of each bibtex item; in the second window
is shown the relative file .bib.

In addition, while the cursor is in Quickfix window, I press n I get
these error message: "E486: Expression not found: F9" and also f key
doesn't work at all.

I am using gvim 7.1 on windows xp.

Thank you.

-- 
Saltini Roberto

Re: [Vim-latex-devel] [PATCH] Update errorformat to support (pdf)latex -file-line-error

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

I fear that Thunderbird was sending with format=flowed, and so I 
attached the below as patches.

On 1/12/09 4:24 PM, Ted Pavlic wrote:
>
> The attached patches to compiler/tex.vim configure the Vim-LaTeX suite
> to parse error messages when
>
>           latex -file-line-error
>
> is used. This option tells LaTeX to produce more C-like error messages
> so that Vim doesn't have to do parentheses acrobatics to figure out the
> corresponding file. However, warnings are still in LaTeX's lisp-y
> format, and so a good latex wrapper is still warranted if you care about
> warnings.
>
> The second patch updates the tex.vim modeline to match the conventional
> Vim-LaTeX source modeline.



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

   Please visit my ALS association page:
         http://web.alsa.org/goto/tedpavlic
   My family appreciates your support in the fight to defeat ALS.

[Vim-latex-devel] [PATCH] Update errorformat to support (pdf)latex -file-line-error

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

The attached patches to compiler/tex.vim configure the Vim-LaTeX suite
to parse error messages when

         latex -file-line-error

is used. This option tells LaTeX to produce more C-like error messages
so that Vim doesn't have to do parentheses acrobatics to figure out the
corresponding file. However, warnings are still in LaTeX's lisp-y
format, and so a good latex wrapper is still warranted if you care about
warnings.

The second patch updates the tex.vim modeline to match the conventional
Vim-LaTeX source modeline.


# HG changeset patch
# User tpavlic
# Date 1231793010 18000
# Node ID 57d4972f5443bcf5b791ff02ef493fd64fd4867d
# Parent  1482232d621c1fab4ca88b2c447e3c30f5b32c0c
Added errorformat (efm) support for latex -file-line-error (which 
sanitizes error messages for Vim)

diff --git a/vimfiles/compiler/tex.vim b/vimfiles/compiler/tex.vim
--- a/vimfiles/compiler/tex.vim
+++ b/vimfiles/compiler/tex.vim
@@ -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
diff --git a/vimfiles/ftplugin/latex-suite/texrc 
b/vimfiles/ftplugin/latex-suite/texrc
--- a/vimfiles/ftplugin/latex-suite/texrc
+++ b/vimfiles/ftplugin/latex-suite/texrc
@@ -104,7 +104,8 @@
  " values, but if use some other compiler, then you will want to change 
this.
  " As CompileFlags value you'd perhaps like to use, e.g., '-src-specials',
  " but it is known that it can sometimes give different results in the 
output,
-" so use it with care.
+" so use it with care. The '-file-line-error' flag helps sanitize LaTeX 
error
+" messages for processing by Vim.
  TexLet g:Tex_CompileRule_dvi = 'latex -interaction=nonstopmode $*'
  TexLet g:Tex_EscapeChars = '{}\'

# HG changeset patch
# User tpavlic
# Date 1231793243 18000
# Node ID 2c02840c23f8ca3a29e08eea90b33df6ca1ff5ad
# Parent  57d4972f5443bcf5b791ff02ef493fd64fd4867d
Update modeline in compiler/tex.vim to match others.

diff --git a/vimfiles/compiler/tex.vim b/vimfiles/compiler/tex.vim
--- a/vimfiles/compiler/tex.vim
+++ b/vimfiles/compiler/tex.vim
@@ -291,4 +291,4 @@

  call Tex_Debug("compiler/tex.vim: sourcing this file", "comp")

-" vim: fdm=marker:commentstring=\ \"\ %s
+" vim:fdm=marker:ff=unix:noet:ts=4:sw=4



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

   Please visit my ALS association page:
         http://web.alsa.org/goto/tedpavlic
   My family appreciates your support in the fight to defeat ALS.