Micah Cowan wrote: > > > >> Sorry for the repost; but I realized I should've drawn more attention > to > >> the message with the patch in it, both so other lurkers know the threa> d > >> now includes a proposed patch, and so that we know what message to go > >> back to if we want to refer to the code we're discussing. > >> > >> I have made a slight adjustment to the patch, swapping the order of > >> STRICMP and term_is_xterm within vim_uses_xterm_mouse(). I was using > >> vim_is_xterm() instead of term_is_xterm at first, but afterwards > >> replaced it for efficiency, but left the order as it was. > > > > Looks OK to me. > > Terrific! Does that mean it'll go in? :)
Probably, but not right now. > > If I understood your other message correctly then using "xterm2" for > > 'ttymouse' would not work for screen. > > Well... manually setting it to "xterm2" will work fine (assuming screen > is running under a supporting version of xterm): I get the full dragging > effect, etc. But screen doesn't do t_RV, and I don't know how else you'd > determine support for "xterm2", so there doesn't seem to be a safe way > to set ttymouse to it automatically, for screen. > > Towards a better solution: how straightforward do you think it'll be to > talk the ncurses guys into adding support for some of screen's > extensions? AFAIK, the only one I care about is the xterm mouse support; > another interesting one is a boolean "supports ansi > setforeground/setbackground codes"; but I usually infer this (if > necessary) from the presence of setaf/setbf (not a given, but...). I think you need to talk to more people than ncurses for changing the termcap/terminfo entries. But it's a good start. - Bram -- >From "know your smileys": :-F Bucktoothed vampire with one tooth missing /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
