head 1.2; access; symbols perseant-exfatfs-base-20250801:1.2 perseant-exfatfs-base-20240630:1.2 perseant-exfatfs:1.2.0.16 perseant-exfatfs-base:1.2 cjep_sun2x:1.2.0.14 cjep_sun2x-base:1.2 cjep_staticlib_x-base1:1.2 cjep_staticlib_x:1.2.0.12 cjep_staticlib_x-base:1.2 phil-wifi-20200421:1.2 phil-wifi-20200411:1.2 phil-wifi-20200406:1.2 pgoyette-compat-merge-20190127:1.2 pgoyette-compat-20190127:1.2 pgoyette-compat-20190118:1.2 pgoyette-compat-1226:1.2 pgoyette-compat-1126:1.2 pgoyette-compat-1020:1.2 pgoyette-compat-0930:1.2 pgoyette-compat-0906:1.2 pgoyette-compat-0728:1.2 pgoyette-compat-0625:1.2 pgoyette-compat-0521:1.2 pgoyette-compat-0502:1.2 pgoyette-compat-0422:1.2 pgoyette-compat-0415:1.2 pgoyette-compat-0407:1.2 pgoyette-compat-0330:1.2 pgoyette-compat-0322:1.2 pgoyette-compat-0315:1.2 pgoyette-compat:1.2.0.10 pgoyette-compat-base:1.2 prg-localcount2-base3:1.2 prg-localcount2-base2:1.2 prg-localcount2-base1:1.2 prg-localcount2:1.2.0.8 prg-localcount2-base:1.2 pgoyette-localcount-20170426:1.2 bouyer-socketcan-base1:1.2 pgoyette-localcount-20170320:1.2 bouyer-socketcan:1.2.0.6 bouyer-socketcan-base:1.2 pgoyette-localcount-20170107:1.2 pgoyette-localcount-20161104:1.2 localcount-20160914:1.2 pgoyette-localcount-20160806:1.2 pgoyette-localcount-20160726:1.2 pgoyette-localcount:1.2.0.4 pgoyette-localcount-base:1.2 netbsd-5-2-3-RELEASE:1.1.1.1 netbsd-5-1-5-RELEASE:1.1.1.1 netbsd-6-0-6-RELEASE:1.1.1.1 netbsd-6-1-5-RELEASE:1.1.1.1 yamt-pagecache-base9:1.2 yamt-pagecache-tag8:1.1.1.1 netbsd-6-1-4-RELEASE:1.1.1.1 netbsd-6-0-5-RELEASE:1.1.1.1 tls-earlyentropy:1.2.0.2 tls-earlyentropy-base:1.2 riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.2 riastradh-drm2-base3:1.2 netbsd-6-1-3-RELEASE:1.1.1.1 netbsd-6-0-4-RELEASE:1.1.1.1 netbsd-5-2-2-RELEASE:1.1.1.1 netbsd-5-1-4-RELEASE:1.1.1.1 netbsd-6-1-2-RELEASE:1.1.1.1 netbsd-6-0-3-RELEASE:1.1.1.1 netbsd-5-2-1-RELEASE:1.1.1.1 netbsd-5-1-3-RELEASE:1.1.1.1 netbsd-6-1-1-RELEASE:1.1.1.1 riastradh-drm2-base2:1.1.1.1 riastradh-drm2-base1:1.1.1.1 riastradh-drm2:1.1.1.1.0.34 riastradh-drm2-base:1.1.1.1 netbsd-6-1:1.1.1.1.0.40 netbsd-6-0-2-RELEASE:1.1.1.1 netbsd-6-1-RELEASE:1.1.1.1 khorben-n900:1.1.1.1.0.38 netbsd-6-1-RC4:1.1.1.1 netbsd-6-1-RC3:1.1.1.1 agc-symver:1.1.1.1.0.36 agc-symver-base:1.1.1.1 netbsd-6-1-RC2:1.1.1.1 netbsd-6-1-RC1:1.1.1.1 yamt-pagecache-base8:1.1.1.1 netbsd-5-2:1.1.1.1.0.32 netbsd-6-0-1-RELEASE:1.1.1.1 yamt-pagecache-base7:1.1.1.1 netbsd-5-2-RELEASE:1.1.1.1 netbsd-5-2-RC1:1.1.1.1 matt-nb6-plus-nbase:1.1.1.1 yamt-pagecache-base6:1.1.1.1 netbsd-6-0:1.1.1.1.0.30 netbsd-6-0-RELEASE:1.1.1.1 netbsd-6-0-RC2:1.1.1.1 tls-maxphys:1.1.1.1.0.28 tls-maxphys-base:1.2 matt-nb6-plus:1.1.1.1.0.26 matt-nb6-plus-base:1.1.1.1 netbsd-6-0-RC1:1.1.1.1 yamt-pagecache-base5:1.1.1.1 yamt-pagecache-base4:1.1.1.1 netbsd-6:1.1.1.1.0.24 netbsd-6-base:1.1.1.1 netbsd-5-1-2-RELEASE:1.1.1.1 netbsd-5-1-1-RELEASE:1.1.1.1 yamt-pagecache-base3:1.1.1.1 yamt-pagecache-base2:1.1.1.1 yamt-pagecache:1.1.1.1.0.6 yamt-pagecache-base:1.1.1.1 cherry-xenmp:1.1.1.1.0.22 cherry-xenmp-base:1.1.1.1 bouyer-quota2-nbase:1.1.1.1 bouyer-quota2:1.1.1.1.0.20 bouyer-quota2-base:1.1.1.1 matt-mips64-premerge-20101231:1.1.1.1 matt-nb5-mips64-premerge-20101231:1.1.1.1 matt-nb5-pq3:1.1.1.1.0.18 matt-nb5-pq3-base:1.1.1.1 netbsd-5-1:1.1.1.1.0.16 netbsd-5-1-RELEASE:1.1.1.1 netbsd-5-1-RC4:1.1.1.1 matt-nb5-mips64-k15:1.1.1.1 netbsd-5-1-RC3:1.1.1.1 netbsd-5-1-RC2:1.1.1.1 netbsd-5-1-RC1:1.1.1.1 netbsd-5-0-2-RELEASE:1.1.1.1 matt-nb5-mips64-premerge-20091211:1.1.1.1 matt-premerge-20091211:1.1.1.1 matt-nb5-mips64-u2-k2-k4-k7-k8-k9:1.1.1.1 matt-nb4-mips64-k7-u2a-k9b:1.1.1.1 matt-nb5-mips64-u1-k1-k5:1.1.1.1 matt-nb5-mips64:1.1.1.1.0.14 netbsd-5-0-1-RELEASE:1.1.1.1 jym-xensuspend-nbase:1.1.1.1 netbsd-5-0:1.1.1.1.0.12 netbsd-5-0-RELEASE:1.1.1.1 netbsd-5-0-RC4:1.1.1.1 netbsd-5-0-RC3:1.1.1.1 netbsd-5-0-RC2:1.1.1.1 jym-xensuspend:1.1.1.1.0.10 jym-xensuspend-base:1.1.1.1 netbsd-5-0-RC1:1.1.1.1 netbsd-5:1.1.1.1.0.8 netbsd-5-base:1.1.1.1 matt-mips64-base2:1.1.1.1 wrstuden-revivesa-base-3:1.1.1.1 wrstuden-revivesa:1.1.1.1.0.4 wrstuden-revivesa-base:1.1.1.1 wrstuden-revivesa-base-2:1.1.1.1 wrstuden-revivesa-base-1:1.1.1.1 yamt-pf42-base4:1.1.1.1 yamt-pf42-base3:1.1.1.1 hpcarm-cleanup-nbase:1.1.1.1 yamt-pf42:1.1.1.1.0.2 yamt-pf42-base2:1.1.1.1 yamt-pf42-base:1.1.1.1 nvi-1-81-6:1.1.1.1 NVI:1.1.1; locks; strict; comment @# @; 1.2 date 2013.11.28.22.38.00; author christos; state dead; branches; next 1.1; commitid Y4koZ5sZCl2F16fx; 1.1 date 2008.05.16.18.04.06; author aymeric; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2008.05.16.18.04.06; author aymeric; state Exp; branches 1.1.1.1.2.1 1.1.1.1.4.1 1.1.1.1.6.1 1.1.1.1.28.1; next ; 1.1.1.1.2.1 date 2008.05.16.18.04.06; author yamt; state dead; branches; next 1.1.1.1.2.2; 1.1.1.1.2.2 date 2008.05.18.12.29.30; author yamt; state Exp; branches; next ; 1.1.1.1.4.1 date 2008.05.16.18.04.06; author wrstuden; state dead; branches; next 1.1.1.1.4.2; 1.1.1.1.4.2 date 2008.09.17.04.45.26; author wrstuden; state Exp; branches; next ; 1.1.1.1.6.1 date 2014.05.22.11.27.02; author yamt; state dead; branches; next ; commitid IOnR4fgXMZvMGwBx; 1.1.1.1.28.1 date 2014.08.19.23.45.35; author tls; state dead; branches; next ; commitid jTnpym9Qu0o4R1Nx; desc @@ 1.2 log @These have moved to external @ 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 log @Initial revision @ text @@ 1.1.1.1 log @import nvi 1.81.6 verbatim, untouched from the git tree @ text @@ 1.1.1.1.28.1 log @Rebase to HEAD as of a few days ago. @ text @@ 1.1.1.1.6.1 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 @@ 1.1.1.1.4.1 log @file TODO was added on branch wrstuden-revivesa on 2008-09-17 04:45:26 +0000 @ text @d1 90 @ 1.1.1.1.4.2 log @Sync with wrstuden-revivesa-base-2. @ 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.2.1 log @file TODO was added on branch yamt-pf42 on 2008-05-18 12:29:30 +0000 @ text @d1 90 @ 1.1.1.1.2.2 log @sync with head. @ 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. */ @