Dear Kevin,
what you describe is currently not possible, i.e., you cannot remove the
"<CR>" after "\begin{someenv}" directly by some configuration variable.
However, you can define
let g:Tex_Env_someenv =
"\\begin{someenv}[<+optional+>]{<+mandatory+>}\<CR><++>\<CR>\\end{someenv}"
in your `.vim/ftplugin/tex.vim` to obtain the desired expansion (see
also
http://vim-latex.sourceforge.net/documentation/latex-suite.html#Tex_Env_name).
Best regards,
Gerd
On 2018-04-01 04:29, Kevin wrote:
> Hi,
> In the current version, the environment mapping is like below:
>
> \begin{someenv}
> <++>
> \end{someenv}
>
> but in many cases, the environments have arguments, so I have to press `<ESC>kA` to add those arguments, like
>
> \begin{someenv}[<optional>]{<mandatory >}
> <++>
> \end{someenv}
>
> it's very annoying. This problem will be solved by changing the mapping to
>
> \begin{someenv}<++>
> \end{someenv}
>
> At this time, if the environment doesn't have arguments, I can simply press `<CR>`, if it does, I can directly type them.
>
> I have read the help document but cannot find a way to change it. So is there a method to change the default mapping? If not, hope you make it possible, thanks!
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
|
