diff options
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 56 |
1 files changed, 30 insertions, 26 deletions
@@ -4,12 +4,9 @@ Tasks: "edit" hook. Known Bugs: + * Solaris/OmniOS: There are groff build errors. * Gtk sometimes allows scrolling with the mouse when it shouldn't. All mouse events should currently be blocked. - * Editing very large files, or at least files with very long lines, is painstakingly slow. - Try for instance openrussian-custom-2023-10-09.sql. - For some strange reason, this affects both Curses and GTK. - In UTF-8 mode, this doesn't even load anytime soon. * PDCurses/WinGUI: There is still some flickering, but it got better since key macros update the command line only once. Could already be fixed upstream, see: @@ -106,6 +103,8 @@ Known Bugs: This feature would especially be important in order to support e.g. the SCI_SETPROPERTY message with two strings in order to set lexer properties. + * The lexer.sciteco.macrodef lexer property cannot currently + be set/disabled (see above). * Mac OS: The colors are screwed up with the terminal.tes color scheme (and with --no-profile) under Mac OS terminal emulators. This does not happen under Linux with Darling. @@ -202,8 +201,8 @@ Features: integer and floating point types internally. The operator decides how to interpret the arguments and the return type. - * Having a separate number parser state will simplify - number syntax highlighting. + * Having a separate number parser state will slightly simplify + number syntax highlighting (see teco_lexer_getstyle()).. * Key macro masking flag for the beginning of the command line. May be useful e.g. for solarized's F5 key (i.e. function key macros that need to terminate the command line as they @@ -346,9 +345,6 @@ Features: * Command to free Q-Register (remove from table). e.g. FQ (free Q). :FQ could free by QRegister prefix name for the common use case of Q-Register subtables and lists. - * TECO syntax highlighting. - This should now be relatively easy to implement by reusing - the parser. * multiline commandline * Perhaps use Scintilla view as mini buffer. This means patching Scintilla, so it does not break lines @@ -454,7 +450,7 @@ Features: Furthermore, it may not be trivial to detect such dangling Else/End-If statements as the parser state does not tell us enough. There is nothing that makes code after a successful If-condition - special. Even if we always incresed the nest_level, that + special. Even if we always increased the nest_level, that variable does not discern Ifs and Whiles. * Possible Nightly Build improvements (and therefore releases): * Build 32-bit Ubuntu packages @@ -482,7 +478,6 @@ Features: Other editors use the +line[,col] syntax (see nano). * <:EF> for saving and closing a buffer, similar to <:EX>. * Bash completions. - * Case-sensitive search command (modifier or flag). * FreeBSD: rctl(8) theoretically allows setting up per-process actions when exceeding the memory limit. This however requires special system settings. @@ -529,12 +524,10 @@ Features: Also, parsers are not fully embeddable right now. At the same time, it would need access to the view/document it's supposed to style. Tricky, but not impossible. - * Support external lexers. - Eg. @ES/SCI_SETILEXER/scintillua:APL/ - automatically loads libscintillua.so or scintillua.dll, caches - the library handle and creates the "APL" lexer. - There would also have to be some kind of SCI_NAMEDSTYLE wrapper, - so we can look up style ids by name (specifically for Scintillua). + * A generic Scintillua lexer could be added if we supported setting + lexer properties and if there was a way to retrieve SCI_PRIVATELEXERCALL(1, str). + Perhaps there should be an @EPq/SCI.../ call. + See "Lexer Detection" in https://orbitalquark.github.io/scintillua/manual.html * Lexilla: Could also add an APL lexer to Lexilla. APL has very simple lexical rules. * ^^ in string building expanding to a single caret is not @@ -583,14 +576,20 @@ Features: Perhaps a few select local Q-Registers (-, _, ^X, ^R) should be accessible with the global reg syntax as well, so G- is equivalent to G.-? - * Real block comments (!* ... *!) that don't spam the goto tables. - TECO-64 has end of line comments beginning with !! as well. - We may want both as 0<...> cannot be used to comment out all sorts - of blocks as it necessarily drives the parser. * `-` currently inverts the number sign in teco_state_start_minus(). So --1 == 1 and --C == C. There is probably no need for this "feature" and an error should be thrown instead on the second `-`. + * The command line replacement register (Escape) should be automatically + syntax highlighted. + I am not sure however how that could be done without a special + ED hook. + * Instead of defaulting to nothing in the absence of ~/.teco_ini, + we should load the installed sample.teco_ini, which + gives a more user-friendly experience. + * NLS (Native Language Support). I could at least add German and Russian. + There aren't many localizable strings in SciTECO. + Should be optional. Optimizations: * Use SC_DOCUMENTOPTION_STYLES_NONE in batch mode. @@ -643,9 +642,9 @@ Optimizations: so we would need a small wrapper to call it from C world. * Perhaps replace glib with gnulib. Could improve portability and reduce binary size on platforms where - I have to ship the glib shared library. - Also we could control memory allocations more tightly. - We could also make use of the fnmatch and canonicalize + I currently have to ship the glib shared library. + Also, we could control memory allocations more tightly. + We could also make use of the "fnmatch" and "canonicalize" modules. On the other hand, this imports tons of sh*t into the repository and chains us to Autotools. @@ -658,6 +657,10 @@ Optimizations: are defined. But how to even test for glibc's ptmalloc? Linux could use musl as well for instance. + * Resolve Coverity Scan issues. + If this turns out to be useful, perhaps we can automatically + upload builds via CI? + https://scan.coverity.com/projects/rhaberkorn-sciteco Documentation: * Doxygen docs could be deployed on Github pages @@ -674,9 +677,10 @@ Documentation: Object-oriented SciTECO ideoms etc. ;-) * What to do with `--xembed`: tabbed, st when used as the git editor, etc. - * Perhaps there should be a Getting Started document, - that is automatically opened by sample.teco_ini. * People are demanding a Youtube tutorial. + * Vimtutor like tutorial. Could be a woman-page. + Perhaps sciteco-tutorial would copy the files to /tmp and + open them always with sample.teco_ini. * The HTML manuals lack monospaced fonts. This is partly because an.tmac removes the Courier family in nroff mode, but it still doesn't work if you undo this. |