On Jan 2, 4:32 pm, Tony Mechelynck <[email protected]>
wrote:
> On 02/01/09 23:05, zhengquan wrote:
>
> > Thanks Tony,
> > the output of the two verbose commands shows no mappings.
>
> You did issue them with your latex file current didn't you?
>
> What are you hoping that this Alt-I should do?

yes I did issue the commands with my latex file, and the output show
no mappings.
I am hoping that in  an itemize environment, when I type alt-i in the
environment, it  will automatically insert a \item

\begin
{itemize}
\item   (\item is inserted as the result of alt-
i)

\end{itemize}

>
> > It is quite
> > possible that the mlterm does not pass the alt-i combo to vim... I am
> > wondering how to make alt-i passable to vim in mlterm.
>
> As I said, if I were you I'd use a different key. You can even map F7
> (or anything that Vim does see) to Alt-I and from then on when you hit
> F7 Vim will interpret it as Alt-I.
I know this a workaround but I would like to pass alt-i to vim in
mlterm. what I am doing now is that I am switching to some tasks to
xterm. but the support for multibyte characters of xterm is feeble.

>
> Note that Vim cannot distinguish Alt-i from é (small-e-acute), or Alt-I
> (Alt-Shift-i) from É (capital-E-acute). If you can type é (e.g. as e2 in
> pinyin), Vim will see it as synonymous to Alt-i. This also means that
this is confusing me because if I type alt-i in under mlterm with my
latex file, it will be a small-e-acute.
but if I use xterm, it will insert a correct \item. So this makes me
feel that the problem is with mlterm. It seems like an off topic issue
now...

Thank you for your help.

Regards,
Zhang
> you should not map Alt-i in Insert mode if you want to be able to type
> e-acute into your text.
>
>
>
> > Regards,
> > Zhang
>
> Best regards,
> Tony.
> --
> Old soldiers never die.  Young ones do.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to