From: Daniel J S. <dan...@ie...> - 2007-06-01 17:41:23
|
Ethan Merritt wrote: > On Friday 01 June 2007 10:23, Daniel J Sebald wrote: > >>>But the "raise console" mechanism doesn't operate via key bindings. >>>That's the whole point of this discussion. >> >>I thought you were proposing to make close and raise part of key bindings, not >>get rid of the actions. > > > I want to get rid of them altogether. > Petr wants to keep the "raise" action, but it is not clear what > it would be triggered by. > > >>>Switching it to use key bindings would be a major change, >> >>Why? I thought the difficult part was handling all events from all terminals at >>the same time. (And it is, I looked at the code and saw some global term-> >>pointer and that's as far as I want to look.) > > > I have tried to explain this about 4 times now. > I give up. There are all these entries in the term table #ifdef USE_MOUSE int (*waitforinput) __PROTO((void)); /* used for mouse input */ void (*put_tmptext) __PROTO((int, const char [])); /* draws temporary text; int determines where: 0=statusline, 1,2: at corners of zoom box, with \r separating text above and below the point */ void (*set_ruler) __PROTO((int, int)); /* set ruler location; x<0 switches ruler off */ void (*set_cursor) __PROTO((int, int, int)); /* set cursor style and corner of rubber band */ void (*set_clipboard) __PROTO((const char[])); /* write text into cut&paste buffer (clipboard) */ #endif why would adding something like (*reposition_window) not work? Dan |