head 1.1; branch 1.1.1; access; symbols netbsd-11-0-RC5:1.1.1.1 netbsd-11-0-RC4:1.1.1.1 netbsd-11-0-RC3:1.1.1.1 netbsd-11-0-RC2:1.1.1.1 netbsd-11-0-RC1:1.1.1.1 perseant-exfatfs-base-20250801:1.1.1.1 netbsd-11:1.1.1.1.0.44 netbsd-11-base:1.1.1.1 netbsd-10-1-RELEASE:1.1.1.1 perseant-exfatfs-base-20240630:1.1.1.1 perseant-exfatfs:1.1.1.1.0.42 perseant-exfatfs-base:1.1.1.1 netbsd-8-3-RELEASE:1.1.1.1 netbsd-9-4-RELEASE:1.1.1.1 netbsd-10-0-RELEASE:1.1.1.1 netbsd-10-0-RC6:1.1.1.1 netbsd-10-0-RC5:1.1.1.1 netbsd-10-0-RC4:1.1.1.1 netbsd-10-0-RC3:1.1.1.1 netbsd-10-0-RC2:1.1.1.1 netbsd-10-0-RC1:1.1.1.1 netbsd-10:1.1.1.1.0.40 netbsd-10-base:1.1.1.1 netbsd-9-3-RELEASE:1.1.1.1 cjep_sun2x-base1:1.1.1.1 cjep_sun2x:1.1.1.1.0.38 cjep_sun2x-base:1.1.1.1 cjep_staticlib_x-base1:1.1.1.1 netbsd-9-2-RELEASE:1.1.1.1 cjep_staticlib_x:1.1.1.1.0.36 cjep_staticlib_x-base:1.1.1.1 netbsd-9-1-RELEASE:1.1.1.1 phil-wifi-20200421:1.1.1.1 phil-wifi-20200411:1.1.1.1 is-mlppp:1.1.1.1.0.34 is-mlppp-base:1.1.1.1 phil-wifi-20200406:1.1.1.1 netbsd-8-2-RELEASE:1.1.1.1 netbsd-9-0-RELEASE:1.1.1.1 netbsd-9-0-RC2:1.1.1.1 netbsd-9-0-RC1:1.1.1.1 phil-wifi-20191119:1.1.1.1 netbsd-9:1.1.1.1.0.32 netbsd-9-base:1.1.1.1 phil-wifi-20190609:1.1.1.1 netbsd-8-1-RELEASE:1.1.1.1 netbsd-8-1-RC1:1.1.1.1 pgoyette-compat-merge-20190127:1.1.1.1 pgoyette-compat-20190127:1.1.1.1 pgoyette-compat-20190118:1.1.1.1 pgoyette-compat-1226:1.1.1.1 pgoyette-compat-1126:1.1.1.1 pgoyette-compat-1020:1.1.1.1 pgoyette-compat-0930:1.1.1.1 pgoyette-compat-0906:1.1.1.1 netbsd-7-2-RELEASE:1.1.1.1 pgoyette-compat-0728:1.1.1.1 netbsd-8-0-RELEASE:1.1.1.1 phil-wifi:1.1.1.1.0.30 phil-wifi-base:1.1.1.1 pgoyette-compat-0625:1.1.1.1 netbsd-8-0-RC2:1.1.1.1 pgoyette-compat-0521:1.1.1.1 pgoyette-compat-0502:1.1.1.1 pgoyette-compat-0422:1.1.1.1 netbsd-8-0-RC1:1.1.1.1 pgoyette-compat-0415:1.1.1.1 pgoyette-compat-0407:1.1.1.1 pgoyette-compat-0330:1.1.1.1 pgoyette-compat-0322:1.1.1.1 pgoyette-compat-0315:1.1.1.1 netbsd-7-1-2-RELEASE:1.1.1.1 pgoyette-compat:1.1.1.1.0.28 pgoyette-compat-base:1.1.1.1 netbsd-7-1-1-RELEASE:1.1.1.1 matt-nb8-mediatek:1.1.1.1.0.26 matt-nb8-mediatek-base:1.1.1.1 perseant-stdc-iso10646:1.1.1.1.0.24 perseant-stdc-iso10646-base:1.1.1.1 netbsd-8:1.1.1.1.0.22 netbsd-8-base:1.1.1.1 prg-localcount2-base3:1.1.1.1 prg-localcount2-base2:1.1.1.1 prg-localcount2-base1:1.1.1.1 prg-localcount2:1.1.1.1.0.20 prg-localcount2-base:1.1.1.1 pgoyette-localcount-20170426:1.1.1.1 bouyer-socketcan-base1:1.1.1.1 pgoyette-localcount-20170320:1.1.1.1 netbsd-7-1:1.1.1.1.0.18 netbsd-7-1-RELEASE:1.1.1.1 netbsd-7-1-RC2:1.1.1.1 netbsd-7-nhusb-base-20170116:1.1.1.1 bouyer-socketcan:1.1.1.1.0.16 bouyer-socketcan-base:1.1.1.1 pgoyette-localcount-20170107:1.1.1.1 netbsd-7-1-RC1:1.1.1.1 pgoyette-localcount-20161104:1.1.1.1 netbsd-7-0-2-RELEASE:1.1.1.1 localcount-20160914:1.1.1.1 netbsd-7-nhusb:1.1.1.1.0.14 netbsd-7-nhusb-base:1.1.1.1 pgoyette-localcount-20160806:1.1.1.1 pgoyette-localcount-20160726:1.1.1.1 pgoyette-localcount:1.1.1.1.0.12 pgoyette-localcount-base:1.1.1.1 netbsd-7-0-1-RELEASE:1.1.1.1 netbsd-7-0:1.1.1.1.0.10 netbsd-7-0-RELEASE:1.1.1.1 netbsd-7-0-RC3:1.1.1.1 netbsd-7-0-RC2:1.1.1.1 netbsd-7-0-RC1:1.1.1.1 tls-maxphys-base:1.1.1.1 tls-maxphys:1.1.1.1.0.8 netbsd-7:1.1.1.1.0.6 netbsd-7-base:1.1.1.1 yamt-pagecache:1.1.1.1.0.4 yamt-pagecache-base9:1.1.1.1 tls-earlyentropy:1.1.1.1.0.2 tls-earlyentropy-base:1.1.1.1 riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.1.1.1 riastradh-drm2-base3:1.1.1.1 nvi-20131120:1.1.1.1 NVI:1.1.1; locks; strict; comment @# @; 1.1 date 2013.11.22.14.55.19; author christos; state Exp; branches 1.1.1.1; next ; commitid mIBZbnFe7d4AEhex; 1.1.1.1 date 2013.11.22.14.55.19; author christos; state Exp; branches 1.1.1.1.4.1 1.1.1.1.8.1; next ; commitid mIBZbnFe7d4AEhex; 1.1.1.1.4.1 date 2013.11.22.14.55.19; author yamt; state dead; branches; next 1.1.1.1.4.2; commitid Arqj98NAscKb9yBx; 1.1.1.1.4.2 date 2014.05.22.15.50.35; author yamt; state Exp; branches; next ; commitid Arqj98NAscKb9yBx; 1.1.1.1.8.1 date 2013.11.22.14.55.19; author tls; state dead; branches; next 1.1.1.1.8.2; commitid jTnpym9Qu0o4R1Nx; 1.1.1.1.8.2 date 2014.08.19.23.51.52; author tls; state Exp; branches; next ; commitid jTnpym9Qu0o4R1Nx; desc @@ 1.1 log @Initial revision @ text @Top priority would be the mouse. We need to get cut&paste working. (Including extend beyond the visible screen. I believe I'm sending the correct mouse events for that, but I haven't tested it.) =-=-=-= Find a tool to convert the reference doc to html, and just point a browser at it for the help screen. Have "novice", "fast lookup" and an "everything" version. =-=-=-= Disassociate scrollbar actions from the cursor, i.e. when you scroll the screen moves but the cursor doesn't. >> However, it seems to me that the cursor should disappear from >> the screen as soon as it's no longer positioned on a line that's >> on the screen. Does that make sense? And, if so, how do we >> make that happen? > > I'd add a message: > IPO_DISPLAY_CARET( boolean ) > since the caret is also used for the current drawing position, we > really can't move it 'off the screen'. =-=-=-= >> BTW, this may be a bug, I can't seem to erase characters in the >> colon command line. > > It's a bug that I reported earlier. Core is not (correctly) reading the > tty options for the terminal. Since we have not bound magic > characters (VI_BACKSPACE) to BackSpace and Delete keys, the > editing here is counter-intuitive. I'd guess that you use > Delete for Tty Erase. Try ^H in the colon line and see what happens. =-=-=-= Implement a "word search" button for the search dialog -- it's not trivial, the ex/ex_subst.c/re_compile() routine is going to have to allocate memory for the pattern which isn't going to make it happy. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /* TODO List: * scrollbars Need protocol messages that tell us what to display * in the scrollbars. Suggestion: * scrollbar( bottom, lines, home ) * bottom is $ * lines is lines shown in the window * (takes wrap into account) * home is the line number ot the top visible line * * On the way back send scroll( top ) * * User should be able to enable/disable bar display * * horizontal scrollbar * * expose_func * insert/delete When we have a partially obscured window, we only * refresh a single line after scrolling. I believe this * is due to the exposure events all showing up after * the scrolling is completed (pipe_input_func does all * of the scrolling and then we get back to XtMainLoop) * * split Ought to be able to put a title on each pane * Need protocol messages to shift focus * * bell user settable visible bell * * busy don't understand the protocol * * mouse need to send IPO_MOVE_CARET( row, column ) * (note that screen code does not know about tabs or * line wraps) * Connect to window manager cut buffer * need to send IPO_EXTEND_SELECT( r1, c1, r2, c1 ) * otherwise core and screen duplicate selection logic * Need to determine correct screen for event. Not * needed until split is implemented. * * arrow keys need to define a protocol. I can easily send * the vt100 sequences (and currently do). * In general, we need to define what special keys * do (for example PageUp) and what happens when we * are in Insert mode. * * Suggestion: IPO_COMMAND( string ). vi core can * take it as a command even when in insert mode. * * icon Is currently B&W. To get a color icon, would * require a lot of work or that bostic pick up * the xpm library. */ @ 1.1.1.1 log @Import nvi-1.81.6 + HEAD-2013-11-20 from git://repo.or.cz/nvi.git @ text @@ 1.1.1.1.8.1 log @file TODO was added on branch tls-maxphys on 2014-08-19 23:51:52 +0000 @ text @d1 90 @ 1.1.1.1.8.2 log @Rebase to HEAD as of a few days ago. @ text @a0 90 Top priority would be the mouse. We need to get cut&paste working. (Including extend beyond the visible screen. I believe I'm sending the correct mouse events for that, but I haven't tested it.) =-=-=-= Find a tool to convert the reference doc to html, and just point a browser at it for the help screen. Have "novice", "fast lookup" and an "everything" version. =-=-=-= Disassociate scrollbar actions from the cursor, i.e. when you scroll the screen moves but the cursor doesn't. >> However, it seems to me that the cursor should disappear from >> the screen as soon as it's no longer positioned on a line that's >> on the screen. Does that make sense? And, if so, how do we >> make that happen? > > I'd add a message: > IPO_DISPLAY_CARET( boolean ) > since the caret is also used for the current drawing position, we > really can't move it 'off the screen'. =-=-=-= >> BTW, this may be a bug, I can't seem to erase characters in the >> colon command line. > > It's a bug that I reported earlier. Core is not (correctly) reading the > tty options for the terminal. Since we have not bound magic > characters (VI_BACKSPACE) to BackSpace and Delete keys, the > editing here is counter-intuitive. I'd guess that you use > Delete for Tty Erase. Try ^H in the colon line and see what happens. =-=-=-= Implement a "word search" button for the search dialog -- it's not trivial, the ex/ex_subst.c/re_compile() routine is going to have to allocate memory for the pattern which isn't going to make it happy. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /* TODO List: * scrollbars Need protocol messages that tell us what to display * in the scrollbars. Suggestion: * scrollbar( bottom, lines, home ) * bottom is $ * lines is lines shown in the window * (takes wrap into account) * home is the line number ot the top visible line * * On the way back send scroll( top ) * * User should be able to enable/disable bar display * * horizontal scrollbar * * expose_func * insert/delete When we have a partially obscured window, we only * refresh a single line after scrolling. I believe this * is due to the exposure events all showing up after * the scrolling is completed (pipe_input_func does all * of the scrolling and then we get back to XtMainLoop) * * split Ought to be able to put a title on each pane * Need protocol messages to shift focus * * bell user settable visible bell * * busy don't understand the protocol * * mouse need to send IPO_MOVE_CARET( row, column ) * (note that screen code does not know about tabs or * line wraps) * Connect to window manager cut buffer * need to send IPO_EXTEND_SELECT( r1, c1, r2, c1 ) * otherwise core and screen duplicate selection logic * Need to determine correct screen for event. Not * needed until split is implemented. * * arrow keys need to define a protocol. I can easily send * the vt100 sequences (and currently do). * In general, we need to define what special keys * do (for example PageUp) and what happens when we * are in Insert mode. * * Suggestion: IPO_COMMAND( string ). vi core can * take it as a command even when in insert mode. * * icon Is currently B&W. To get a color icon, would * require a lot of work or that bostic pick up * the xpm library. */ @ 1.1.1.1.4.1 log @file TODO was added on branch yamt-pagecache on 2014-05-22 15:50:35 +0000 @ text @d1 90 @ 1.1.1.1.4.2 log @sync with head. for a reference, the tree before this commit was tagged as yamt-pagecache-tag8. this commit was splitted into small chunks to avoid a limitation of cvs. ("Protocol error: too many arguments") @ text @a0 90 Top priority would be the mouse. We need to get cut&paste working. (Including extend beyond the visible screen. I believe I'm sending the correct mouse events for that, but I haven't tested it.) =-=-=-= Find a tool to convert the reference doc to html, and just point a browser at it for the help screen. Have "novice", "fast lookup" and an "everything" version. =-=-=-= Disassociate scrollbar actions from the cursor, i.e. when you scroll the screen moves but the cursor doesn't. >> However, it seems to me that the cursor should disappear from >> the screen as soon as it's no longer positioned on a line that's >> on the screen. Does that make sense? And, if so, how do we >> make that happen? > > I'd add a message: > IPO_DISPLAY_CARET( boolean ) > since the caret is also used for the current drawing position, we > really can't move it 'off the screen'. =-=-=-= >> BTW, this may be a bug, I can't seem to erase characters in the >> colon command line. > > It's a bug that I reported earlier. Core is not (correctly) reading the > tty options for the terminal. Since we have not bound magic > characters (VI_BACKSPACE) to BackSpace and Delete keys, the > editing here is counter-intuitive. I'd guess that you use > Delete for Tty Erase. Try ^H in the colon line and see what happens. =-=-=-= Implement a "word search" button for the search dialog -- it's not trivial, the ex/ex_subst.c/re_compile() routine is going to have to allocate memory for the pattern which isn't going to make it happy. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /* TODO List: * scrollbars Need protocol messages that tell us what to display * in the scrollbars. Suggestion: * scrollbar( bottom, lines, home ) * bottom is $ * lines is lines shown in the window * (takes wrap into account) * home is the line number ot the top visible line * * On the way back send scroll( top ) * * User should be able to enable/disable bar display * * horizontal scrollbar * * expose_func * insert/delete When we have a partially obscured window, we only * refresh a single line after scrolling. I believe this * is due to the exposure events all showing up after * the scrolling is completed (pipe_input_func does all * of the scrolling and then we get back to XtMainLoop) * * split Ought to be able to put a title on each pane * Need protocol messages to shift focus * * bell user settable visible bell * * busy don't understand the protocol * * mouse need to send IPO_MOVE_CARET( row, column ) * (note that screen code does not know about tabs or * line wraps) * Connect to window manager cut buffer * need to send IPO_EXTEND_SELECT( r1, c1, r2, c1 ) * otherwise core and screen duplicate selection logic * Need to determine correct screen for event. Not * needed until split is implemented. * * arrow keys need to define a protocol. I can easily send * the vt100 sequences (and currently do). * In general, we need to define what special keys * do (for example PageUp) and what happens when we * are in Insert mode. * * Suggestion: IPO_COMMAND( string ). vi core can * take it as a command even when in insert mode. * * icon Is currently B&W. To get a color icon, would * require a lot of work or that bostic pick up * the xpm library. */ @