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

Re: [Vim-latex-devel] strange error

[Alan S. <ala...@po...>]

* Mikolaj Machowski (mi...@wp...) wrote:
> Dnia Monday 27 of October 2003 16:03, Alan Schmitt napisa?:
> > Hi,
> >
> > (I'm using the current version from cvs).
> >
> > When I compile some tex code, with some warning, I get as a message:
> >
> > not finding error pattern anywhere in quickfix window :
> > /lem:algo_atomic
> >
> > Then hitting enter I get:
> >
> > sync.tex|| LaTeX Warning: Reference `lem:algo_atomic' on page \thepage=
=20
> > undefined on input
> >
> > in my error list, with the cursor correctly positionned.
> >
> > If I have 2 vertical windows when compiling, I get (the rightmost one
> > being local.sty):
> >
> > not finding error pattern anywhere in quickfix window :
> > not finding error pattern anywhere in quickfix window :local.sty
> >
> > and once again the cursor correctly positioned with the correct warning.
> >
> Yes it is strange. LS relies on simple window layout and with more
> sophisticated layout it can broke. Does it happen if you have only one
> wndow open?

I'll try and let you know. I know that it does not happen all the time
even with a multi-window layout.

Alan Schmitt

--=20
The hacker: someone who figured things out and made something cool happen.

Re: [Vim-latex-devel] strange error

[Mikolaj M. <mi...@wp...>]

Dnia Monday 27 of October 2003 16:03, Alan Schmitt napisał:
> Hi,
>
> (I'm using the current version from cvs).
>
> When I compile some tex code, with some warning, I get as a message:
>
> not finding error pattern anywhere in quickfix window :
> /lem:algo_atomic
>
> Then hitting enter I get:
>
> sync.tex|| LaTeX Warning: Reference `lem:algo_atomic' on page \thepage 
> undefined on input
>
> in my error list, with the cursor correctly positionned.
>
> If I have 2 vertical windows when compiling, I get (the rightmost one
> being local.sty):
>
> not finding error pattern anywhere in quickfix window :
> not finding error pattern anywhere in quickfix window :local.sty
>
> and once again the cursor correctly positioned with the correct warning.
>
Yes it is strange. LS relies on simple window layout and with more
sophisticated layout it can broke. Does it happen if you have only one
wndow open?

m.

Re: [Vim-latex-devel] gvim viewer problem

[Mikolaj M. <mi...@wp...>]

Dnia Friday 31 of October 2003 12:14, Ulrich Hoppe napisał:
> I am new to linux, but used vim on windows before.
> Using gvim together with latex-suite (last development version)
> I encountered a problem: I was not able to launch a viewer,
> neither for pdf nor for ps or dvi.  After editing the texrc file
> I noticed that the trouble was caused by the subsequent ampersand '&'
> symbols in the exec commands in  function ViewLaTeX() in
> ftplugin/compiler.vim.
> They work fine for vim but do not work with gvim.
> Removing the '&' s made the \lv command work under gvim.
>
> Do you have any solution of this problem?
>
Cannot confirm that. Everything works for me - both in vim and gvim.[1]

[1] OK actually not, I have something broke with font configuration
and xdvi segv'ed but kdvi (dvi), xpdf (pdf), ghostview (ps) works as
expected.

m.

[Vim-latex-devel] gvim viewer problem

[Ulrich H. <ulr...@ru...>]

Hi there!

First of all, thanks a lot for this wonderful suite.

I am new to linux, but used vim on windows before.
Using gvim together with latex-suite (last development version)
I encountered a problem: I was not able to launch a viewer,
neither for pdf nor for ps or dvi.  After editing the texrc file
I noticed that the trouble was caused by the subsequent ampersand '&'
symbols in the exec commands in  function ViewLaTeX() in 
ftplugin/compiler.vim.
They work fine for vim but do not work with gvim.
Removing the '&' s made the \lv command work under gvim. 

Do you have any solution of this problem?

Best regards
Ulrich Hoppe

----
Ulrich Hoppe
University of Bochum
Germany

Re: [Vim-latex-devel] [ vim-latex-Bugs-822510 ] texrc doc inconsistency

[Mikolaj M. <mi...@wp...>]

Dnia Monday 13 of October 2003 05:03, SourceForge.net napisał:
>
> Initial Comment:
> two different files say two totally different things
> about customizing vim-latex settings. The sample texrc
> included is correct, the instructions included with
> latex-suite.txt are not. The instructions in
> latex-suite.txt should be corrected.
>

Corrected.

m.

Re: [Vim-latex-devel] [ vim-latex-Bugs-831467 ] A bug?

[Mikolaj M. <mi...@wp...>]

Dnia Tuesday 28 of October 2003 00:24, SourceForge.net napisał:
> Summary: A bug?
Unfortunately
>
> Initial Comment:
> I just noticed a possible bug introduced in the 20031022
> release: in the 'Templates' menu the first file in the
> templates
> directory is displayed with its full pathname and cannot
> be loaded.
>
> The problem did not exist in the 20030913 release.

Fixed in CVS.

m.

[Vim-latex-devel] [ vim-latex-Bugs-831467 ] A bug?

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

Bugs item #831467, was opened at 2003-10-28 00:24
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=831467&group_id=52322

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Lin-bo Zhang (zlb)
Assigned to: Nobody/Anonymous (nobody)
Summary: A bug?

Initial Comment:
I just noticed a possible bug introduced in the 20031022
release: in the 'Templates' menu the first file in the
templates
directory is displayed with its full pathname and cannot
be loaded.

The problem did not exist in the 20030913 release.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=831467&group_id=52322

[Vim-latex-devel] strange error

[Alan S. <ala...@po...>]

Hi,

(I'm using the current version from cvs).

When I compile some tex code, with some warning, I get as a message:

not finding error pattern anywhere in quickfix window :
/lem:algo_atomic

Then hitting enter I get:

sync.tex|| LaTeX Warning: Reference `lem:algo_atomic' on page \thepage  und=
efined on input

in my error list, with the cursor correctly positionned.

If I have 2 vertical windows when compiling, I get (the rightmost one
being local.sty):

not finding error pattern anywhere in quickfix window :
not finding error pattern anywhere in quickfix window :local.sty

and once again the cursor correctly positioned with the correct warning.

Alan Schmitt

--=20
The hacker: someone who figured things out and made something cool happen.

[Vim-latex-devel] folding \part

[Zhang Lin-bo <zl...@ls...>]

It is nice that the newest dated version (20031022)
folds the abstract environment. Please also consider
to process the \part command when doing folding
- it is annoying to have it hidden behind \chapter,
\section, etc.

Best,
LB

--

[Vim-latex-devel] folder problem for figure* envioronment

[Gang L. <li...@st...>]

Dear vim-latex developers,

I found that the folding behavior of environment "figure*" is a
bit peculiar: seems the ending block is not set correctly;
therefore it always folds till the end of my tex file...

I tested it on my debian box and on our department's unix
machine, and the results are the same. Hope you may look into
this problem, thanks!

Gang

Re: [Vim-latex-devel] buggish: vim-latex and multibyte character input

[Mikolaj M. <mi...@wp...>]

Dnia Wednesday 15 of October 2003 03:04, Srinath Avadhanula napisał:
> something else and we need to debug further. If the problem appears (i.e
> composition does not happen), then the problem is with VIM itself and
> not with latex-suite and you will have to submit a bug-report to
> vi...@vi... or vi...@vi......
>
For reporting bugs bu...@vi... is better - faster.

m.

Re: [Vim-latex-devel] gentoo ebuild for vim latexsuite

[Srinath A. <sr...@fa...>]

Hi Bj=F6rn,

Thanks for doing this!

On Sun, 12 Oct 2003, [ISO-8859-1] Bj=F6rn Michaelsen wrote:
> portage (the gentoo package system yet.) It makes installing
> vim-latexsuite as simple as typing
> emerge vim-latexsuite
>

Srinath

Re: [Vim-latex-devel] buggish: vim-latex and multibyte character input

[Srinath A. <sr...@fa...>]

Hi Kihwang,

On Tue, 14 Oct 2003, Kihwang Lee wrote:

> I use Linux (tailored RedHat 7.1), gvim (6.1.165) and a XIM server
> called Ami for Korean input.  The thing is that when I use vim-latex
> with Ami, I can't input Korean characters (euc-kr) properly. It is
> hard to describe. Korean and many other scripts belong to so-called
> composite characters: you have to input several (more than 2) key
> strokes to make a meaningful unit (sort of a character, but not
> necessarily a word). I don't know about

I am assuming that the problem you are having is that in the presence of
latex-suite, you are unable to compose characters using multiple
letters. Is that right?

I am not really sure what could be going on. The way latex-suite
accomplishes most of its mappings is to map lots of characters (actually
it maps every printable characters i.e with ascii code <= 127). If for
example, after opening a tex file (so latex-suite is activated) you do:

	:imap a

you should see something like:

i  a           * <C-R>=<SNR>11_LookupCharacter("a")<CR>

The s:LookupCharacter() function resides in imaps.vim. In the normal
course of events it should just return the string 'a' when you type a. I
have a feeling that the problem is being caused by this intermediate
mapping...

Just to pinpoint the problem, do the following.

Suppose you use the sequence of characters 'ka' to type a composite
character. In the normal course of events, you would be able to open up
a non-tex file (so latex-suite is not activated) and type 'ka' get a
single composite character, right?

Now in that non-tex file (so latex-suite is not triggered), issue the
following commands:

inoremap k k
inoremap a a

Then type ka. Does the composition occur? If so, then the problem is
something else and we need to debug further. If the problem appears (i.e
composition does not happen), then the problem is with VIM itself and
not with latex-suite and you will have to submit a bug-report to
vi...@vi... or vi...@vi......

Srinath

[Vim-latex-devel] gentoo ebuild for vim latexsuite

[M. <P1...@pu...>]

The gentoo linux distro (www.gentoo.org) uses ebuilds as a equivalent of rpm. I generated one for the vim latexsuite, which is not in portage (the gentoo package system yet.) It makes installing vim-latexsuite as simple as typing
emerge vim-latexsuite

Greetz,
-- 
Björn Michaelsen
pub  1024D/C9E5A256 2003-01-21 Björn Michaelsen <bmi...@gm...>
   Key fingerprint = D649 8C78 1CB1 23CF 5CCF  CA1A C1B5 BBEC C9E5 A256

[Vim-latex-devel] buggish: vim-latex and multibyte character input

[Kihwang L. <k....@ed...>]

Hi!

I have downloaded the vim-latex yesterday and installed it.
What a piece of work!!!

I am reporting a buggish behaviour of vim-latex I have found.
I am a Korean, and naturally I frequently use LaTeX to produce Korean
documents.

I use Linux (tailored RedHat 7.1), gvim (6.1.165) and a XIM server called Ami for Korean input.
The thing is that when I use vim-latex with Ami, I can't input Korean
characters (euc-kr) properly. It is hard to describe. Korean and many other scripts belong to so-called composite characters: you have to input several (more than 2) key strokes to make a meaningful unit (sort of a character, but not necessarily a word). I don't know about the internals of vim-latex. My guess is that vim-latex stores the key strokes in a buffer and checks them and returns them, and it is intervening the character composition process of a XIM. 

Can you help me?

Many thanks in advance.

Kihwang



-- 
Kihwang Lee
PhD Student
Institute for Communicating and Collaborative Systems (ICCS)
School of Informatics, University of Edinburgh
2 Buccleuch Place, Edinburgh EH8 9LW, United Kingdom
Tel: +44-131-650-4418
Fax: +44-131-650-6626
Email: k....@ed...
WWW: http://www.iccs.informatics.ed.ac.uk/~leekh

[Vim-latex-devel] [ vim-latex-Bugs-822510 ] texrc doc inconsistency

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

Bugs item #822510, was opened at 2003-10-13 05:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=822510&group_id=52322

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ari Pollak (sourceo)
Assigned to: Nobody/Anonymous (nobody)
Summary: texrc doc inconsistency

Initial Comment:
two different files say two totally different things
about customizing vim-latex settings. The sample texrc
included is correct, the instructions included with
latex-suite.txt are not. The instructions in
latex-suite.txt should be corrected.

~/.vim/ftplugin/latex-suite/texrc says:
"        NOTE: Do NOT be edit this file directly:
"              this file will be over-written each time
you install a new copy
"              of latex-suite.
"
"              You can do one of the following:
"              1. Copy this file into
$VIMFILES/ftplugin/tex/texrc
"                 and edit the values in that file.
"                 $VIMFILES is ~/.vim for UNIX systems
and ~/vimfiles for
"                 WINDOWS systems.
"
"              2. Just set values of each setting
individually in your
"                 $VIMFILES/ftplugin/tex.vim file. (See
above for what
"                 $VIMFILES is). You will need to use
:let instead of :TexLet
"                 in this case.


latex-suite.txt says:
Customizing Latex-Suite is done by defining certain
global variables in
$VIM/ftplugin/tex/texrc.vim, where $VIM corresponds to
~/.vim for *nix machines
and ~/vimfiles for windows machines. This file is not
part of the Latex-Suite
distribution. You will need to create this file if you
need to change any
default settinngs. Since this file is not included as
part of the Latex-Suite
distribution, it will not be over-written in subsequent
updates.

NOTE: It is also possible to define any customization
in the
      $VIM/ftplugin/tex.vim file, but for the sake of
clarity, you might want to
      use the texrc.vim file described above

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=822510&group_id=52322

Re: [Vim-latex-devel] syntax/tex.vim addons

[Mikolaj M. <mi...@wp...>]

Dnia Thursday 09 of October 2003 16:17, Johannes Tanzler napisał:
> Hi,
>
> I've attached my ~/.vim/syntax/tex.vim file -- it provides
> pseudo-WYSIWYM for font-commands (in GVim), and more colors (\footnote,
> \title, and sectioning commands)
>
> Perhaps it's of use for your project.
>
We don't have syntax file in lS and I don't plan to introduce it (at
least until we will deal with conceal features). But your propositions
look interesting. Maybe you should send them to maintainer of tex syntax
file - "Charles E. Campbell" <ce...@gr...>?

m.

Re: [Vim-latex-devel] Function: Tex_InsertItem

[Mikolaj M. <mi...@wp...>]

Dnia Thursday 09 of October 2003 16:17, Johannes Tanzler napisał:
>
> the following function inserts "\item", "\item[]", or "\item{}[]"
> depending on the environment the cursor currently is in.
> There are two mappings: <M-RET> starts a new line before inserting,
> "<Leader>it" inserts the item in the current line.

Thanks.

I changed it little to better fit into lS:

" Tex_InsertItem: insert item into a list   {{{
"    Description: Find last \begin line, extract env name, return to the 
start
"    			  position and insert proper \item, depending on env name.
"    			  Env names are stored in g: variables it can be used by
"    			  package files. 
let g:Tex_ItemNormal = ',itemize,enumerate,theindex,' 
let g:Tex_ItemBib = ',thebibliography,' 
let g:Tex_ItemDescription = ',description,' 
function! Tex_InsertItem()

    " Get current environment: 
	let pos = line('.').' | normal! '.virtcol('.').'|'
    let env_line = search('^[^%]*\\begin{', 'bW')
    let env = matchstr(getline(env_line), '\\begin{\zs.\{-}\ze}')
	exe pos

    if g:Tex_ItemNormal =~ ','.env.','
        return IMAP_PutTextWithMovement("\\item ")
	elseif g:Tex_ItemDescription =~ ','.env.','
        return IMAP_PutTextWithMovement("\\item[<+label+>] <++>")
    elseif g:Tex_ItemBib =~ ','.env.','
        return IMAP_PutTextWithMovement("\\item[<+biblabel+>]{<+bibkey+>}<+
+>")
    else
        return ''
    endif

endfunction

inoremap <C-CR> <ESC>o<C-R>=Tex_InsertItem()<CR>
inoremap <Leader>it <C-R>=Tex_InsertItem()<CR>


There are still problems:

1.
Changed map from <M-CR> to <C-CR>. There are numerous difficulties with
M maps but Ctrl doesn't work in terminal Vim. Any ideas?

1a.
<Leader>it is rather uncommon form for lS Insert mode. Maybe ITE?

2.
Solved thing with quoted begin but it doesn't recognize \%. Such
construction should be extremely rare but if any regexp guru is reading 
advice would be appreciated :)

m.

Re: [Vim-latex-devel] Function: Tex_InsertItem

[Srinath A. <sr...@fa...>]

Hi Johannes

On Thu, 9 Oct 2003, Johannes Tanzler wrote:

> Hi,
>
> the following function inserts "\item", "\item[]", or "\item{}[]"
> depending on the environment the cursor currently is in.
> There are two mappings: <M-RET> starts a new line before inserting,
> "<Leader>it" inserts the item in the current line.

Thanks for this. I'm glad to include this in the default latex-suite
installation. I made a few changes to this. Its already up on the latest
vim-latex cvs tree. So you can check the changes there... The function
has been incorporated into the ftplugin/tex/brackets.vim script. I made
a few changes to better suit latex-suite (including not using marks to
remember position, logic for finding out if the cursor is outside a list
environment etc).

I also changed the default map to <M-i>. I took away the <M-ret> mapping
because it looks like <ret><M-i> is almost as short. Ofcourse, the user
can always construct the equivalent of the <M-ret> mapping using the
<Plug>ed mapping provided by default.

Thanks,
Srinath

[Vim-latex-devel] Function: Tex_InsertItem

[Johannes T. <joh...@ao...>]

Hi,

the following function inserts "\item", "\item[]", or "\item{}[]"
depending on the environment the cursor currently is in.
There are two mappings: <M-RET> starts a new line before inserting,
"<Leader>it" inserts the item in the current line.


regards,
Johannes

[Vim-latex-devel] syntax/tex.vim addons

[Johannes T. <joh...@ao...>]

Hi,

I've attached my ~/.vim/syntax/tex.vim file -- it provides
pseudo-WYSIWYM for font-commands (in GVim), and more colors (\footnote,
\title, and sectioning commands)

Perhaps it's of use for your project.

regards,
Johannes

Re: [Vim-latex-devel] automatic/remembered TTarget for a directory/project?

[Mikolaj M. <mi...@wp...>]

Dnia Monday 06 of October 2003 17:08, Maciej Kalisiak napisał:
> Hello,
>
> Is it possible to somehow remember what :TTarget was set to last time
> for a given file or project?  I thought that this setting might be
> remembered with :mksession, but it isn't.  If there is no way currently,
> I would like to nominate this for a feature request.
>
> Example of when the above is useful: I occasionally work on a paper
> which specifically requires PDF submission, and thus I will always want
> to use pdflatex (i.e., TTarget = pdf) for it, despite generally
> preferring dvi.  It would be nice that, whenever I load up the
> corresponding .tex file (perhaps by sourcing a session file), the
> TTarget was already set correctly.

I already suggested autocommand but part of "project" exists if you have
texproject.vim in your :scriptnames.

Put 
let g:Tex_DefaultTargetFormat = 'pdf'

in <main>.tex.latexmain. More about .latexmain files in
|latex-master-file|. Currently this is only 'dumb' file for triggering
some events but it can be used to store some settings. With
texproject.vim it will be sourced.

This feature isn't documented because it was not completed.

m.

-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/

Re: [Vim-latex-devel] automatic/remembered TTarget for a directory/project?

[Mikolaj M. <mi...@wp...>]

Dnia Wednesday 08 of October 2003 16:21, Alan Schmitt napisał:
> * Maciej Kalisiak (ma...@dg...) wrote:
> > Hello,
> >
> > Is it possible to somehow remember what :TTarget was set to last time
> > for a given file or project?  I thought that this setting might be
> > remembered with :mksession, but it isn't.  If there is no way
> > currently, I would like to nominate this for a feature request.
> >
Yes, this is a part of so called "project" feature - not existing yet.
IMO lS should create auxiliary file with saved settings like local
defined target, files existing in project, support for easy adding,
removing and viewing them and saving some variables coming from scanning
files - it should improve start up time of latex files in Vim.
Unfortunately now I don't have much time to introduce such big thing :(

But if you have any ideas please write what should be in "project".
Several times I saw implementing is quite easy in comparison with
designing UI.

> > Example of when the above is useful: I occasionally work on a paper
> > which specifically requires PDF submission, and thus I will always want
> > to use pdflatex (i.e., TTarget = pdf) for it, despite generally
> > preferring dvi.  It would be nice that, whenever I load up the
> > corresponding .tex file (perhaps by sourcing a session file), the
> > TTarget was already set correctly.
>
> How about using modelines ?

Modelines are for Vim options, not user defined variables.
But it should be possible it with autocommands:
au BufRead /path/to/project/* let g:Tex_DefaultTargetFormat='pdf'

m.
-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/

Re: [Vim-latex-devel] automatic/remembered TTarget for a directory/project?

[Maciej K. <ma...@dg...>]

On Wed, Oct 08, 2003 at 10:21:09AM -0400, Alan Schmitt wrote:
> * Maciej Kalisiak (ma...@dg...) wrote:
> > Is it possible to somehow remember what :TTarget was set to last time
> > for a given file or project?  I thought that this setting might be
> > remembered with :mksession, but it isn't.  If there is no way currently,
> > I would like to nominate this for a feature request.
> 
> How about using modelines ?

That is true... I totally forgot that modeline syntax is not restricted
to just setting of options.  I'll give that a try.  Although a
":mksession" method would be preferred... is there any local variable
that one could set that would have an effect similar to :TTarget (and be
saved out by :mksession)?

-- 
"Joy in looking and comprehending is nature's most beautiful gift."
	-- Albert Einstein

Re: [Vim-latex-devel] automatic/remembered TTarget for a directory/project?

[Alan S. <ala...@po...>]

* Maciej Kalisiak (ma...@dg...) wrote:
> Hello,
>=20
> Is it possible to somehow remember what :TTarget was set to last time
> for a given file or project?  I thought that this setting might be
> remembered with :mksession, but it isn't.  If there is no way currently,
> I would like to nominate this for a feature request.
>=20
> Example of when the above is useful: I occasionally work on a paper
> which specifically requires PDF submission, and thus I will always want
> to use pdflatex (i.e., TTarget =3D pdf) for it, despite generally
> preferring dvi.  It would be nice that, whenever I load up the
> corresponding .tex file (perhaps by sourcing a session file), the
> TTarget was already set correctly.

How about using modelines ?

:h modeline

Alan Schmitt

--=20
The hacker: someone who figured things out and made something cool happen.