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

Re: [Vim-latex-devel] copying lines between buffers

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

* Andreas Lagemann on Tuesday, April 04, 2006 at 11:40:40 +0200:
> I installed latex-suite recently. Since then I cannot yank a line in one
> latex-buffer open another one and paste it there.

Just for the record: I can't reproduce this here (vim7 on
MacOSX, svn HEAD vim-latex). Yanking and pasting between buffers
works as expected.

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

Fwd: [Vim-latex-devel] copying lines between buffers

[Javier R. <jer...@gm...>]

On 4/4/06, Andreas Lagemann <ae...@in...> wrote:
>
> Hello,
> I installed latex-suite recently. Since then I cannot yank a line in one
> latex-buffer open another one and paste it there.


I have the same problem. To be able to copy between buffers I'm using named
buffers, for example, to copy a line to buffer "a" I use the command:

"ayy

and to paste it on the other buffer

"ap

Despite the available workaround, this is IMHO a bug in vimlatex

Greets,

Javier Rojas

[Vim-latex-devel] copying lines between buffers

[Andreas L. <ae...@In...>]

Hello,
I installed latex-suite recently. Since then I cannot yank a line in one
latex-buffer open another one and paste it there. For me this is an
essential feature of vim. So I would like to ask if someone has an idea,
why this is so and how to change it. I'm pretty sure this is a
latex-suite issue because it works as before editing none latex files.

Best Regards,

Andreas Lagemann

[Vim-latex-devel] How can I change what a paragraph is?

[Sebastian M. <seb...@un...>]

Hi all

I just discovered the vim command "gqap".

Its very nice, but i would like to have a \n between \section{My
Section} and my text. Like so:

\section{My Section} 
Here is my Text.

\section{Next section}

How can i configure that in latex-suite?

TIA, Sebastian.

Re: [Vim-latex-devel] couple of questions

[Srinath A. <sri...@gm...>]

Hi Andreas,

On 3/31/06, Andreas Wagner <A.W...@st...> wrote:
> first of all thanks for this life-changing suite. I cannot imagine
> working without it anymore. After playing around with it a bit, I

Thanks for the encouragement :)

These are all excellent suggestions. Some of them are pretty trivial to
implement, some will require quite a bit of code rearrangement.

> I'd like to suggest to have Tex_package_detected be defined also when
> Tex_PackagesMenu=3D0 (else I found at least SmartDots to fail).
>
This is the suggestion which will probably take the longest. I am not
100% sure though, since I had very little to do with the packages
portion (it was mostly done by Mikolaj Machowski). In any case, I plan
to take a look at this after a few days.

> Second, the handy ellipsis package takes care of ellipsis dots as
> well, so that it would probably be better if SmartDots replaced the
> dots with \dots instead of \ldots when it is loaded, too.

Sounds good, I'll make the change.

> AFAIU, in the ngerman package file, there should be lines like these:
>    let g:TeX_package_ngerman =3D ''
>    let g:TeX_package_option_ngerman =3D ''
>

Sounds good, I'll make this change...

> Fourth, I would like to overwrite the EFC mapping (associated with
> filecontents env.) with another environment (actually, not an
> environment, but the footcite command from the jurabib package). So
> I have this in my ~/.vim/vimfiles/ftplugin/tex/texrc:
>
>      call IMAP('EFC',"\\footcite[<++>][<++>]{<++>}<++>",'tex')
>
> (I also have these in my texrc and this, i.e. S-F4, seems to work)
>      TexLet g:Tex_Env_footcite=3D"\\footcite[<++>][<++>]{<++>}<++>"
>      TexLet g:Tex_HotKeyMappings=3D'citation,quotation,quote,footcite'
>
> What can I do to have EFC remain mapped to the footcite env?
> (With EFN and ECT which I am using for footnote and cite env resp.
> command, it is working fine, too. Or are these overwritten after all,
> too?)

As matters stand right now, any IMAPs defined by the user are
over-written by latex-suite. This should probably be considered a bug.
I will fix this if it turns out it won't cause any problems.

In the meanwhile, a workaround is to define the IMAPs in
~/.vim/after/ftplugin/tex.vim

This file will get sourced _after_ latex-suite does its thing and it
will be able to over-write the IMAP created by latex-suite.

> Fifth and finally, I am trying to get together package support files
> for the packages I am using -- Out of the examples on the web and in
> the exmpl file, I am not sure which prefix should be prepended to
> brace commands that accept one option, like \fixme[margin]{nonsense}
> (I tried brd and nob, but both are giving two pairs of curly
> braces...)

It looks like there is no standard way of doing this! This should be
easy to fix. I'll make the change soon.

> I have attached another package support file, too, in case you're
> interested. (But this is the one I am still planning to improve.) I am
> not sure if the attachments will be stripped somewhere along the way,
> tho.
>

I did get the attachments fine. Thanks! I'll include these in the next
release.

Thanks!
Srinath

[Vim-latex-devel] couple of questions

[Andreas W. <A.W...@st...>]

Hi list,
first of all thanks for this life-changing suite. I cannot imagine 
working without it anymore. After playing around with it a bit, I 
thought now would be a good time to come out of the woodwork and point 
out a couple of things that I think could be improved or even suggest 
something for it. But of course, I also have questions. Bear with me, I 
am asking because I want to work not only /with/, but also a bit /on/ it 
(not like a real developer, tho), and am determined to finally share 
whatever I can come up with.

In this vein, I hope you forgive me for just sending you what is 
somewhat a collection of things that have bothered me at one time or 
another, and not splitting these question into several mails.
Anyway, here goes:


First,
I'd like to suggest to have Tex_package_detected be defined also when 
Tex_PackagesMenu=0 (else I found at least SmartDots to fail).



Second,
the handy ellipsis package takes care of ellipsis dots as well, so that 
it would probably be better if SmartDots replaced the dots with \dots 
instead of \ldots when it is loaded, too.
In main.vim:

" SmartDots: inserts \cdots instead of ... in math mode otherwise \ldots {{{
" if amsmath or ellipsis packages are detected then just use \dots and
" let those two take care of it.
if g:Tex_SmartKeyDot
         function! <SID>SmartDots()
                 if strpart(getline('.'), col('.')-3, 2) == '..' &&
                         \ ( g:Tex_package_detected =~ '\<amsmath\>' ||
                         \   g:Tex_package_detected =~ '\<ellipsis\>' )
                         return "\<bs>\<bs>\\dots"
                 elseif synIDattr(synID(line('.'),col('.')-1,0),"name") =~ '^texMath'
                         \&& strpart(getline('.'), col('.')-3, 2) == '..'
                         return "\<bs>\<bs>\\cdots"
                 elseif strpart(getline('.'), col('.')-3, 2) == '..'
                         return "\<bs>\<bs>\\ldots"
                 else
                         return '.'
                 endif
         endfunction

endif
" }}}

(I have attached a package support file for ellipsis. Is it a good idea 
to include the \dots command in there (which is redefined y the package) 
although it is a plain LaTeX command after all?)



Third,
AFAIU, in the ngerman package file, there should be lines like these:
   let g:TeX_package_ngerman = ''
   let g:TeX_package_option_ngerman = ''



Fourth,
I would like to overwrite the EFC mapping (associated with filecontents 
env.) with another environment (actually, not an environment, but the 
footcite command from the jurabib package). So I have this in my 
~/.vim/vimfiles/ftplugin/tex/texrc:

     call IMAP('EFC',"\\footcite[<++>][<++>]{<++>}<++>",'tex')

(I also have these in my texrc and this, i.e. S-F4, seems to work)
     TexLet g:Tex_Env_footcite="\\footcite[<++>][<++>]{<++>}<++>"
     TexLet g:Tex_HotKeyMappings='citation,quotation,quote,footcite'

What can I do to have EFC remain mapped to the footcite env?
(With EFN and ECT which I am using for footnote and cite env resp. 
command, it is working fine, too. Or are these overwritten after all, 
too?)



Fifth and finally,
I am trying to get together package support files for the packages I am 
using -- Out of the examples on the web and in the exmpl file, I am not 
sure which prefix should be prepended to brace commands that accept one 
option, like \fixme[margin]{nonsense} (I tried brd and nob, but both are 
giving two pairs of curly braces...)

- Coming to think of it, can anyone explain how this goes for the 
   various combinations of one, two or several options /and/ one, two or 
   several brace expressions (like the 'brd' prefix IIUC).?
- What do those 'special' formats mean?
- And is there a way to specify which options such a command can take 
   (like the specification of the package options is possible)? Or do you 
   just put the cursor in there and use 'special' type commands (I think 
   I understand that's how it works in the hyperref support file)?



I have attached another package support file, too, in case you're 
interested. (But this is the one I am still planning to improve.) I am 
not sure if the attachments will be stripped somewhere along the way, 
tho.



Thanks for your patience,
Andreas Wagner



-- 
Don't hate yourself in the morning, sleep until noon.

-- 
My Public PGP Keys:
1024 Bit DH/DSS: 0x869F81BA
76 Bit RSA:     0x1AD97BA5

Re: [Vim-latex-devel] Path expansion

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

Hi Srinath,

* Srinath Avadhanula on Wednesday, March 29, 2006 at 13:42:52 -0800:
> On 3/28/06, Christian Ebert <bla...@gm...> wrote:
> [snip description of what Tex_ImageDir is used for]
> 
>> Hope it has become clearer instead of more confusing.
>> 
> Yes... Its become clearer. I have enabled this feature in SVN in the
> latest release.

Great, works fine; now I've run out of criticisism ...

Thanks

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

Re: [Vim-latex-devel] Path expansion

[Srinath A. <sri...@gm...>]

Hi Christian,

On 3/28/06, Christian Ebert <bla...@gm...> wrote:

[snip description of what Tex_ImageDir is used for]

>
> Hope it has become clearer instead of more confusing.
>
Yes... Its become clearer. I have enabled this feature in SVN in the
latest release.

Srinath

Re: [Vim-latex-devel] Path expansion

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

Hi Srinath,

* Srinath Avadhanula on Tuesday, March 28, 2006 at 10:33:56 -0800:
> On 3/28/06, Christian Ebert <bla...@gm...> wrote:

<snipped problems already solved in svn HEAD>

> The maps are:
>     C: display the files in the current directory. i.e, if you do
>         :cd /some/dir
>        and then press "C" it will display the contents of /some/dir.

Ok, I get it, and it works exactly like that with new version.

>> [ collect files with python? ]
>> 
> ??

Just mumbling to myself that perhaps something like  python's
os.walk() might be faster than vim. So, forget it, as, at least
for me it's fast enough now.

>> 2. Feature proposal:
>> 
>> At the moment it inserts the relative path. I might not be the
>> only one who puts (links to) the image file in $TEXINPUTS (that's
>> what it's for after all) or (less friendly on resources) declares
>> \graphicspath. That way you can move around your source-file and
>> don't have to worry about paths. Wouldn't it make sense to have
>> an option to get just the basename (w/o suffix) of the image? --
>> Unless that's what's "C" for.
> 
> No thats not what C is for... This seems like an easy thing to add
> though... I'm personally do not use this feature of latex though, so
> you'll have to explain this in a little bit more detail to have it
> become a feature.

Example:

I put my images (or links to them) in the directory

$HOME/texinputs

I have set the environment variable $TEXINPUTS to the above
directory. This means LaTeX will include the files in that
directory in its filename database.

Suppose I have a Document at

$HOME/Testdir/test.tex

Now, I write into test.tex:

\includegraphics{image}

[ just the basename ]

and if

$HOME/texinputs/image.jpg

exists, it is found and included in the (pdf)output.

Same thing happens if I have declared

\graphicspath{{/path/to/home/texinputs}}

[ See grfguide.ps ]

in my document (it only eats loads of LaTeX' resources when there
many files in that directory, or several directories).

This has the big advantage over declaring an absolute path that
in the case I move test.tex to eg.

$HOME/Anotherdirectory/test.tex

the document still compiles without changes.

Similarly when I decide to move the images to

$HOME/Images

I simply change $TEXINPUTS to $HOME/Images.

Whereas when I have absolute paths in my document I have to
change every path to every image.

Hope it has become clearer instead of more confusing.

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

Re: [Vim-latex-devel] Path expansion

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

* Srinath Avadhanula on Tuesday, March 28, 2006 at 11:19:01 -0800:
> I timed it more carefully. It looks like FB_DisplayFiles() takes 104
> seconds to display 2300 files!

My estimated 20 secs were for 430 files.

> I therefore changed the way FB_DisplayFiles() works. With the
> improvement, it takes about 0.6s econds with vim7 and 1.0
> second with vim6.
> 
> I checked the modification to SVN. See if it improves things in your
> case as well.

Works like a charm, unfortunately it is too fast to give me
enough time to time it ;-) Thank you.

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

Re: [Vim-latex-devel] Path expansion

[Srinath A. <sri...@gm...>]

Hi Christian,

On 3/28/06, Srinath Avadhanula <sri...@gm...> wrote:
> which contains about 2200 files, then the time it takes is around 20
> seconds or so. So if you have on the order of these many files then it
> will take a lot of time.

I timed it more carefully. It looks like FB_DisplayFiles() takes 104
seconds to display 2300 files! I therefore changed the way
FB_DisplayFiles() works. With the improvement, it takes about 0.6s econds
with vim7 and 1.0 second with vim6.

I checked the modification to SVN. See if it improves things in your
case as well. I think it should unless the slowdown was caused by
something else in your case.

Srinath

Re: [Vim-latex-devel] Path expansion

[Srinath A. <sri...@gm...>]

Hi Christian,

On 3/28/06, Christian Ebert <bla...@gm...> wrote:
> r1005 works -- up to a certain extent:
>
> 1. It almost freezes vim; symptoms:
>
> a) It takes ages (ca. 20 secs) to display the explorer.
>
> b) Reaction to pressing eg. "C" or "?" takes about the same
> amount of time.
>
> c) Choosing a file with <CR> works instantly.
>
> d) What does "C" actually do? I don't see a difference.
>

It looks like maybe your setting of Tex_ImageDir points to a directory
with a _lot_ of files. Basically, all of these symptoms point to the
function FB_DisplayFiles() taking a lot of time. This function basically
does a glob('*'), i.e, gets a list of all files and then "filters" them
according to FB_AllowRegexp and FB_RejectRegexp. This function is in
~/.vim/plugin/filebrowser.vim, which ships with latex-suite. Its
actually a small function, so you could if you want take a look at it.

The most probable cause of the slow-down is the FB_Strntok() function,
which FB_DisplayFiles() files uses to get the i^th line of the <NL>
seperated string returned by glob('*'). If the string is huge, the time
it takes to split the list grows exponentially. I tested that on my
computer, if I say:

    :call FB_OpenFileBrowser('c:/WINDOWS/system32')

which contains about 2200 files, then the time it takes is around 20
seconds or so. So if you have on the order of these many files then it
will take a lot of time.

The maps are:
    C: display the files in the current directory. i.e, if you do
        :cd /some/dir
       and then press "C" it will display the contents of /some/dir.

    ?: Basically expands the help section. Unfortunately, since I wrote
       it very inefficiently, it also completely re-reads and re-parses
       the file list.

Both these functions call FB_DisplayFiles().

I remember that in another place in latex-suite, I got a very
significant speed up by using stridx() rather than *Strntok(). Maybe
thats the way to go here.

> [ collect files with python? ]
>
??

> 2. Feature proposal:
>
> At the moment it inserts the relative path. I might not be the
> only one who puts (links to) the image file in $TEXINPUTS (that's
> what it's for after all) or (less friendly on resources) declares
> \graphicspath. That way you can move around your source-file and
> don't have to worry about paths. Wouldn't it make sense to have
> an option to get just the basename (w/o suffix) of the image? --
> Unless that's what's "C" for.

No thats not what C is for... This seems like an easy thing to add
though... I'm personally do not use this feature of latex though, so
you'll have to explain this in a little bit more detail to have it
become a feature.

HTH
Srinath

Re: [Vim-latex-devel] Path expansion

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

Hi Srinath,

* Srinath Avadhanula on Sunday, March 26, 2006 at 09:18:48 -0800:
> In some release of latex-suite, support for Tex_ImageDir() got taken
> out! :( I don't know how it happened. Its an easy fix though... I'll
> make the required change in SVN.

r1005 works -- up to a certain extent:

1. It almost freezes vim; symptoms:

a) It takes ages (ca. 20 secs) to display the explorer.

b) Reaction to pressing eg. "C" or "?" takes about the same
amount of time.

c) Choosing a file with <CR> works instantly.

d) What does "C" actually do? I don't see a difference.

[ collect files with python? ]

2. Feature proposal:

At the moment it inserts the relative path. I might not be the
only one who puts (links to) the image file in $TEXINPUTS (that's
what it's for after all) or (less friendly on resources) declares
\graphicspath. That way you can move around your source-file and
don't have to worry about paths. Wouldn't it make sense to have
an option to get just the basename (w/o suffix) of the image? --
Unless that's what's "C" for.


My platform is MacOS 10.3.9 and I only use vim7 without gui. I am
awaiting debugging instructions ;-)

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

Re: [Vim-latex-devel] Re: search for bibtex entry by regexp

[Srinath A. <sri...@gm...>]

Hi Fabian,


On 3/27/06, Fabian Braennstroem <f.b...@gm...> wrote:
> There is a small problem in bibtools.py from line 84:
>
>
>             else:
> <<<<<<< .mine
>                 mn =3D re.search(r',|$', body)
>                 if not mn:
>                     return None
>                 value =3D m.group(2) + body[:(mn.start(0))].rstrip()
> =3D=3D=3D=3D=3D=3D=3D
>                 # $ always matches. So we do not need to do any
>                 # error-checking.
>                 mn =3D re.search(r',|$', body)
>                 value =3D m.group(2) + body[:(mn.start(0))].rstrip()
> >>>>>>> .r1004
>
>
> Those >>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D appeared; I do not know if it=
 is bad
> svn usage from me...
>
Those are called "conflict-markers". Basically, since you helped me by
modifying bibtools.py, when you ran ``svn update``, it thought that
there were local modifications to bibtools.py which conflicted with the
remote changes... It's an SVN thingie...

Srinath

[Vim-latex-devel] Re: search for bibtex entry by regexp

[Fabian B. <f.b...@gm...>]

Hi Srinath,

* On 25 Mar 2006 * Srinath Avadhanula wrote:

> Hi Fabian,
> 
> On 3/24/06, Fabian Braennstroem <f.b...@gm...> wrote:
> > ... but when I try to display all entries after I used the
> > filter, I get:
> >
> > Error detected while processing function
> > Tex_HandleBibShortcuts..Tex_DisplayBibList:
> > line   22:
> > Traceback (most recent call last):
> >   File "<string>", line 1, in ?
> >   File "/home/fab/.vim/ftplugin/latex-suite/bibtools.py",
> > line 198, in __str__
> >     if b['key'] and b.satisfies(self.filters):
> >   File "/home/fab/.vim/ftplugin/latex-suite/bibtools.py",
> > line 152, in satisfies
> >     for field, regexp in filters:
> > ValueError: need more than 1 value to unpack
> 
> This problem has been fixed in SVN.
> 
> 
> > and one small feature request :-) When I use the filter like
> > 'a Searched_Author <CR>', I get and have to press <CR> again
> > to display the results:
> >
> > (a) all (f) filter (s) sort (n) next (p) previous (q) quit (<CR>) choose
> > Hit ENTER or type command to continue
> >
> > Would that work without a second <CR>,too?
> 
> This has been fixed as well.

There is a small problem in bibtools.py from line 84:


            else:
<<<<<<< .mine
                mn = re.search(r',|$', body)
                if not mn:
                    return None
                value = m.group(2) + body[:(mn.start(0))].rstrip()
=======
                # $ always matches. So we do not need to do any
                # error-checking.
                mn = re.search(r',|$', body)
                value = m.group(2) + body[:(mn.start(0))].rstrip()
>>>>>>> .r1004


Those >>>>>> ========== appeared; I do not know if it is bad
svn usage from me...

Anyways, commenting those lines out, everything works very
nice!

Thanks!
Fabian 

Re: [Vim-latex-devel] Path expansion (was: search for bibtex entry by regexp)

[Srinath A. <sri...@gm...>]

Hi Christian,

On 3/25/06, Christian Ebert <bla...@gm...> wrote:
>
> Yes. Under the condition that I do not use "~" in Tex_BIBINPUTS.
> I have to include the full path to my $HOME -- $HOME is not
> expanded either. Either the docs are misleading or again I
> misunderstood.
>
> latex-suite.txt, line 1126f.:
>
> |Example:  >
> |    let g:Tex_TEXINPUTS =3D '~/texmf/mypackages/**,./**'
>
> As h:file-searching does not say anything about variable
> expansion it might only be a matter of correcting the docs.

Yes, I mistakenly assumed that Vim's file-searching used expansion. This
might be a good time to convince Bram to support it since he's making
a new release.

> As file-searching can be quite time consuming perhaps the example
> could be changed to something like
>
> Example:  >
>     let g:Tex_TEXINPUTS =3D '/full/path/to/home/texmf/mypackages/**2,./**=
'
>
This makes sense as well. I'll change the docs for both cases.

> While I was at it I set Tex_ImageDir for the first time. But it
> doesn't seem to work for me. I have
>
> let g:Tex_ImageDir =3D '/Users/chris/texinputs'
>
> where my images are stored. So I believed that when doing
>
> \includegraphics{
>
> and pressing <F9> the explorer would also show me the contents of
> /Users/chris/texinputs but I only get the current directory. What
> am I doing wrong?

In some release of latex-suite, support for Tex_ImageDir() got taken
out! :( I don't know how it happened. Its an easy fix though... I'll
make the required change in SVN.

> Anyway, thanks for latex-suite. Perhaps you don't get as much
> feedback as you sometimes whish because people are too busy using
> it and it just works ;-)
>
Thanks :) I hope thats the case.

Srinath

[Vim-latex-devel] Path expansion (was: search for bibtex entry by regexp)

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

Hi Srinath,

* Srinath Avadhanula on Friday, March 24, 2006 at 20:44:45 -0800:
> On 3/24/06, Christian Ebert <bla...@gm...> wrote:
>> Something went wrong with my Tex_BIBINPUTS setting. Sorry for the
>> noise. All works fine now.
>> 
> Thanks for confirming that it works for you. That makes you the first
> documented evidence of my programming working for someone other than me
> :)

hehe

> I'm going to assume that both bibtools.py and the \cite completion from
> within Vim work for you, i.e., the whole thing.

Yes. Under the condition that I do not use "~" in Tex_BIBINPUTS.
I have to include the full path to my $HOME -- $HOME is not
expanded either. Either the docs are misleading or again I
misunderstood.

latex-suite.txt, line 1126f.:

|Example:  >
|    let g:Tex_TEXINPUTS = '~/texmf/mypackages/**,./**'

As h:file-searching does not say anything about variable
expansion it might only be a matter of correcting the docs.

As file-searching can be quite time consuming perhaps the example
could be changed to something like

Example:  >
    let g:Tex_TEXINPUTS = '/full/path/to/home/texmf/mypackages/**2,./**'

While I was at it I set Tex_ImageDir for the first time. But it
doesn't seem to work for me. I have

let g:Tex_ImageDir = '/Users/chris/texinputs'

where my images are stored. So I believed that when doing

\includegraphics{

and pressing <F9> the explorer would also show me the contents of
/Users/chris/texinputs but I only get the current directory. What
am I doing wrong?

Anyway, thanks for latex-suite. Perhaps you don't get as much
feedback as you sometimes whish because people are too busy using
it and it just works ;-)

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

Re: [Vim-latex-devel] Re: search for bibtex entry by regexp

[Srinath A. <sri...@gm...>]

Hi Fabian,

On 3/24/06, Fabian Braennstroem <f.b...@gm...> wrote:
> ... but when I try to display all entries after I used the
> filter, I get:
>
> Error detected while processing function
> Tex_HandleBibShortcuts..Tex_DisplayBibList:
> line   22:
> Traceback (most recent call last):
>   File "<string>", line 1, in ?
>   File "/home/fab/.vim/ftplugin/latex-suite/bibtools.py",
> line 198, in __str__
>     if b['key'] and b.satisfies(self.filters):
>   File "/home/fab/.vim/ftplugin/latex-suite/bibtools.py",
> line 152, in satisfies
>     for field, regexp in filters:
> ValueError: need more than 1 value to unpack

This problem has been fixed in SVN.


> and one small feature request :-) When I use the filter like
> 'a Searched_Author <CR>', I get and have to press <CR> again
> to display the results:
>
> (a) all (f) filter (s) sort (n) next (p) previous (q) quit (<CR>) choose
> Hit ENTER or type command to continue
>
> Would that work without a second <CR>,too?

This has been fixed as well.

Srinath

Re: [Vim-latex-devel] Re: search for bibtex entry by regexp

[Srinath A. <sri...@gm...>]

Hi Chris,

On 3/24/06, Christian Ebert <bla...@gm...> wrote:
> * Christian Ebert on Friday, March 24, 2006 at 11:04:35 +0100:
> > Apparently my bib file is not found. I'll try and dig into this.
>
> Something went wrong with my Tex_BIBINPUTS setting. Sorry for the
> noise. All works fine now.
>
Thanks for confirming that it works for you. That makes you the first
documented evidence of my programming working for someone other than me
:)

I'm going to assume that both bibtools.py and the \cite completion from
within Vim work for you, i.e., the whole thing.

Srinath

Re: [Vim-latex-devel] Re: search for bibtex entry by regexp

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

* Christian Ebert on Friday, March 24, 2006 at 11:04:35 +0100:
> Apparently my bib file is not found. I'll try and dig into this.

Something went wrong with my Tex_BIBINPUTS setting. Sorry for the
noise. All works fine now.

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

[Vim-latex-devel] Re: search for bibtex entry by regexp

[Fabian B. <f.b...@gm...>]

Hi Srinath,

* On 24 Mar 2006 * Srinath Avadhanula wrote:

> Hi Fabian,
> 
> On 3/23/06, Fabian Braennstroem <f.b...@gm...> wrote:
> >
> > `-->  python bibtools.py /home/fab/HOME/Dissertation/CFD/Projects/Building_airflow/Paper/Vergleich_RANS-LES/biballsed.bib
> > Traceback (most recent call last):
> >   File "bibtools.py", line 227, in ?
> >     bf = BibFile(sys.argv[1])
> >   File "bibtools.py", line 174, in __init__
> >     self.addfile(f)
> >   File "bibtools.py", line 189, in addfile
> >     b = Bibliography('@' + f, self.macros)
> >   File "bibtools.py", line 86, in __init__
> >     value = m.group(2) + mn.group(0)
> > AttributeError: 'NoneType' object has no attribute 'group'
> >
> Okay, I relaxed the parsing pretty much the whole way... Hopefully
> things work now. Try the attached file...

It works for me, thanks :-)

... but when I try to display all entries after I used the
filter, I get:

Error detected while processing function
Tex_HandleBibShortcuts..Tex_DisplayBibList:
line   22:
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "/home/fab/.vim/ftplugin/latex-suite/bibtools.py",
line 198, in __str__
    if b['key'] and b.satisfies(self.filters):
  File "/home/fab/.vim/ftplugin/latex-suite/bibtools.py",
line 152, in satisfies
    for field, regexp in filters:
ValueError: need more than 1 value to unpack
(a) all (f) filter (s) sort (n) next (p) previous (q) quit
(<CR>) choose
Hit ENTER or type command to continue


and one small feature request :-) When I use the filter like
'a Searched_Author <CR>', I get and have to press <CR> again
to display the results:

(a) all (f) filter (s) sort (n) next (p) previous (q) quit (<CR>) choose
Hit ENTER or type command to continue

Would that work without a second <CR>,too?

Thanks!
Fabian

-- 

Re: [Vim-latex-devel] Re: search for bibtex entry by regexp

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

* Srinath Avadhanula on Friday, March 24, 2006 at 01:16:14 -0800:
> Okay, I relaxed the parsing pretty much the whole way... Hopefully
> things work now. Try the attached file...

Works with the "python bibtools.py /path/to/bibfile" but here I
still get an empty __OUTLINE__ window.

Apparently my bib file is not found. I'll try and dig into this.

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

Re: [Vim-latex-devel] Re: search for bibtex entry by regexp

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

* Srinath Avadhanula on Thursday, March 23, 2006 at 17:08:51 -0800:
>             elif re.match(r'\d', m.group(2)):
>                 mn = re.match(r'\d+', body)

                 if not mn:
                     return None

>                 value = m.group(2) + mn.group(0)

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

Re: [Vim-latex-devel] Viewer doesnt start in Ubuntu Dapper Drake

[Sebastian M. <seb...@un...>]

Am Donnerstag, den 23.03.2006, 11:04 -0800 schrieb Srinath Avadhanula:
> 2. If none of this gives you any new information, you can try as a last
>    resort looking at the Tex_ViewLaTeX() function in
>    ~/.vim/ftplugin/latex-suite/compiler.vim. This is the function
>    invoked when you type \lv.

Bad news: wrong CWD was wrong ..

I looked into the function and put some new debug statements there to be
sure what the cwd is. There was no problem at all.

Good news: 

Problem is fixed. :-) Here a small log of my analysis:

When i opened the file in nautilus (the gnome file explorer) with "GVim
Text Editor", I had _two_ buffers in vim. One with "~/path/file.tex" and
one with "file:///home/me/path/file.tex". Dont know why. 

But starting a file from nautilus with my homebrewn command "gvim", i
had only one buffer, and surprisingly "\lv" works fine.

To reproduce the error, I launched gvim from the shell the same way it
is launched from nautilus:

# gvim -f file:///home/me/path/file.tex

And look, i had two buffers and \lv didnt work. Interestingly, 

# gvim  file:///... (without '-f')

opens two buffers but \lv works. 

Looking into the man-page "-f" means "foreground, do not fork and detach
from the shell vim was started in". Whatever that means.

Testing

# gvim -f path/file.tex

results in one buffer, but \lv doesnt work. So forget the two buffers
and file:// URL and focus on "-f"

So i guess the problem is analyzed and solved, but im not sure whose it
is :-)

regards, Sebastian.

Re: [Vim-latex-devel] Re: search for bibtex entry by regexp

[Srinath A. <sri...@gm...>]

Hi Fabian,

On 3/23/06, Fabian Braennstroem <f.b...@gm...> wrote:
>
> `-->  python bibtools.py /home/fab/HOME/Dissertation/CFD/Projects/Buildin=
g_airflow/Paper/Vergleich_RANS-LES/biballsed.bib
> Traceback (most recent call last):
>   File "bibtools.py", line 227, in ?
>     bf =3D BibFile(sys.argv[1])
>   File "bibtools.py", line 174, in __init__
>     self.addfile(f)
>   File "bibtools.py", line 189, in addfile
>     b =3D Bibliography('@' + f, self.macros)
>   File "bibtools.py", line 86, in __init__
>     value =3D m.group(2) + mn.group(0)
> AttributeError: 'NoneType' object has no attribute 'group'
>
Okay, I relaxed the parsing pretty much the whole way... Hopefully
things work now. Try the attached file...

Srinath