vim-latex-devel

[Vim-latex-devel] [vim-latex - Help] A bug?

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

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

I have encountered a problem with one of my document.
I'm not sure whether it was because of a bug in vim-latex or
I was doing something wrong.

To illustrate the problem I have worked out a sample TeX file which only contains
the following lines:

------------------------- sample.tex -------------------
aaaaa

\section{AAA}

\begin{verbatim}
    \usepackage{anypackage}
\end{verbatim}
---------------------------- cut --------------------------

'sample.tex' can be loaded into vim without problem. But if
first open another TeX file by, say 'gvim somefile.tex', then load 'sample.tex'
with ':edit sample.tex', gvim blocks. By pressing Ctrl-C I get the following
messages:

Error detected while processing /home/zlb/.vim/ftplugin/tex_latexSuite.vim:
line   13:
Interrupted
Error detected while processing /usr/share/vim/vim61/ftplugin/tex.vim:
line    1:
Interrupted

The same problem also appears when toggling
between the two buffers with ":buffer 1" and ":buffer 2" commands, as long as
\section{AAA} is folded (the
problem does not appear if \section{AAA} is unfolded).

I was using 'latexSuite20030606.tar.bz'.


______________________________________________________________________
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/monitor.php?forum_id=173627

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

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

> https://sourceforge.net/forum/message.php?msg_id=2061707
> By: zlb
>

Unfortunately, it looks like a vim bug:

do the following: open up a new file and type:

bar
baz
foo
baz

Set fdm=manual and fold up the whole file (using ggVGzf). Open the
fold, put yourself on the first baz line. now close fold again. with
fold closed, search for baz using /baz. You will still be on the first
baz line, not the second.

This seems to be due to the default fold-behavior described at:

-----------------------------------%<-----------------------------------
For Ex commands the range is adjusted to always start at the first line of a
fold and end at the last line of a fold.  Thus this command: >
	:s/foo/bar/g
when used with the cursor on a closed fold, will replace "foo" with "bar" in
all lines of the fold.
This does not happen for |:folddoopen| and |:folddoclosed|.
-----------------------------------%<-----------------------------------

It will be kind of non-trivial to fix this! :( Basically, it will
involve opening up the whole file, doing the package scanning and
folding it back the way it was...

Srinath

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

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

Thanks for the quick response :-)

In fact I was trying to figure out what happened precisely
but since I'm not familiar with the Vim stuffs I have soon
found out that it was out of my reach :-(

Instead of seeking for a thorough solution which, as you stated,
seems to be quite involving, there might be some simple workaround.
For example, the '\usepackage' macros are generally placed in the
preamble before all sectioning commands and they don't cause troubles.
I ran into this problem because I was describing certain LaTeX packages,
and in my document the \usepackage commands which come after a \section
command are all between '\begin{verbatim}' and '\end{verbatim}'. I think
when generating foldmarkers the verbatim environments (as well as the
comment environment) should be skipped, and that will at least solve
my problem. Of course I don't know whether it's complicated or
not to skip the verbatim environments when scanning foldregions so
this is just a suggestion.

Best,
LB

On Sun, 15 Jun 2003, Srinath Avadhanula wrote:

>
> > https://sourceforge.net/forum/message.php?msg_id=2061707
> > By: zlb
> >
>
> Unfortunately, it looks like a vim bug:
>
> do the following: open up a new file and type:
>
> bar
> baz
> foo
> baz
>
> Set fdm=manual and fold up the whole file (using ggVGzf). Open the
> fold, put yourself on the first baz line. now close fold again. with
> fold closed, search for baz using /baz. You will still be on the first
> baz line, not the second.
>
> This seems to be due to the default fold-behavior described at:
>
> -----------------------------------%<-----------------------------------
> For Ex commands the range is adjusted to always start at the first line of a
> fold and end at the last line of a fold.  Thus this command: >
> 	:s/foo/bar/g
> when used with the cursor on a closed fold, will replace "foo" with "bar" in
> all lines of the fold.
> This does not happen for |:folddoopen| and |:folddoclosed|.
> -----------------------------------%<-----------------------------------
>
> It will be kind of non-trivial to fix this! :( Basically, it will
> involve opening up the whole file, doing the package scanning and
> folding it back the way it was...
>
> Srinath
>

--

[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

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.