[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