Ken Takata wrote:
> I tried `:let &t_PS="\e[200~"` to set 't_PS' without using the raw
> escape code, but it failed with E355. I didn't know that there are
> two types of 't_*'
> options: output code options and key code options. I found the following
> comment in option.c:
> /* terminal key codes are not in here */
> Therefore this seems to be an intended behavior. However I couldn't find the
> reason in the document. So, is there any reasons that `:let &` cannot be used
> for key code options?
>
> I think that it should be documented that `:let &` cannot be used for key code
> options. Please check the attached patch.
>
> P.S. I can use `:exec "set t_PS=\e[200~"` instead of `:let &`.
There is no reason not to have :let work for these termcap settings,
other than that it's done in a different way. See the call to
add_termcode() from option.c. But it needs a few checks for a valid
name and calling ttest() afterwards.
--
ARTHUR: Shut up! Will you shut up!
DENNIS: Ah, now we see the violence inherent in the system.
ARTHUR: Shut up!
DENNIS: Oh! Come and see the violence inherent in the system!
HELP! HELP! I'm being repressed!
The Quest for the Holy Grail (Monty Python)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
