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

Re: [Vim-latex-devel] German quotation marks and `

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

Sorry about that. The problem is due to `g being mapped to \gamma. I
will fix this now.

[To Vim devel]
More unprotected quote maps!!! Ouch! As of now, `g doesnt get expanded
in the following scenarios:

``g
\`g

Now it looks like it should also be protected in

"`g

As of now, the way to protect against these expansions is to define:

call IMAP('`g', '\gamma', 'tex')
" The following fake maps are just to make `g not expand when preceded
" \ or `.
call IMAP('``g', '``g', 'tex')
call IMAP('\`g', '\`g', 'tex')

and so on and so forth... Is this really the correct way to attack this
problem? Or can someone think of something more elegant?

Thanks,

Srinath

On Tue, 14 Jan 2003, Bernhard Walle wrote:

> Hello,
>
> in german.sty the correct quotation marks are "` and "' (instead of ``
> and ''). But if I type "`gut"' for example it's expanded to
> "\gammaut. Is there any solution for this?
>
> Regards,
> Bernhard
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: Take your first step towards giving
> your online business a competitive advantage. Test-drive a Thawte SSL
> certificate - our easy online guide will show you how. Click here to get
> started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

Re: [Vim-latex-devel] Vim-LaTeX problem with "

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

Mikolaj Machowski wrote:
> On Tue, Jan 14, 2003 at 10:35:53AM -0500, Benji Fisher wrote:
> 
>>which language is being used.  If anyone is interested in helping with 
>>this, the main thing I do not know is how to guess what language is in use.
> 
> 
> Checking for "v:lang" and/or "v:ctype" value?
> 
> Mikolaj

      I do not think this helps someone who writes in two different 
languages.

Alexander Schatten wrote:
[snip]
 > when I write german texts, I use the
 > german package:
 >
 > \usepackage{german}
 >
 > I think it has to do with german Umlauts, as well as hyphenation and
 > that stuff...
 > however: I guess, every german document should have this package loaded.
 >
 > btw: the german quotations are like this. "`a text"'

      That sounds more like it.  Do the package scripts already extract 
this information?

					--Benji

[Vim-latex-devel] German quotation marks and `

[Bernhard W. <ber...@gm...>]

Hello,

in german.sty the correct quotation marks are "` and "' (instead of ``
and ''). But if I type "`gut"' for example it's expanded to 
"\gammaut. Is there any solution for this?

Regards,
Bernhard

Re: [Vim-latex-devel] Vim-LaTeX problem with "

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

On Tue, Jan 14, 2003 at 10:35:53AM -0500, Benji Fisher wrote:
> which language is being used.  If anyone is interested in helping with 
> this, the main thing I do not know is how to guess what language is in use.

Checking for "v:lang" and/or "v:ctype" value?

Mikolaj

Re: [Vim-latex-devel] Vim-LaTeX problem with "

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

Alexander Schatten wrote:
> Benji Fisher wrote:
> 
>>
>>      If you have to write English and German in the same file, this 
>> seems like the only reasonable solution.  If each file is either 
>> English or German, it might be worth having the TexQuote() function 
> 
> well, yes. this is usually the case-
> unfortunately I do not really understand what you meant by the 
> TeXQuote() function...

      That is the function that gets invoked when you type " .  But you 
do not have to worry about that:  the rest of us can handle the 
implementation.  What I need to know is how to tell whether to use 
English or German quotes.  Is there a \documentclass option or a 
\usepackage line that you use to tell TeX that you are writing in 
German?  I think there must be something like this, because TeX uses 
different hyphenation patterns for different languages.

					--Benji Fisher

Re: [Vim-latex-devel] Vim-LaTeX problem with "

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

Alexander Schatten wrote:
> Benji Fisher wrote:
> 
>> Alexander Schatten wrote:
>>
>>
>> :let Tex_SmartKeyQuote = 0
>>
>> You may have to do this in the texrc file; I am not sure if it will 
>> work on the fly.)
>>
>> HTH                    --Benji Fisher
>>
> thank you very much for this fast and concise answer. in fact it solved 
> the problem immediately. the problem is, that I have to write english as 
> well as german texts, so it seems to be a little uncomfortable, but 
> however, I switched this feature out at all.

      If you have to write English and German in the same file, this 
seems like the only reasonable solution.  If each file is either English 
or German, it might be worth having the TexQuote() function figure out 
which language is being used.  If anyone is interested in helping with 
this, the main thing I do not know is how to guess what language is in use.

					--Benji Fisher

Re: [Vim-latex-devel] Vim-LaTeX problem with "

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

Alexander Schatten wrote:
> First of all, thank you very much for the vim-latex package.
> 
> unfortunately I have a small, but awkward problem. When you press the " 
> key, vi replaces it with `` at the beginning or '' at the end of the 
> quotation.
> 
> this is nice, when you do edit english texts, unfortunately, this is no 
> such good idea, when I edit german texts. because in german it should 
> start with "`.
> 
> even worse, I do not see a possibility to get the " to do it manually, 
> because it is always immediately replaced by ``.
> 
> 
> could you give me a hint how to solve this problem?

      This is a documentation problem.  Have a look at the file

ftplugin/latex-suite/texrc .

First, see the installation instructions in the comments at the top. 
Then, search for /Quote/ and you will get to the lines

===
" Pressing " (english double quote) will insert `` or '' by making an
" intelligent guess about whether we intended to open or close a quote.
TexLet g:Tex_SmartKeyQuote = 1

" Users of other languages might want to change the quote characters to suit
" their locale.
TexLet g:Tex_SmartQuoteOpen = "``"
TexLet g:Tex_SmartQuoteClose = "''"
===

Just change the last two lines.  These changes will not take effect 
until you restart vim.  You can change the variables on the fly:

:let Tex_SmartQuoteOpen = '"`'

should work (untested).  (I hope the closing character is something like 
'", which you would have to enter as "'\"", and not "', because I think 
the system will be buggy if the open and close quotes start with the 
same character.  In this case, you can turn it off completely with

:let Tex_SmartKeyQuote = 0

You may have to do this in the texrc file; I am not sure if it will work 
on the fly.)

HTH					--Benji Fisher

[Vim-latex-devel] Vim-LaTeX problem with "

[Alexander S. <ale...@sc...>]

First of all, thank you very much for the vim-latex package.

unfortunately I have a small, but awkward problem. When you press the " 
key, vi replaces it with `` at the beginning or '' at the end of the 
quotation.

this is nice, when you do edit english texts, unfortunately, this is no 
such good idea, when I edit german texts. because in german it should 
start with "`.

even worse, I do not see a possibility to get the " to do it manually, 
because it is always immediately replaced by ``.


could you give me a hint how to solve this problem?


thank you!

-- 
mfg / with best regards

Alexander Schatten

=====================================================================
Dipl.Ing. Alexander Schatten
Email: ale...@sc...          URL: http://www.schatten.info
Address: Gallitzinstr.7-13/7/7                    1160 Vienna/Austria
Tel: 0699/10 862 175                             FAX: 0699/40 862 175    
=====================================================================
Dusk is dawn is day // Where did it go?

Re: [Vim-latex-devel] Problem with VIM-LATEX

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

On Sat, 11 Jan 2003, Mikolaj Machowski wrote:

> > This error occurres unter Win98 with Miktex 2.2 and under Linux
> > (Debian 3.0) with TeTeX. Both times i used gvim 6.1.  Is there a fix
> > for the problem?
>
> Sorry. Now there is (in CVS).
>
I've uploaded the fixed version on to the web-site.

Also, developers: please see the present makefile in vimfiles/ for how
to release stuff... With such important bug-fixes, its important to make
a release asap, in case I am unavailable for it.

Thanks,

Srinath

Re: [Vim-latex-devel] Problem with VIM-LATEX

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

On Sat, Jan 11, 2003 at 05:56:39PM +0100, Andre Sell wrote:
> When i try to do "Tex-Environments -> Tables -> table" i get the
> messages:
> > Error detected while processing function Tex_DoEnvironment..Tex_PutEnvironment:
> > line    1:
> >E15: Invalid expression: s:isvisual == "yes"
> In file ~/.vim/ftplugin/latex-suite/envmacros.vim on line 570 s:isvisual
> seems to be not defined.
> This error occurres unter Win98 with Miktex 2.2 and under Linux (Debian 3.0)
> with TeTeX. Both times i used gvim 6.1.
> Is there a fix for the problem?

Sorry. Now there is (in CVS).

Mikolaj

[Vim-latex-devel] Problem with VIM-LATEX

[Andre S. <and...@gm...>]

Hello.
I just downloaded the lastest release of vim-latex and have a problem,
when i try to insert TeX-Environments.

When i try to do "Tex-Environments -> Tables -> table" i get the
messages:

> Error detected while processing function Tex_DoEnvironment..Tex_PutEnvironment:
> line    1:
>E15: Invalid expression: s:isvisual == "yes"

In file ~/.vim/ftplugin/latex-suite/envmacros.vim on line 570 s:isvisual
seems to be not defined.

This error occurres unter Win98 with Miktex 2.2 and under Linux (Debian 3.0)
with TeTeX. Both times i used gvim 6.1.

Is there a fix for the problem?

Tank you.
Best regards,
André Sell

Re: [Vim-latex-devel] Now, you tell me!

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

Wow! So all along, we could have used a :scriptencoding latin1 and
gotten away with it... Interesting! Ho Well, I think its still worth
doing what we did...

Srinath

PS: This email was malformed. Your mail client said that the text was
'quoted-printable' encoded, but it wasn't... I must admit pine is really
shabby at handling this error, but you might want to look at it anyway..

On Fri, 10 Jan 2003, Benji Fisher wrote:

>       I was browsing the vim docs, and I ran across the :scriptencoding
> command.  Try sourcing a file with the lines
>
> scriptencoding latin1
> let fooChar =3D "=AB"
> let barChar =3D "\xab"
>
> and then try
>
> :echo fooChar barChar
>
> I suppose it will look pretty boring if you have a version with
> -multi_byte but if you have m-b support and 'encoding' is set to
> "utf-8", then fooChar looks good and barChar is an invalid byte.
>
>       There will still be problems if the user wants "=AB" and "=BB"
> characters in the file or (less likely, I think) uses an encoding that
> cannot translate these characters, but I think this is the right way to
> include funky characters.  When we write more of doc/imaps.txt , I think
> we sho

Re: [Vim-latex-devel] CVS keyword expansion

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

Hmm... It looks like my last "experiment" might have been flawed...
Since it was very fishy that a file was being exported with CRLF EOLs
even on a unix machine, I tried again:

dos> date > dosfile3
dos> unix2dos dosfile3
dos> cvs add dosfile3

I checked to see if the file had the '-kb' sticky tag. It didnt.

unix> cvs update
unix> vim dosfile3

And now dosfile3 doesn't have the '^M' characters and its also ff=unix.

So I don't know what went wrong last time...

In any case, setting -kb for the files might actually be a bad idea
because in some situations, a cvs client might create dos style files on
a unix clients... Bad Idea!

So what I propose is the following:

Unsetting the -kb flag from all our files.

This will have the side-effect that cvs clients on windows machines will
create dos style EOLs. Therefore its not possible to create packages via
a DOS machine... But as I mentioned previously, this shouldn't be
a problem because I create releases from my linux account on sf.net.
Also, it will enable using keyword substitution...

Also, as far as verifying that the files are all in unix format at
release time, Ulrich Spoerlin suggested I use:

file `find . -print` | grep CRLF | sed s/:.*// | xargs dos2unix

I'll add this to our makefile just to make doubly sure...

Srinath

PS: The tip about 'ffs' was very helpful! Turns out there that the
system vimrc on sf.net sets lots of very nondefault values, one of those
being 'ffs=unix' with the comment "I want to see those ^M characters
when I am editing dos files"... Go figure.

[Vim-latex-devel] Now, you tell me!

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

      I was browsing the vim docs, and I ran across the :scriptencoding=20
command.  Try sourcing a file with the lines

scriptencoding latin1
let fooChar =3D "=AB"
let barChar =3D "\xab"

and then try

:echo fooChar barChar

I suppose it will look pretty boring if you have a version with=20
-multi_byte but if you have m-b support and 'encoding' is set to=20
"utf-8", then fooChar looks good and barChar is an invalid byte.

      There will still be problems if the user wants "=AB" and "=BB"=20
characters in the file or (less likely, I think) uses an encoding that=20
cannot translate these characters, but I think this is the right way to=20
include funky characters.  When we write more of doc/imaps.txt , I think=20
we should recommend this approach.

					--Benji

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

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

Hey Charlie,

On Fri, 10 Jan 2003, Charles Boncelet wrote:

> Even weirder in the my version (a few days old), type "I am here".  The
> double quotes get changed to two left quotes, which then trigger the `I
> substitution and you get `\int...
>
> Also fix for `I (which gives int).  The others (lines 90-116 in my
> main.vim) might occur, but are less likely.  If the fix is easy, fix for
> them also.
>
> Some bugs:  When I type `i or `j or `o (letters not in greek) I get an
> error: Undefined variable s:greek_i etc. instead of `i etc.
>

All these problems have been taken care of in the latest version... I
wonder if I have made a release... Yes... I see the latest files on the
download page of latex-suite have these fixes...


> The issue of what to use as a Tex_Leader is interesting.  Some years
> ago, I did my own mappings (when vim was much more primative) with ",".
> The idea is that in English a comma is almost always followed by
> whitespace.  The same holds true for semi-colon ";".  Both make good
> leaders.  A period "." can also be used (as in nroff)

Yes... When I first started this project, I should have thought a bit
more about what leader character to use. I admit, in retrospect, ';'
would have made a most excellent choice. I think I have _never_ used a ;
in all of my latex writing and its so nicely placed...

Having said that, its still possible that some people might like to
customize their leader settings to be '`' because its a somewhat
commonly used vim <leader>. In that case, they would have had problems.
The present solution allows people to have Tex_Leader as '`' and still
continue using latex-suite smoothly.

> A left quote is a little more problematic.  It is used for diacritical
> marks (as you note) and for double left quotes in Latex.  Many
> experienced latex authors automatically type `` at the beginning of a
> quote.
>
Yes... Well, take some consolation in the fact that for the first couple
of days of the project, I used '\' as the default!!! Imagine the havoc
that caused. :)

> If this were a brand new project, I'd suggest using one of "," or ";"
> for latex-suite macros and leaving the other one for user defined
> macros.
>
Well, unfortunately, it really isn't a brand new project... And since I
have solved the problem with using Tex_Leader = '`', I will let it
remain as it is.. (at least till someone reports an even more serious
problem).

Srinath

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

[Charles B. <bon...@ma...>]

On Fri, 2003-01-10 at 00:56, Srinath Avadhanula wrote:
> On Thu, 9 Jan 2003, Srinath Avadhanula wrote:
> > > One bug: The documentation says that "SPG" gives a \paragraph,
> > > but "SPR" does.
> > >
> > I'll fix this now...
> >
> I actually ended up changing the map for \paragraph to SPG instead of
> fixing the documentation... SPG seems a more logical choice.

Either one is reasonable.

> 
> > > call IMAP (g:Tex_Leader.'M', "\\sum_{<++>}^{<++>}<++>", 'tex')
> > >
> > This is an excellent suggestion thanks. I've added this, but the problem
> > with this is that because g:Tex_Leader is "`" by default, therefore at
> > the beginning of a quote, you press M, you'll get \sum.. which will
> 
> I have taken care of this problem. In the latest version `M expands to
> \sum except when it is preceded by ` or \ (so that we can type ``Moo and
> \`M (for diacritics)).
> 

Even weirder in the my version (a few days old), type "I am here".  The
double quotes get changed to two left quotes, which then trigger the `I
substitution and you get `\int...

Also fix for `I (which gives int).  The others (lines 90-116 in my
main.vim) might occur, but are less likely.  If the fix is easy, fix for
them also.

The issue of what to use as a Tex_Leader is interesting.  Some years
ago, I did my own mappings (when vim was much more primative) with ",". 
The idea is that in English a comma is almost always followed by
whitespace.  The same holds true for semi-colon ";".  Both make good
leaders.  A period "." can also be used (as in nroff)

The recognition of both "," and ";" can be improved if you require
whitespace (or first character of new line) before expanding the macro.

A left quote is a little more problematic.  It is used for diacritical
marks (as you note) and for double left quotes in Latex.  Many
experienced latex authors automatically type `` at the beginning of a
quote.

If this were a brand new project, I'd suggest using one of "," or ";"
for latex-suite macros and leaving the other one for user defined
macros.

Some bugs:  When I type `i or `j or `o (letters not in greek) I get an
error: Undefined variable s:greek_i etc. instead of `i etc.

	Charlie Boncelet

 
> Thanks,
> 
> Srinath
-- 
Charles Boncelet <bon...@ec...>
University of Delaware

Re: [Vim-latex-devel] CVS keyword expansion

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

Srinath Avadhanula wrote:
> On Thu, 9 Jan 2003, Benji Fisher wrote:
> 
> Okay. I just checked this. I did the following:
> 
> Then on my sourceforge account
> 
> nix > cvs update
> nix > vim dosfile2
> 
> Guess what? I see the annoying ^M character at the EOL! But ff? gives me
> 'unix'. Setting ff=dos and saving doesn't help. However, doing
> 'dos2unix dosfile2' does help in removing the ^M character and ff is
> also correctly identified as unix...

      Try this:

nix > vim dosfile2
:set ffs?

If the 'fileformats' option does not include "dos" then it explains the 
behavior you got.  Try (still in vim)

:set ffs+=dos
:e!

and I think it will set 'ff' to "dos".

> So well, I guess we are somewhat screwed if the file being commited is
> in dos format. I am wondering why this didn't happen already...

      Maybe the CVS CR/LF conversion did some good.  I guess I am not 
clear on how it caused problems in the first place...

> But this problem is not really related to -kb at all... You'll notice
> that I didn't use -kb anywhere... If I do
> 
> nix > cvs admin -kb dosfile2
> nix > cvs update dosfile2
> 
> Even then, it doesn't help...
> 
> So whats the conclusion from all this? I really don't know...
> 
> 
>>      Can you add something to the makefile that will check for and
>>correct line endings?  It seems to be safe to run dos2unix on a file
>>already in unix format; with the -k flag, it keeps the time stamp.
> 
> 
> Yes... I'll do this. But what about files in which there are spurious ^M
> characters?

      That counts as a "funky character" and should be removed anyway. 
Before changing the makefile, you should check out a fresh copy and make 
sure we do not have any ^M characters lurking.  Can grep handle that?

Mikolaj Machowski wrote:
 >
 > It seems the only solution is to add in modeline ff=unix in all files.

      I think this is worth doing.  Even if we adopt another solution 
(like using dos2unix in the makefile) this could be a second line of 
defense.  By itself, it is not quite enough:  if I create a file with 
DOS-style line endings, add the modeline, save it, and commit it, then 
it still has DOS-style line endings.  Vim only changes the line endings 
when the file is loaded with that modeline.

					--Benji

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

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

Srinath Avadhanula wrote:
>>>call IMAP (g:Tex_Leader.'M', "\\sum_{<++>}^{<++>}<++>", 'tex')
>>>
>>
>>This is an excellent suggestion thanks. I've added this, but the problem
>>with this is that because g:Tex_Leader is "`" by default, therefore at
>>the beginning of a quote, you press M, you'll get \sum.. which will
> 
> 
> I have taken care of this problem. In the latest version `M expands to
> \sum except when it is preceded by ` or \ (so that we can type ``Moo and
> \`M (for diacritics)).

      I would prefer "S" for "sun" instead of "M".  Is this already taken?

					--Benji

Re: [Vim-latex-devel] CVS keyword expansion

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

On Thu, Jan 09, 2003 at 04:56:42PM -0800, Srinath Avadhanula wrote:
> Guess what? I see the annoying ^M character at the EOL! But ff? gives me
> 'unix'. Setting ff=dos and saving doesn't help. However, doing
> 'dos2unix dosfile2' does help in removing the ^M character and ff is
> also correctly identified as unix...
> So well, I guess we are somewhat screwed if the file being commited is
> in dos format. I am wondering why this didn't happen already...

It seems the only solution is to add in modeline ff=unix in all files.

Mikolaj

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

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

On Thu, 9 Jan 2003, Srinath Avadhanula wrote:
> > One bug: The documentation says that "SPG" gives a \paragraph,
> > but "SPR" does.
> >
> I'll fix this now...
>
I actually ended up changing the map for \paragraph to SPG instead of
fixing the documentation... SPG seems a more logical choice.

> > call IMAP (g:Tex_Leader.'M', "\\sum_{<++>}^{<++>}<++>", 'tex')
> >
> This is an excellent suggestion thanks. I've added this, but the problem
> with this is that because g:Tex_Leader is "`" by default, therefore at
> the beginning of a quote, you press M, you'll get \sum.. which will

I have taken care of this problem. In the latest version `M expands to
\sum except when it is preceded by ` or \ (so that we can type ``Moo and
\`M (for diacritics)).

Thanks,

Srinath

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

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

Hello,

On Thu, 9 Jan 2003, Charles Boncelet wrote:

> One bug: The documentation says that "SPG" gives a \paragraph,
> but "SPR" does.
>
I'll fix this now...

> 1) add the following line to main.vim to give \sum (which I
> use a lot and a macro can save lots of typing)
>
> call IMAP (g:Tex_Leader.'M', "\\sum_{<++>}^{<++>}<++>", 'tex')
>
> (an "M" is a rotated sigma).
>
This is an excellent suggestion thanks. I've added this, but the problem
with this is that because g:Tex_Leader is "`" by default, therefore at
the beginning of a quote, you press M, you'll get \sum.. which will
become annoying. I suppose the way to get around that is to use
g:Tex_Leader = ';', which doesn't occur much in latex... (does it?)

> 2) add the reformat paragraph macro from auctex.vim (lines 604-625).
>
Will do...

> One comment: The output of \ll is confusing.  It took me awhile to
> figure out how to continue editing without exiting the editor. I would
> prefer to continue to see my file in a window (\ll was opening up my
> .bbl file which it thought was in error--and it wasn't). This problem
> may be unavoidable due to complexities within vim, but it is confusing
> when first presented.
>
Are you sure there was no actual error in the .bbl file? The compiler
plugin has been worked upon a fair deal to get it working right... Could
you provide a bug report about what was the faulty error?

Thanks,

Srinath

Re: [Vim-latex-devel] CVS keyword expansion

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

On Thu, 9 Jan 2003, Benji Fisher wrote:

>
>       I think the only likely problem is if one of us uses DOS-style
> line endings, and they get uploaded to the CVS repository.  How do we
> test this?  Maybe we should each do a "cvs add" and then "cvs commit" on
> the test project, then someone using Linux (like me) can download the
> files and check with ":set ff?".

Okay. I just checked this. I did the following:

(On my dos machine):

dos > date > dosfile2
dos > unix2dos dosfile2
dos > cvs add dosfile2
dos > cvs ci -m 'was ff=dos when created' dosfile2

Then on my sourceforge account

nix > cvs update
nix > vim dosfile2

Guess what? I see the annoying ^M character at the EOL! But ff? gives me
'unix'. Setting ff=dos and saving doesn't help. However, doing
'dos2unix dosfile2' does help in removing the ^M character and ff is
also correctly identified as unix...

So well, I guess we are somewhat screwed if the file being commited is
in dos format. I am wondering why this didn't happen already...

But this problem is not really related to -kb at all... You'll notice
that I didn't use -kb anywhere... If I do

nix > cvs admin -kb dosfile2
nix > cvs update dosfile2

Even then, it doesn't help...

So whats the conclusion from all this? I really don't know...

>       Can you add something to the makefile that will check for and
> correct line endings?  It seems to be safe to run dos2unix on a file
> already in unix format; with the -k flag, it keeps the time stamp.

Yes... I'll do this. But what about files in which there are spurious ^M
characters?

Srinath

Re: [Vim-latex-devel] CVS keyword expansion

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

Srinath Avadhanula wrote:
> Hello,
> 
> It looks like we need to rethink how to set the keyword expanion mode of
> our files... What would be ideal for us is if CVS is able to inhibit
> CRLF conversions while also permitting expansion of stuff such as
> $Header$. Unfortunately, it looks like CVS is a bit confused about line
> endings and keyword substitutions. The only way of inhibiting EOL conversions
> is to tell CVS that the file is binary, which unfortunately throws away
> keyword subsitution.
> 
> The following thread in google groups sounded promising, but my cvs
> client doesn't seem to support the CVS_MODE variable which is proposed
> there. (The online manual at cvshome.org also doesn't mention CVS_MODE).
> It also mentions that jCVS is able to do what we want, but I do not have
> time right now to try it.
> 
> http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=fa.ion3edv.6g8l9e%40ifi.uio.no&rnum=1&prev=/groups%3Fq%3Dline%2Bconversion%2Bgroup:fa.info-cvs%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3Dfa.ion3edv.6g8l9e%2540ifi.uio.no%26rnum%3D1
> 
> The only way to have keyword expansion is therefore to remove the -kb
> flag from files. So the question is:
> 
> Are there platforms for which the cvs client performs a CRLF conversion
> which vim doesn't like? Is one of us developers on such a platform? If
> so, should we bother unsetting the -kb flag to allow keyword
> subsitution? Or should we just forget about keyword substitution?

      I think the only likely problem is if one of us uses DOS-style 
line endings, and they get uploaded to the CVS repository.  How do we 
test this?  Maybe we should each do a "cvs add" and then "cvs commit" on 
the test project, then someone using Linux (like me) can download the 
files and check with ":set ff?".

      I have always thought that -kb was a bit of an abuse.  OTOH, I am 
not sure that keyword substitution gives us anything very useful.

> Note, that since I make releases via my sourceforge shell account, the
> .zip and .tar.gz packages always have UNIX style EOLs in the files,
> which should be fine with vim on any platform...

      Can you add something to the makefile that will check for and 
correct line endings?  It seems to be safe to run dos2unix on a file 
already in unix format; with the -k flag, it keeps the time stamp.

					--Benji

Re: [Vim-latex-devel] some questions about main.vim

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

Srinath Avadhanula wrote:
>>Why is silent used only in has('gui')?
>>
> 
> When I try to execute a <silent> command like ":silent !latex %" or such
> from within a console vim, my vim display gets overwritten by the
> display of the commanad. (I tested this using the console vim which
> ships with cygwin) I then have to press <C-l> to get back... A newbie
> might get into a total panic if something like that happens... With gvim
> ofcourse, a seperate window is spawned... Doesn't this problem occur
> with console vim's in *nix?

      I am not sure about the console, but in an xterm I get a "Hit 
ENTER" prompt and then vim comes back to me.

>>2. Does the comment about compiler/tex.vim mean that ":compiler tex" was
>>tried and did not work?
> 
> 
> I haven't tried this in a long while... Let me see... No ":compiler tex"
> doesn't seem to work. I haven't looked into this in a while. Maybe our
> compiler/tex.vim needs to set some global variable so vim's compiler
> doesn't overwrite ours... It looks like ":compiler tex" does source our
> compiler/tex.vim but also vim's compiler/tex.vim...

      Unbder :help :compiler,

What this command actually does is:
- delete the "current_compiler" variable
- execute ":runtime! compiler/{name}.vim"

First non-comment lines of the standard compiler/tex.vim :

if exists("current_compiler")
	finish
endif

It then sets g:current_compiler to "latex" or whatever is specified by 
b:tex_flavor or g:tex_flavor .

					--Benji

[Vim-latex-devel] CVS keyword expansion

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

Hello,

It looks like we need to rethink how to set the keyword expanion mode of
our files... What would be ideal for us is if CVS is able to inhibit
CRLF conversions while also permitting expansion of stuff such as
$Header$. Unfortunately, it looks like CVS is a bit confused about line
endings and keyword substitutions. The only way of inhibiting EOL conversions
is to tell CVS that the file is binary, which unfortunately throws away
keyword subsitution.

The following thread in google groups sounded promising, but my cvs
client doesn't seem to support the CVS_MODE variable which is proposed
there. (The online manual at cvshome.org also doesn't mention CVS_MODE).
It also mentions that jCVS is able to do what we want, but I do not have
time right now to try it.

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=fa.ion3edv.6g8l9e%40ifi.uio.no&rnum=1&prev=/groups%3Fq%3Dline%2Bconversion%2Bgroup:fa.info-cvs%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3Dfa.ion3edv.6g8l9e%2540ifi.uio.no%26rnum%3D1

The only way to have keyword expansion is therefore to remove the -kb
flag from files. So the question is:

Are there platforms for which the cvs client performs a CRLF conversion
which vim doesn't like? Is one of us developers on such a platform? If
so, should we bother unsetting the -kb flag to allow keyword
subsitution? Or should we just forget about keyword substitution?

Note, that since I make releases via my sourceforge shell account, the
.zip and .tar.gz packages always have UNIX style EOLs in the files,
which should be fine with vim on any platform...

Srinath