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

Re: [Vim-latex-devel] site CVS

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

Hey Mikolaj,

I just fixed the web page screwup. The problem before was that the
groups htdocs/ directory was checked out with

cvs -d:ext:srinathava@cvs1 ...

Thats why it asked you for my password last time.

Now I have checked it out with anonymous pserver. I have also changed
the permissions of the htdocs/ directory to be group writable. Therefore
anyone should be able to log into sf.net, change to the groups htdocs
directory and run

cvs update -q

You can also optionally cd to htdocs/packages and do a

cvs update -q

NOTE: The htdocs/packages directory is a local repository copy of
'vimfiles/ftplugin/latex-suite/packages' module not the
'htdocs/packages' module. I will actually remove the htdocs/pacakges
from the master CVS sometime soon.

NOTE 2: I need to do similar things to the htdocs/templates directory...

I think therefore that a cron job can be simplified to:

-----------------------%<-----------------------
#!/bin/sh

# update the htdocs directory
cd /home/groups/v/vim/vim-latex/htdocs; cvs -q update
# update the packages directory
cd /home/groups/v/vim/vim-latex/htdocs/packages; cvs -q update
-----------------------%<-----------------------

This will I think be also a bit more robust.

I do not have a good idea about how to set up cron jobs. If you want,
you can go ahead and do it using your sf.net account.

NOTE: The web-page now points to the latest "raw" CVS version of the
htdocs module... This means that some of the things point to
comingsoon.inc, and the links link is broken (the irony!)

I am also thinking of making syncmail send emails for commits to the
htdocs/ module. If the subscribers to vim-latex-cvs object, I will
reconsider.

Thanks,

Srinath

> ------------
> #!/bin/sh
> # download cvs tarball from its place to our home directory
> wget -q http://cvs1.sourceforge.net/cvstarballs/vim-latex-cvsroot.tar.gz
>
> # move it to proper place of www directory
> cp vim-latex-cvsroot.tar.gz /home/groups/v/vim/vim-latex/htdocs/packages
>
> # now, we have to go there
> cd /home/groups/v/vim/vim-latex/htdocs/packages
>
> # here is a hack, I can't believe this is not possible with simple
> # switch but also I am not able to find it in tar docs.
> tar -zxf vim-latex-cvsroot.tar.gz vimfiles/ftplugin/latex-suite/packages/
> cp -f vimfiles/ftplugin/latex-suite/packages/* .
> rm -rf vimfiles/ vim-latex-cvsroot.tar.gz
> -------------
>

-- 
Srinath Avadhanula
Dec 14 2:59pm
Ray's Rule of Precision:
	Measure with a micrometer.  Mark with chalk.  Cut with an axe.

Re: [Vim-latex-devel] site CVS

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

On Fri, Dec 13, 2002 at 10:17:56PM -0800, Srinath Avadhanula wrote:
> Hello!
> I just got done with an exam. So a little time for vimming. I will
> mostly do the outstanding things like the web-page cvs screw up and a
> few other things. I will also put this new version of imaps.vim into a
> new branch which I shall call... lets see...

I think we can remove package and template directories from site CVS.
Not from site but from CVS. Better solution to update this files will be
running cron with script like that:

------------
#!/bin/sh
# download cvs tarball from its place to our home directory
wget -q http://cvs1.sourceforge.net/cvstarballs/vim-latex-cvsroot.tar.gz

# move it to proper place of www directory
cp vim-latex-cvsroot.tar.gz /home/groups/v/vim/vim-latex/htdocs/packages

# now, we have to go there
cd /home/groups/v/vim/vim-latex/htdocs/packages

# here is a hack, I can't believe this is not possible with simple
# switch but also I am not able to find it in tar docs.
tar -zxf vim-latex-cvsroot.tar.gz vimfiles/ftplugin/latex-suite/packages/
cp -f vimfiles/ftplugin/latex-suite/packages/* .
rm -rf vimfiles/ vim-latex-cvsroot.tar.gz
-------------

I did not tested it fully (wget works). Next steps are impossible
because I do not have permissions. Big plus there is only one
place where package files (also templates) are.

[Vim-latex-devel] Re: new version of imaps.vim

[Luc H. <her...@fr...>]

* On Sat, Dec 14, 2002 at 12:38:10PM -0800, Srinath Avadhanula <sr...@fa...> wrote:
> This is bad! We have a problem with vim's limitation of only letting
> functions take upto 20 arguments...

Is it the same with commands ?


> call Tex_IMAP('EPI', "\\begin{picture}(<+width+>, <+height+>)"
>                 \ . "(<+xoff+>,<+yoff+>)\<cr>\\put(<+xoff+>,<+yoff+>)"
>                 \ . "{\\framebox(<++>,<++>){<++>}}\<cr>\\end{picture}<++>",
>                 \ 'tex')
> creates more than 20 arguments!

> So... Whats the hack around it?

template-files ?
Moreover, it is easier for the end user to configure -- if he needs to.

> [encoding]
> Another thing to note: There seem to be a lot of patches in vim 6.0
> towards MB chars... Therefore, maybe we should only test on vim 6.0
> w/o patches henceforth, so we have the safest...

I ran Benji's `experiment' on Gvim-win32 6.1-263 on MsWindows Me.
And I get the same result he did.


-- 
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] new version of imaps.vim

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

This is bad! We have a problem with vim's limitation of only letting
functions take upto 20 arguments...

On Sat, 14 Dec 2002, Benji Fisher wrote:

> > NOTE: This is a work in progress. the changed version of Tex_IMAP() is not
> > yet working quite robustly enought. It is sometimes generating more
> > arguments than are needed.
>
>       Examples?  Maybe my simplified version will work better.

Thanks for the simplifications!  Turns out the Tex_IMAP() function was
fine. But the following

call Tex_IMAP('EPI', "\\begin{picture}(<+width+>, <+height+>)"
                \ . "(<+xoff+>,<+yoff+>)\<cr>\\put(<+xoff+>,<+yoff+>)"
                \ . "{\\framebox(<++>,<++>){<++>}}\<cr>\\end{picture}<++>",
                \ 'tex')

creates more than 20 arguments!

Now what? A long term solution to this problem is ofcourse changing vim
to be more script friendly and accept more than 20 arguments (Its bad
that there are limitations in the first place!). But I suspect that Bram
will most probably ask us to use some hack to get around the limitation
rather than change things... And even if he does change it, it will be
bad to make latex-suite depend on the very latest vim being installed.

So... Whats the hack around it?

Maybe if IMAP() is called with the same LHS more than once, it appends
this RHS to the previous RHS? Then change Tex_IMAP() to call
IMAP() with chunks of 20 arguments each time? This is sad... A simple
function getting needlessly complex.

I'll let others think about it / implement it :)

About imaps... For sometime I have been thinking of having IMAPS() take
a flag which makes it "safe", i.e if the user defines other mappings
with the same LHS before latex-suite, it will not override his
mappings... Now the flag argument could also be useful for telling us
whether this is part of an append or an entirely new RHS... The flag
cannot be optional. It will have to be left as '' if we just want it to
overwrite like now.

>       Can you test this?  It might be a solution to the remaining
> encoding problems.
>
> :let foo = "\xab"
> :echo iconv(foo, "latin1", &enc) =~ foo
>

Yes. This seems to echo 1 with encoding set to both 'latin1' and
'utf8'...

Another thing to note: There seem to be a lot of patches in vim 6.0
towards MB chars... Therefore, maybe we should only test on vim 6.0 w/o
patches henceforth, so we have the safest...

Srinath

-- 
Srinath Avadhanula
Dec 14 12:13pm
According to Arkansas law, Section 4761, Pope's Digest:  "No person
shall be permitted under any pretext whatever, to come nearer than
fifty feet of any door or window of any polling room, from the opening
of the polls until the completion of the count and the certification of
the returns."

Re: [Vim-latex-devel] Vim latex Suite is not compiling any .tex files (fwd)

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

On Fri, Dec 13, 2002 at 10:03:54AM -0500, Benji Fisher wrote:
>      Try
> :call RunLaTeX()
> You will probably get an error message about not understanding the 
> option --src-specials .  (I do, with RH 8.0 and whatever version of 
> teTeX it installs.)  In the texrc file, find the lines
> if has('win32')
> 	let s:CompileFlags = '--src-specials'
> 	TexLet g:Tex_EscapeChars = ''
> else
> 	let s:CompileFlags = '--src-specials'
> 	TexLet g:Tex_EscapeChars = '{}\'
> endif
> and change the fifth line to
> 	let s:CompileFlags = ''
> I have just uploaded a new version with this change, and also updated 
> the installation instructions in the comments at the top, but for now 
> you can only get the new version from CVS.

Oops :( My fault.
I thought I didn't make that commit.

m.

[Vim-latex-devel] new version of imaps.vim

[Benji F. <be...@me...>]

sri...@us... wrote:
> Modified Files:
>       Tag: b-newimaps
> 	imaps.vim=20
> Log Message:
> . modified the older version (Tex_IMAP) to use the new IMAP() function.
> . changed Tex_PutTextWithMovement() to just a hack. It substitutes '<+'=
 and
>   '+>' with the s:PlaceHolder*() variables and then calls the new
>   Imap_PutText...

      Thanks.  That was on my TODO list:  make Tex_IMAP() and=20
Tex_PutTextWithMovement() wrappers for the new versions.

> sorry for the short cvs log. I am running really late.
>=20
> NOTE: This is a work in progress. the changed version of Tex_IMAP() is =
not
> yet working quite robustly enought. It is sometimes generating more
> arguments than are needed.

      Examples?  Maybe my simplified version will work better.

> This commmit will be followed by another huge commit which is essential=
ly
> replacing all =E4 characters with <++>, =AB with <+ and so on....

      That was also on the TODO list. ;)

> Therefore...
>=20
> FROM HENCEFORTH:
>=20
> Use <+ and +> instead of =AB and =BB
>=20
> Better still, dont use any placeholders at all and use the new IMAP()
> function.

      Can you test this?  It might be a solution to the remaining=20
encoding problems.

:let foo =3D "\xab"
:echo iconv(foo, "latin1", &enc) =3D~ foo

It should return 1 (I hope).

					--Benji

[Vim-latex-devel] new CVS branch

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> Hello!
> 
> I just got done with an exam. So a little time for vimming. I will
> mostly do the outstanding things like the web-page cvs screw up and a
> few other things. I will also put this new version of imaps.vim into a
> new branch which I shall call... lets see...
> 
> b-newimaps
> 
> (Lets make it convention to name all branch tags with a leading 'b-').
> 
> Next time, keep your old copy of the repository and check out the new
> version into a new directory using
> 
> cvs checkout -r b-newimaps -d newdir

      Make that

$ cvs -z3 -d 
:ext:ma...@cv...:/cvsroot/vim-latex get -r 
b-newimaps -d alpha vimfiles

Replace "macvimx" with your user name and replace "alpha" with whatever 
you like.

> Then newdir will contain the new branch files.
> 
> BTW, branching in CVS is _extremeley_ easy, contrary to popular opinion.
> All that needs to be done is:
> 
> 1. go to the local repository.
> 2. "cvs update" to bring things up to date.
> 3. "cvs tag trunk-<date>" (replace <date> with current date).
>    this step is not essential. But it helps to keep a tagged version at
>    the root of every branch.
> 4. "cvs tag -b b-newimaps"
> 
> thats it!
> 
> then do the checkout thing I mention earlier.
> 
> Further reading:
> 
> http://cvsbook.red-bean.com/cvsbook.html#Branches
> 
> The link has a very nice explanation of all these concepts, including
> ofcourse how to merge changes from the branch onto the trunk.
> Recommended reading for any hacker :)
> 
> ------ IMPORTANT ---------
> Its very important to tag the whole branch repository every time a
> change from it is merged into the main trunk. I suppose we should
> somehow automate this...
> 
> This is important because if we want to merge from the branch onto the
> main trunk more than once, then we cvs needs to know the 2 revs from
> which it calculates the diff.
> ------ IMPORTANT ---------
> 
> In the web cvs, you will need to select the correct branch to view the
> branch versions of the files.
> 
> Hopefully, this email will serve as a future short reference for cvs
> branching. 
      Yes, hence the new subject line.  I apologize:  you sent us 
directions before, but that was when I had just installed Linux, and I 
only kept one copy, and I had problems ...  (Note to self:  time for a 
backup!)

					--Benji

Re: [Vim-latex-devel] [devel] Re: multibyte in patterns & jumping to placeholders

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

Hey Luc,

I will incorporate your jump function into latex-suite.

I am in a kind of a hurry right now, so I will write more later.

> So, if you agree with me to not waste energy, you can consider making
>     http://hermitte.free.fr/vim/ressources/plugin/bracketing.base.vim
> part of vim-latex ; after all Srinath already put me in the credits for
> my variation on Stephen's bracketing system. ;-)
>
the URL above gives me a URL not found on this server message.

> In order to have the documentation and the mapping that inserts a marker
> around a visually-selected text (or the current word) and the
> documentation, two other files are required. Check the tarball archive:
>     http://hermitte.free.fr/vim/ressources/ lh-map-tools.vim
>

The same for this one.

Thanks,

Srinath

Re: [Vim-latex-devel] new version of plugin/imaps.vim

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

Hello!

I just got done with an exam. So a little time for vimming. I will
mostly do the outstanding things like the web-page cvs screw up and a
few other things. I will also put this new version of imaps.vim into a
new branch which I shall call... lets see...

b-newimaps

(Lets make it convention to name all branch tags with a leading 'b-').

Next time, keep your old copy of the repository and check out the new
version into a new directory using

cvs checkout -r b-newimaps -d newdir

Then newdir will contain the new branch files.

BTW, branching in CVS is _extremeley_ easy, contrary to popular opinion.
All that needs to be done is:

1. go to the local repository.
2. "cvs update" to bring things up to date.
3. "cvs tag trunk-<date>" (replace <date> with current date).
   this step is not essential. But it helps to keep a tagged version at
   the root of every branch.
4. "cvs tag -b b-newimaps"

thats it!

then do the checkout thing I mention earlier.

Further reading:

http://cvsbook.red-bean.com/cvsbook.html#Branches

The link has a very nice explanation of all these concepts, including
ofcourse how to merge changes from the branch onto the trunk.
Recommended reading for any hacker :)

------ IMPORTANT ---------
Its very important to tag the whole branch repository every time a
change from it is merged into the main trunk. I suppose we should
somehow automate this...

This is important because if we want to merge from the branch onto the
main trunk more than once, then we cvs needs to know the 2 revs from
which it calculates the diff.
------ IMPORTANT ---------

In the web cvs, you will need to select the correct branch to view the
branch versions of the files.

Hopefully, this email will serve as a future short reference for cvs
branching.

Srinath

On Fri, 13 Dec 2002, Benji Fisher wrote:

>       Sorry, I should really start a new branch, but I have not done
> that before, so I am just attaching a file.  The new syntax is
>
> :call IMAP("tex", "foo", "b", "", "ar")
>
> I have tested this:  typing "foo" gives
>
> b|ar
>
> with | indicating the cursor position.  So far so good!
>
>       BUT it does not work if 'enc' is set to utf-8 and I use "\xab" and
> "\xbb" as place holders.  I'll post a question to the vim users' list.
>
>       Since this is in transition, it is not a good time to add new
> packages, etc.  If you want to add them with the old syntax, please use
> Tex_IMAP() and Tex_PutTextWithMovement() for now.
>
> 					--Benji
>

[Vim-latex-devel] [devel] Re: multibyte in patterns & jumping to placeholders

[Luc H. <her...@fr...>]

Benji,

I answer your point about encoding on the vim-latex ML.

* On Fri, Dec 13, 2002 at 06:21:15PM -0500, Benji Fisher <be...@me...> wrote:
>      More multi-byte woes.  If 'encoding' is set to utf-8, then a MB 
> character does not match itself!
> 
> :let foo = "\xab"
> :set enc?
>   encoding=latin1
> :echo foo =~ foo
> 1
> :set enc=utf8
> :set enc?
>   encoding=utf-8
> :echo foo =~ foo
> 0

The same workaround than the one I used, seems to work.

The important thing is that I require the encoding to be set before
every else. It is a very reallistic requirement.
The encoding is supposed to be set either by the system (red hat if I
understood it well, $LANG, locale() & co) or by .vimrc. Therefore,
'encoding' is set before any other plugin is run.

Then, we can notice that:
    :set enc=utf8
    :let foo = "\xab"
    :echo foo =~ foo
    0
does not work as it should, but:
    :set enc=utf8
    :let foo = nr2char(char2nr("\xab"))
    :echo foo =~ foo
    1
does !

Don't ask me why, but it does.

Earlier this week I ask on the vim ML if somebody could test my latest
version of my variation on Stephen Riehm's bracketing system, but I get
no response. :-((
So I don't know if it correctly works with encodings other than
latin1,2,15 or utf-8 set from .vimrc.

> Is this expected, or is it a bug?  Is there a work-around?  Am I
> supposed to do this?
> :echo iconv(foo, 'latin1', &enc) =~ foo
> 1

Hum, this is another quite odd workaround.

Otherwise, looks like a bug to me.
Or may be it concerns 'termencoding'. I don't know.

____________________
Regarding the other e-mail you sent on the vim-latex-devel ML.

> "        File: imaps.vim
> [...]
> " IMAP_Jumpfunc: takes user to next ?place-holder? {{{
> " Author: Gergely Kontra
> "         taken from mu-template.vim by him This idea is originally
> "         from Stephen Riehm's bracketing system.
> " modified by SA to use optional place holder characters.
> function! IMAP_Jumpfunc()

That is not completly true. The version Gergely rewrote was a simplifed
version over the function I originally wrote. I know he didn't wanted of
the complexity of my function. So he get rid of the possibility of
having different strings to express the markers (aka placeholders).
[However, selecting the marker instead of echoing its value is Gergely
idea]

Then Srinath unaware of my function, I guess, reintroduced this
functionnality.  But several things are still missing.

Here is a little list of other things taken into account in my function:
- the 'wrapscan' option is used -- 'W' is not an acceptable option to
  'search()', 'wrapscan' is meant to settle this issue.
- It can jump forward or backward -- thanks to Robert Kelly IV (aka
  feral).
- I leave the possibility to select _or_ erase the marker (/placeholder)
  we jump to -- select-mode is not always very handy.
  BTW, we can select empty markers instead of deleting them.
- It can be configured thanks to options and '<Plug>xxxx' mappings.
- It jumps to the next/prev marker even if the cursor is
  in the middle of a marker -- thanks to Robert again.
- It is compatible with the two strings you use to define your
  placeholders -- I guessed you will not revert back to my original
  variation on Stephen's bracketing system.
- It correclty works even when the marker (we jump to) is within a
  closed folder.
- There is a documentation up to date.
- It is compatible with the next version of mu-template I plan to
  release soon -- actually the version 0.29 of mu-template is compatible
  with my variation and with imaps.vim.
  But as the jumping function becomes quite complex, my version of
  bracketing.base.vim will be part of mu-template 0.30 and more.
- The screen never flashes -- there exist other variations that make the
  screen flash.
- It has been patched regarding the encoding issue -- but more tests
  should be done. I guess I will upload my last version on SF during by
  the end of this week-end.
- It is maintained and will be maintained by myself: no need to
  reinvent the wheel or having 10 person fixing the same bug or adding
  the same feature at monthes (or years) of interval.





So, if you agree with me to not waste energy, you can consider making
    http://hermitte.free.fr/vim/ressources/plugin/bracketing.base.vim
part of vim-latex ; after all Srinath already put me in the credits for
my variation on Stephen's bracketing system. ;-)

In order to have the documentation and the mapping that inserts a marker
around a visually-selected text (or the current word) and the
documentation, two other files are required. Check the tarball archive:
    http://hermitte.free.fr/vim/ressources/ lh-map-tools.vim


Have a nice week-end !

-- 
Luc Hermitte
http://hermitte.free.fr/vim/

[Vim-latex-devel] new version of plugin/imaps.vim

[Benji F. <be...@me...>]

      Sorry, I should really start a new branch, but I have not done 
that before, so I am just attaching a file.  The new syntax is

:call IMAP("tex", "foo", "b", "", "ar")

I have tested this:  typing "foo" gives

b|ar

with | indicating the cursor position.  So far so good!

      BUT it does not work if 'enc' is set to utf-8 and I use "\xab" and 
"\xbb" as place holders.  I'll post a question to the vim users' list.

      Since this is in transition, it is not a good time to add new 
packages, etc.  If you want to add them with the old syntax, please use 
Tex_IMAP() and Tex_PutTextWithMovement() for now.

					--Benji

Re: [Vim-latex-devel] Vim latex Suite is not compiling any .tex files (fwd)

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

On Thu, Dec 12, 2002 at 04:37:10PM -0800, Srinath Avadhanula wrote:
>         I have installed vim-latex on my linux machine recently.
> Everything seems to be working except the compiling part.  When i go to
> Tex Suite menu and click on compile option nothing seems to happen
> except the following line in my status bar.
> :silent! call RunLaTeX()

Hmm. For me it compiles. Yes I see this line and it looks like nothing
happen but it works. Maybe there should be any message about status of
work?

I can do from menu compilation and later see it from menu.
Mdk9, TeXLive7, gvim6.1.255 (rpm from Jeremy Brand:
http://nirvani.org/software/vim )

> Ps: The following link seem to be broken
> http://vim-latex.sourceforge.net/index.php?subject=weare

It worked for me yesterday.

Mikolaj

Re: [Vim-latex-devel] Vim latex Suite is not compiling any .tex files (fwd)

[Benji F. <be...@me...>]

> Date: Thu, 12 Dec 2002 18:55:21 -0500
> From: Raju <kk...@co...>
> To: sr...@me...
> Subject: Vim latex Suite is not compiling any .tex files
> 
> Hi Srinath,
> 
>         I have installed vim-latex on my linux machine recently.
> Everything seems to be working except the compiling part.  When i go to
> Tex Suite menu and click on compile option nothing seems to happen
> except the following line in my status bar.
> 
> :silent! call RunLaTeX()
> 
> I went through the documentation and found nothing about this message.

      Try

:call RunLaTeX()

You will probably get an error message about not understanding the 
option --src-specials .  (I do, with RH 8.0 and whatever version of 
teTeX it installs.)  In the texrc file, find the lines

if has('win32')
	let s:CompileFlags = '--src-specials'
	TexLet g:Tex_EscapeChars = ''
else
	let s:CompileFlags = '--src-specials'
	TexLet g:Tex_EscapeChars = '{}\'
endif

and change the fifth line to

	let s:CompileFlags = ''

I have just uploaded a new version with this change, and also updated 
the installation instructions in the comments at the top, but for now 
you can only get the new version from CVS.

 > Also in the documentation file latex-suite.txt  - where it mentions
 > about latex-compiler-target - the texrc tag doesn't seem to be
 > working.

      It works for me.  After installing, did you remember to do

:helptags ~/.vim/doc

> I am using Red hat linux and vim 6.1. Am I missing something here?
> please help me.

      Probably installnig the latest (beta) version of teTeX will also 
work.  You can also change the compiler rules to use pdftex, which can 
also produce dvi output and which does support the --src-specials option.

> Thanks in advance.
> 
> 
> Ps: The following link seem to be broken
> http://vim-latex.sourceforge.net/index.php?subject=weare

      SEP (Somebody Else's Problem).

> bye
> raju

Re: [Vim-latex-devel] coding standards?

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
 >
>>3. Should we try for consistent time stamps?  If so, is there a script
>>for updating them?  Or should we let CVS take care of that, and stop
>>cluttering the diff files with changed time stamps?
>>
> For now, Mikolaj and me use lastchange.vim from:
> 
> http://vim.sourceforge.net/script.php?script_id=259

      The strftime() function is not standard. :-(  On my Linux system, 
strftime('%Z') returns "EST", so I replaced

let timezone = substitute(strftime('%Z'), '\<\(\w\)\(\w*\)\>\(\W\|$\)', 
'\1', 'g')

with

let timezone = strftime('%Z')

You might want to change the posted version to

let timezone = strftime('%Z')
if has("win32")
   let timezone = substitute(...)
endif

					--Benji

[Vim-latex-devel] Vim latex Suite is not compiling any .tex files (fwd)

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

Hello,

Raju here seems to have problems with compiling on a linux machine.
Since I dont have access to a linux machine with latex, I am forwarding
to the group, hoping someone can reproduce this/fix this.

Thanks,

Srinath

---------- Forwarded message ----------
Date: Thu, 12 Dec 2002 18:55:21 -0500
From: Raju <kk...@co...>
To: sr...@me...
Subject: Vim latex Suite is not compiling any .tex files

Hi Srinath,

        I have installed vim-latex on my linux machine recently.
Everything seems to be working except the compiling part.  When i go to
Tex Suite menu and click on compile option nothing seems to happen
except the following line in my status bar.

:silent! call RunLaTeX()

I went through the documentation and found nothing about this message.
Also in the documentation file latex-suite.txt  - where it mentions
about latex-compiler-target - the texrc tag doesn't seem to be working.

I am using Red hat linux and vim 6.1. Am I missing something here?
please help me.

Thanks in advance.


Ps: The following link seem to be broken
http://vim-latex.sourceforge.net/index.php?subject=weare

bye
raju

Re: [Vim-latex-devel] vim-latex site cvs

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

On Tue, Dec 10, 2002 at 05:56:05PM -0800, Srinath Avadhanula wrote:
> I think the best method is CVS. What I normally do is log onto
> sourceforge, cd to the group's htdocs/packages directory and do a cvs
> update. That takes care of things.... Let me know if there are problems.

It doesn't work. Maybe the cause I was not properly logged in
but after "cvs update" in proper directory sf.net asked me
for your password. I can uderstand asking for my password
but yours?

I thought it can be done with cron. Just calling each 24h simple script
-----
#!/bin/sh
CVS_RSH=ssh
CVSROOT=mi...@cv...:/cvsroot/vim-latex
export CVS_RSH CVSROOT

cd /home/groups/v/vi/vim-latex/htdocs
cvs checkout
-----

But even just "cvs checkout" doesn't work properly...

Mikolaj

Re: [Vim-latex-devel] Re: [Vim-latex-cvs] vimfiles/plugin imaps.vim,1.7,1.8

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> Just a small correction..
>=20
> On Wed, 11 Dec 2002, Srinath Avadhanula wrote:
>=20
>>Also mathmacros.vim contains about 600 lines which look like this:
>>
>>-----------------------------------%<----------------------------------=
-
>>let s:pA =3D 'amenu <silent> 85 '.s:MathMenuName
>>exe s:pA2a.'mathbf{}                <plug><C-r>=3DIMAP_PutTextWithMovem=
ent("\\mathbf{=E4}=AB=BB")<cr>'
>>-----------------------------------%<----------------------------------=
-
>>
>>Changing these will also require a nontrivial amount of work.

      Your snipped example is a problem (defining a string and later=20
calling IMAP) but this is not hard.  I can do this with a suitable=20
:%s/../../gc .

>><snip>
>>
>>... I would think that the easiest way to affect the change is to
>>first do a quick
>>
>>exec "% s/\e4/<++>/g"      " for <a-umlaut>
>>exec "% s/\xab/<+/g"       " for "<<"
>>exec "% s/\xbb/+>/g"       " for ">>"
>>% s/IMAP_PutTextWithMovement/Tex_PutTextWithMovement/g
>>
>>where Tex_PutTextWithMovement() will have to be the "hacky" function
>>which knows both about the "\xab" characters and the
>>[g:b]Imap_PlaceHolder* settings. This new function will split its
>>arguments into variable arguments and then call
>>Imap_PutTextWithMovement_new.
>=20
> Tex_PutTextWithMovement will _not_ need to know about
> [g:b]Imap_PlaceHolder* settings, because it will call the
> Imap_PutTextWithMovement_new() function, not the
> Imap_PutTextWithMovement() function...
>=20
> thats all for now.

      I do not need two wrapper functions.  I'll use=20
Tex_PutTextWithMovement() but not Imap_PutTextWithMovement_new().  I'll=20
see how much I can finish tomorrow morning...

					--Benji

Re: [Vim-latex-devel] Re: [Vim-latex-cvs] vimfiles/plugin imaps.vim,1.7,1.8

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

Just a small correction..

On Wed, 11 Dec 2002, Srinath Avadhanula wrote:
> Also mathmacros.vim contains about 600 lines which look like this:
>
> -----------------------------------%<-----------------------------------
> let s:pA =3D 'amenu <silent> 85 '.s:MathMenuName
> exe s:pA2a.'mathbf{}                <plug><C-r>=3DIMAP_PutTextWithMovemen=
t("\\mathbf{=E4}=AB=BB")<cr>'
> -----------------------------------%<-----------------------------------
>
> Changing these will also require a nontrivial amount of work.
>
> <snip>
>
> ... I would think that the easiest way to affect the change is to
> first do a quick
>
> exec "% s/\e4/<++>/g"      " for <a-umlaut>
> exec "% s/\xab/<+/g"       " for "<<"
> exec "% s/\xbb/+>/g"       " for ">>"
> % s/IMAP_PutTextWithMovement/Tex_PutTextWithMovement/g
>
> where Tex_PutTextWithMovement() will have to be the "hacky" function
> which knows both about the "\xab" characters and the
> [g:b]Imap_PlaceHolder* settings. This new function will split its
> arguments into variable arguments and then call
> Imap_PutTextWithMovement_new.

Tex_PutTextWithMovement will _not_ need to know about
[g:b]Imap_PlaceHolder* settings, because it will call the
Imap_PutTextWithMovement_new() function, not the
Imap_PutTextWithMovement() function...

thats all for now.

This is the last 10 days of classes... So I will not be doing any
actual coding in the meantime.

Thanks,

Srinath

Re: [Vim-latex-devel] Re: [Vim-latex-cvs] vimfiles/plugin imaps.vim,1.7,1.8

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

I agree that the IMAP() with the variable number of arguments is the
most elegant and sound. But consider the fact that changing imaps will
also mean changing every place where
Imap_PutTextWithMovement() and IMAP() are used...

For example, consider the following code snippet from envmacros.vim:

-----------------------------------%<-----------------------------------
let s:figure =3D "\\begin{figure}[=ABhtpb=BB]\<cr>\\begin{center}\<cr>\\psf=
ig{figure=3D=ABeps file=BB}\<cr>\\end{center}\<cr>\\caption{=ABcaption text=
=BB}\<cr>\\label{fig:=ABlabel=BB}\<cr>\\end{figure}=AB=BB"

" Tex_figure: {{{
function! Tex_figure(env)
    if g:Tex_UseMenuWizard =3D=3D 1
        let flto    =3D input('Float to (htbp)? ')
        let caption =3D input('Caption? ')
        let center  =3D input('Center ([y]/n)? ')
        let label   =3D input('Label (for use with \ref)? ')
        " additional to AUC Tex since my pics are usually external files
        let pic =3D input('Name of Pic-File? ')
        if flto !=3D ''
            let flto =3D '['.flto."]\<cr>"
        else
            let flto =3D "\<cr>"
        endif
        if pic !=3D ''
            let pic =3D '\input{'.pic."}\<cr>"
        else
            let pic =3D "=E4\<cr>"
        endif
        if caption !=3D ''
            let caption =3D '\caption{'.caption."}\<cr>"
        endif
        if label !=3D ''
            let label =3D '\label{fig:'.label."}\<cr>"
        endif
        if center =3D=3D 'y'
          let centr =3D '\begin{center}' . "\<cr>"
          let centr =3D centr . pic
          let centr =3D centr . caption
          let centr =3D centr . label
          let centr =3D centr . '\end{center}' . "\<cr>"
        else
          let centr =3D pic
          let centr =3D centr . caption
          let centr =3D centr . label
        endif
        let figure =3D '\begin{'.a:env.'}'.flto
        let figure =3D figure . centr
        let figure =3D figure . '\end{'.a:env.'}'
        return IMAP_PutTextWithMovement(figure)
    else
        return IMAP_PutTextWithMovement(s:figure)
    endif
endfunction

call IMAP('EDE', "\<C-r>=3DTex_description()\<CR>", 'tex')
-----------------------------------%<-----------------------------------

Ofcourse, this code is "extracted" from envmacros.vim rather than
directly cut and pasted, but the general flow of information is as
indicated... You will see that with the variable argument syntax, these
kind of functions will take a significant amount of tweaking... I think
almost of envmacros.vim and elementmacros.vim will have to be
re-written.

Also mathmacros.vim contains about 600 lines which look like this:

-----------------------------------%<-----------------------------------
let s:pA =3D 'amenu <silent> 85 '.s:MathMenuName
exe s:pA2a.'mathbf{}                <plug><C-r>=3DIMAP_PutTextWithMovement(=
"\\mathbf{=E4}=AB=BB")<cr>'
-----------------------------------%<-----------------------------------

Changing these will also require a nontrivial amount of work.

I hope I dont come across as discouraging or anything, but the fact
remains that imaps.vim is heavily depended upon by many many things in
latex-suite. (Ofcourse, thats all the more reason to make it better).

So even if we do decide to go with the variable number of arguments
method, we should make sure that latex-suite doesnt remain broken for
too long in the change period. What about creating new functions called
IMAP_new and Imap_PutTextWithMovement_new and begin to slowly port
things across to use these. When we are satisfied that almost (or all)
or latex-suite uses these functions, then rename them to IMAP and
Imap_PutTextWithMovement and remove the originals... (the standard way
to obsolete things in software, I suppose...)

Let me know what you think.

Also, in places like mathmacros.vim, I would think that the easiest way
to affect the change is to first do a quick

exec "% s/\e4/<++>/g"      " for <a-umlaut>
exec "% s/\xab/<+/g"       " for "<<"
exec "% s/\xbb/+>/g"       " for ">>"
% s/IMAP_PutTextWithMovement/Tex_PutTextWithMovement/g

where Tex_PutTextWithMovement() will have to be the "hacky" function
which knows both about the "\xab" characters and the
[g:b]Imap_PlaceHolder* settings. This new function will split its
arguments into variable arguments and then call
Imap_PutTextWithMovement_new.

In any case, I would think that some wrapper function like
Tex_PutTextWithMovement would have been useful even if we had
Imap_PutTextWithMovement_new from the beginning.

Srinath

On Wed, 11 Dec 2002, Benji Fisher wrote:

>       OK, I had a good, long look at imaps.vim.  As currently written,
> IMAP() and IMAP_PutTextWithMovement() are global functions, and their
> input has to use the hard-coded special values.  This could be a problem
> if, for example, "<<" and ">>" are used a French quotation marks, and
> the user wants them in the replacement text.  I think the
> [bg]:Imap_PlaceHolder* should be used internally as well as in the file.

>
> > Also, <C-j> only deletes the placeholders if they are things like
> > "<++>". If there is some explanation like "<+something+>", then it wont
> > get deleted by pressing <C-j>. It will be replaced when you type some
> > printable char.
>
>       Good.
>
> > Again, just to emphasize, we are not trying to decide on a single
> > character to be used across all languages/locales etc. We are just
> > trying to decide for latex-suite... imaps.vim is kinda independent of
> > this. (At present, Imap_PutTextWithMovement tries to replace certain
> > patterns in the lhs with the user's place holder settings. This should
> > be moved over to something in latex-suite).
> [snip]
> >
> >>IMAP().  I propose changing this to
> >>
> >>    :call IMAP(ft, lhs, rhs1, ph1, rhs2, ph2, ...)
> >>
> >
> > This is a beautiful solution. But consider that not all macros in
> > latex-suite are triggered from IMAP(). Some of them do something like:
> >
> > inoremap <M-c> <C-r>=3DTex_MathCal()<CR>
> >
> > Then Tex_MathCal() does:
> >
> >     return Imap_PutTextWithMovement("\\cite{=AB=BB)=AB=BB")
> >
> > So I suppose we will also have to change Imap_PutTextWithMovement() to
> > accept variable arguments...  Although the solution above does look lik=
e
> > it could be _the_ correct solution, I have a feeling that hardcoding
> > placeholders is not such a big deal at all...
> >
> > Assumption:
> >
> > latex-suite will never need to use strings like "<+something+>" except
> > for demarcating placeholer characters.
> > This assumtion is ****important*****
> >
> > Execution:
> >
> > envmacros.vim does:
> >
> >     call Tex_IMAP('`/', '\frac{<++>}{<++>}<++>', 'tex')
> >
> > texrc does:
> >
> >     let g:Imap_PlaceHolderStart =3D "\xab"
> >     let g:Imap_PlaceHolderEnd =3D "\xbb"
> >
> > We define a new function Tex_IMAP which replaces "<+" with the user's
> > choice of g:Imap_PlaceHolderSetting and then call IMAP() with this new
> > thing. Similary Imap_PutTextWithMovement is replaced with
> > Tex_PutTextWithMovement.
> >
> > Finally, when the user press `/, he expands to \frac{|}{=AB=BB}=AB=BB w=
here | is
> > the cursor position. If he wants he could set a different value of the
> > place holder, if =AB=BB does not display nicely on his comp or if he us=
es a
> > language where =AB=BB are legitimate chars.
> >
> > NOTE: imaps.vim will no longer try to replace the "<+" chars with
> > [gb]:Imap_PlaceHolderStart. It will only use this setting in the
> > Imap_JumpFunc().
> >
> > Therefore, we could presumably have a user with an ftplugin/xml.vim
> > file where he sets:
> >
> >     let b:Imap_PlaceHolderStart =3D '?'
> >     let b:Imap_PlaceHolderEnd =3D '?'
> >
> >     call IMAP('li`', '<li>??</li>??', 'xml')
> >
> > The crazy mathematician does
> >
> >     " I have proved that the following strings occur with a probability
> >     " less than 1/(2*pi)^5*10e-12 in my files. I hope this is safe
> >     " enough.
> >     let b:Imap_PlaceHolderStart =3D '%xdf@#$'
> >     let b:Imap_PlaceHolderEnd =3D '*&#$*&'
> >
> > When he presses `/, he will get \frac{|}{%xdf@#$*&#$*&}%xdf@#$*&#$*&
> > with | ofcourse denoting cursor position.
> >
> > Does this make everyone happy?
> >
> > Please try to come up with cases where the above system might fail...
> >
> > Okay... this mail is getting out of hand...
> >
> > Srinath
>
>       I think your proposal will work, but I think it will be hard to
> maintain.  First, I do not like the idea of an extra level of
> indirection:  Tex_Foo() as a wrapper for IMAP_Foo().  Second, it is
> strange for Tex_Foo() to know about the "<+" character in LaTeX suite
> and also the [bg]:Imap_PlaceHolder* variables.
>
>       I propose changing the IMAP() and Imap_PutTextWithMovement()
> functions with versions that take a variable number of arguments, as
> discussed above.  Internally and in the file, they will use the
> [bg]:Imap_PlaceHolder* variables, with "<+" and "+>" as the defaults.
> This scheme has the following advantages (some of which your proposal
> shares):
>
> 1. no funky characters in script files
> 2. Scripts that call IMAP() and Imap_PutTextWithMovement() do not need
> to know what the special characters are.
> 3. When the user decides to change [bg]:Imap_PlaceHolder*, nothing else
> needs to be changed.
>
>       There are also some other changes I would like to make.
>
> 4. Is there any reason not to use curly-brace variables?  These are
> available in all vim 6.x (i.e., not new in 6.1 and not, as far as I can
> tell, a compilation option).
>
> 5. I would like to move the documentation from the comments to
> doc/imaps.txt .
>
> 6. other clever simplifications
>
>       If we can agree on the IMAP(ft, lhs, ...) approach, then I will do
> the work.  I should be able to get some of it done on Friday.
>
>                   --Benji
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

--=20
Srinath Avadhanula
Dec 11 4:58pm
Excellent day for drinking heavily.  Spike office water cooler.

[Vim-latex-devel] Re: [Vim-latex-cvs] vimfiles/plugin imaps.vim,1.7,1.8

[Luc H. <her...@fr...>]

* On Wed, Dec 11, 2002 at 12:00:41PM -0500, Benji Fisher <be...@me...> wrote:
> Did I snip anything that argues against the IMAP(ft, lhs, ...)
> proposal?

Nope. Considering the way it is meant to be used [1], it's fine with me.

Otherwise, once you have done with IMAPxxx(), I have some proposals to
improve the jumping functions -- actually, they are the last version of
the functions Gergely Kontra simplified (he did cut all the options he
found in my original script)
However, they require that the default closing marker/placeholder
character to be defined with nr2char(char2nr("\xbb")) -- I don't really
understand why.


[1] I wrote many smart mappings and abbreviations that insert one text
or another depending on the syntaxic context (comment, string or
character) ; so I need to write things that looks like:
    inoremap seq <C-r>=Function('seq', skeleton_with_marker/placehoders)
-- 
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] Re: [Vim-latex-cvs] vimfiles/plugin imaps.vim,1.7,1.8

[Benji F. <be...@me...>]

Luc Hermitte wrote:
> * On Sun, Dec 08, 2002 at 06:54:47PM -0800, Srinath Avadhanula <srinath=
@fastmail.fm> wrote:
>=20
>>Therefore we could conceivably have ftplugin/c.vim containing lines
>>like:
>>let b:Imap_PlaceHolderStart =3D '?'
>>let b:Imap_PlaceHolderEnd =3D '?'
>>call IMAP('for', "for (??; ??; ??) {\n??\n}??", 'c')
>=20
>=20
> Indeed, but you loose flexibility in that case. The day the new languag=
e
> C% arise, it would not be able to take advantage of the C mapping for
> 'for' as it defines a new operator : '??'=20
> ;-)

      My proposal (see other strands on this thread) also deals with this.
[snip]
>=20
> And I definitively agree, functions like IMAPS() should be independent
> of any placeholder characters. Somehow, '<+' and '+>' (as well as '=AB'=
 &
> '=BB' today) look like placeholders characters, and more important: the=
y
> look like things that some languages may use -- like for instance '=AB'
> and '=BB' in LaTeX documents written in French.
>=20
>=20
>>And I think each language choosing its own placeholders is most
>>elegant and robust...
>=20
> =20
> 100% agree.

      Did I snip anything that argues against the IMAP(ft, lhs, ...)=20
proposal?

					--Benji

Re: [Vim-latex-devel] Re: [Vim-latex-cvs] vimfiles/plugin imaps.vim,1.7,1.8

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> I am glad we are having this discussion on the way to implement this.
> Hopefully, we will be able to come up with a nice long term solution...

      I agree.

[snip]
> I think its essential to understand how placeholders are used... They
> are a bit more flexible than that. The only place where we need to
> ensure that there are no fake strings like '<f, g>' is in latex-suite
> itself. Its okay if the user has them at other places in the file. In
> this case, the user chooses a different value of g:Imap_PlaceHolder*
> variables.
>=20
> Just to be clear, the only real problem with hardcoding something like
> '<' or '<+' into latex-suite is only when latex-suite itself has some
> macros defined with strings like '<+something+>' without meaning for
> them to be placeholders.

      OK, I had a good, long look at imaps.vim.  As currently written,=20
IMAP() and IMAP_PutTextWithMovement() are global functions, and their=20
input has to use the hard-coded special values.  This could be a problem=20
if, for example, "<<" and ">>" are used a French quotation marks, and=20
the user wants them in the replacement text.  I think the=20
[bg]:Imap_PlaceHolder* should be used internally as well as in the file.

> Also, <C-j> only deletes the placeholders if they are things like
> "<++>". If there is some explanation like "<+something+>", then it wont
> get deleted by pressing <C-j>. It will be replaced when you type some
> printable char.

      Good.

> Again, just to emphasize, we are not trying to decide on a single
> character to be used across all languages/locales etc. We are just
> trying to decide for latex-suite... imaps.vim is kinda independent of
> this. (At present, Imap_PutTextWithMovement tries to replace certain
> patterns in the lhs with the user's place holder settings. This should
> be moved over to something in latex-suite).
[snip]
>=20
>>IMAP().  I propose changing this to
>>
>>	:call IMAP(ft, lhs, rhs1, ph1, rhs2, ph2, ...)
>>
>=20
> This is a beautiful solution. But consider that not all macros in
> latex-suite are triggered from IMAP(). Some of them do something like:
>=20
> inoremap <M-c> <C-r>=3DTex_MathCal()<CR>
>=20
> Then Tex_MathCal() does:
>=20
> 	return Imap_PutTextWithMovement("\\cite{=AB=BB)=AB=BB")
>=20
> So I suppose we will also have to change Imap_PutTextWithMovement() to
> accept variable arguments...  Although the solution above does look lik=
e
> it could be _the_ correct solution, I have a feeling that hardcoding
> placeholders is not such a big deal at all...
>=20
> Assumption:
>=20
> latex-suite will never need to use strings like "<+something+>" except
> for demarcating placeholer characters.
> This assumtion is ****important*****
>=20
> Execution:
>=20
> envmacros.vim does:
>=20
> 	call Tex_IMAP('`/', '\frac{<++>}{<++>}<++>', 'tex')
>=20
> texrc does:
>=20
> 	let g:Imap_PlaceHolderStart =3D "\xab"
> 	let g:Imap_PlaceHolderEnd =3D "\xbb"
>=20
> We define a new function Tex_IMAP which replaces "<+" with the user's
> choice of g:Imap_PlaceHolderSetting and then call IMAP() with this new
> thing. Similary Imap_PutTextWithMovement is replaced with
> Tex_PutTextWithMovement.
>=20
> Finally, when the user press `/, he expands to \frac{|}{=AB=BB}=AB=BB w=
here | is
> the cursor position. If he wants he could set a different value of the
> place holder, if =AB=BB does not display nicely on his comp or if he us=
es a
> language where =AB=BB are legitimate chars.
>=20
> NOTE: imaps.vim will no longer try to replace the "<+" chars with
> [gb]:Imap_PlaceHolderStart. It will only use this setting in the
> Imap_JumpFunc().
>=20
> Therefore, we could presumably have a user with an ftplugin/xml.vim
> file where he sets:
>=20
> 	let b:Imap_PlaceHolderStart =3D '?'
> 	let b:Imap_PlaceHolderEnd =3D '?'
>=20
> 	call IMAP('li`', '<li>??</li>??', 'xml')
>=20
> The crazy mathematician does
>=20
> 	" I have proved that the following strings occur with a probability
> 	" less than 1/(2*pi)^5*10e-12 in my files. I hope this is safe
> 	" enough.
> 	let b:Imap_PlaceHolderStart =3D '%xdf@#$'
> 	let b:Imap_PlaceHolderEnd =3D '*&#$*&'
>=20
> When he presses `/, he will get \frac{|}{%xdf@#$*&#$*&}%xdf@#$*&#$*&
> with | ofcourse denoting cursor position.
>=20
> Does this make everyone happy?
>=20
> Please try to come up with cases where the above system might fail...
>=20
> Okay... this mail is getting out of hand...
>=20
> Srinath

      I think your proposal will work, but I think it will be hard to=20
maintain.  First, I do not like the idea of an extra level of=20
indirection:  Tex_Foo() as a wrapper for IMAP_Foo().  Second, it is=20
strange for Tex_Foo() to know about the "<+" character in LaTeX suite=20
and also the [bg]:Imap_PlaceHolder* variables.

      I propose changing the IMAP() and Imap_PutTextWithMovement()=20
functions with versions that take a variable number of arguments, as=20
discussed above.  Internally and in the file, they will use the=20
[bg]:Imap_PlaceHolder* variables, with "<+" and "+>" as the defaults.=20
This scheme has the following advantages (some of which your proposal=20
shares):

1. no funky characters in script files
2. Scripts that call IMAP() and Imap_PutTextWithMovement() do not need=20
to know what the special characters are.
3. When the user decides to change [bg]:Imap_PlaceHolder*, nothing else=20
needs to be changed.

      There are also some other changes I would like to make.

4. Is there any reason not to use curly-brace variables?  These are=20
available in all vim 6.x (i.e., not new in 6.1 and not, as far as I can=20
tell, a compilation option).

5. I would like to move the documentation from the comments to=20
doc/imaps.txt .

6. other clever simplifications

      If we can agree on the IMAP(ft, lhs, ...) approach, then I will do=20
the work.  I should be able to get some of it done on Friday.

					--Benji

[Vim-latex-devel] location of files smartspaces and brackets

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

Hello,

Why these files are in ftplugin/tex and not in ftplugin/latex-suite?

Mikolaj

Re: [Vim-latex-devel] vim-latex site cvs

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

I think the best method is CVS. What I normally do is log onto
sourceforge, cd to the group's htdocs/packages directory and do a cvs
update. That takes care of things.... Let me know if there are problems.

Srinath

On Wed, 11 Dec 2002, Mikolaj Machowski wrote:

> Hello,
>
> How I should upload package files to vim-latex.sf.net: through CVS or
> just scp them?
>
> Mikolaj

-- 
Srinath Avadhanula
Dec 10 5:53pm
"You can't make a program without broken egos."

[Vim-latex-devel] vim-latex site cvs

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

Hello,

How I should upload package files to vim-latex.sf.net: through CVS or
just scp them?

Mikolaj