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

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

Srinath Avadhanula wrote:
> Hey Benji,
> 
>>* Are there any files other than plugin/imaps.vim that need this sort of
>>change?
> 
> texrc also contains the '?' character in the definition of
> g:Tex_IgnoredWarnings. I tried the 'ga' command on it. It shows up as
> hex a1. I dont remember offhand what else needs changing, but this
> particular thing in the texrc is causing problems for people with chinese
> language settings.
> 
> 
>>* Are there any recent changes to 'encoding' etc. that should be undone
>>if this works?
> 
> 
> All these changes are in imaps.vim. The functions
> IMAP_PutTextWithMovement() and the IMAP_JumpFunc() will both have to be
> reverted back to the old versions. The new versions although they did
> work created big screen glitches as I noted... It will be really nice if
> we could have a way to solve this without having to change encoding...

      Thanks.  That will help.  I guess I can get the complete story 
either from the CVS viewer at SourceForge or from my saved CVS-generated 
e-mails.

> But wait. I just thought about this: Won't all of the macros have to be
> changed to use the "\xab" and "\xbb" characters as well. As of now, we
> have things like:
> 
> call s:Tex_SpecialMacros('', 'EnvCommands.&Slides.', '&onlyslides{}', '\onlyslides{??}??', 0)
> 
> in envmacros.vim.
> 
> Will it be possible to somehow change things so that in the
> initialization of latex-suite, we change the encoding once while
> sourcing envmacros.vim and such files and from then on in the functions
> themselves use the "\xab" character? Will this make it possible to keep
> envmacros.vim unchanged? the ? characters are used all over the place.
> In envmacros.vim, someplaces in the packages/* files, and other places.
> So some way of being able to work with all of them unchanged is ideal.

      I disagree.  If you saw my 'encoding' thread on the vim users' 
list, you know that I have had trouble while editing these files.  I 
worry that I (or CVS or ...) will munge some of these characters one of 
these days.  I think it is safest for vim script files to contain 
nothing but safe, universally understood, ASCII characters.  I think we 
should change all of our files now, to avoid trouble in the future.

					--Benji