| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
We cannot rely on the central teco_cmdline_update() call per keypress
in this case.
The analogous call was removed in 4e6ddd6c329d56055a732c6344df019f0d997aaf,
so this was a recent regression.
|
|
* color.target is yellow in terminal.tes which looks awful and it should be
used sparingly.
The largest part of text in any lexer should be in the default colors.
* bash.tes now discerns between double and single quote strings like most lexers.
* autodetect GNUmakefiles
* yaml.tes now uses color.string for keys - this is for consistency with JSON
where keys will also always be strings.
|
|
|
|
* grosciteco.tes generates two output files.
First this was modeled with `%.woman %.woman.tec : ...`, but it creates independant rules
which could result in superfluous builds and broke parallel builds.
Then I tried grouped targets (`%.woman %.woman.tec &: ...`) which were supposed to solve the
problem cleanly. However they turned out to be buggy with pattern rules,
so I used templates instead.
Unfortunately grouped targets turned out to be unreliable in general and that broke
some older platforms, resulting in broken .woman.tec files.
* The same can be achieved by declaring .woman files the main artifact and
having an empty rule like `%.woman.tec : %.woman;`.
If anything draws in .woman.tec, it will still execute the rule only once.
|
|
|
|
|
|
rendered as "TAB" without any indentation
|
|
It does not change anything functionally, though.
|
|
0x404040 (COLOR_LBLACK) is a poor choice since on terminal emulators
with less than 16 colors, it would be rendered in black (and thus be invisible).
|
|
replacement ({...})
* The line end type and tab mode is apparently a property of the document.
Therefore it was lost when exchanging the command line's document during command line replacement.
* Instead, the old command line is now stored in a string.
* During replacement we delete and append only the part of the command line that changed.
This ensures that we don't have to restyle the entire command line with every single
replacement (even if it is at the end of the command line).
|
|
The new wcwidth.c wasn't actually linked in.
|
|
This requires enhanced INDIC_STRAIGHTBOX semantics, which are not yet upstream in Scinterm.
|
|
* This currently needs a yet unmerged patch, fixing the light colors.
* Scinterm no longer systematically initializes the color pairs, so
we cannot predict their numbers - instead we initialize color pairs
on demand and store them in a hash map, very similar to what Scinterm
does internally.
* Scinterm v5.5 can use arbitrary RGB colors now by automatically
allocating curses colors and pairs.
We do not expose this in SciTECO yet, although that would also
be possible.
It has to be decided first whether the special predefined colors
will continue to live in the same namespace along with "true"
RGB colors.
|
|
This was broken if you configured a command line with a height > 1.
|
|
SC_LINE_END_TYPE_NONE
|
|
fmsbw.de CI runner"
This reverts commit 092f7d9919d9572219b7bf516933c37180e6f400.
Turns out that the "Memory limiting" test cases won't even successfully run on my PC under Valgrind.
|
|
|
|
* This allows for several customizations.
* You can simply increase the visible command line history.
For that you must also set SCI_SETWRAPMODE(SC_WRAP_CHAR).
An example was added to fallback.teco_ini.
* You could also set SCI_SETLINEENDTYPESALLOWED(SC_LINE_END_TYPE_DEFAULT)
to see the structure of inserted text.
* Alternatively we could have introduced a new command like EP or FW
and also overload it to replace the current ED&2048 (e.g. -EP and EP).
In DEC TECO `W` comes closest to what 5EJ now does.
|
|
the current line as well
* This optimization is unnecessary for regular TECO scripts unless you write stupendously long lines.
On the command line macro however, we were always restyling the entire command line with every insertion
or rubout since the command line view uses single line mode by default.
Even if you enable a multi-line command line with regular line breaks, it's unlikely that you would insert
many line breaks except when inserting text into the buffer.
* We will now during insertion into the command line view style from the beginning of the last regular
command.
* During rub out from the command line, we still won't have enough information about where the previous
valid start state was, so we will frequently have to restyle the entire command line.
This might be worked around by adding a cmdline-view-specific hack if it turns out to be relevant
on very long command lines and slow computers.
|
|
These are equivalent, but LINES and COLS are shorter.
|
|
enables syntax highlighting on the command line
* M[lexer.set.cmdline] can be used to set up syntax highlighting on the command line
(if desired).
* Color schemes with light-dark themes (solarized.tes) are now responsible
to update the command line view as well.
|
|
* Instead of rendering a teco_string_t into a Scintilla view (GTK)
and an ncurses window (Curses), it is now a Scintilla view and document
that is modified directly.
* Reduces redundancies between GTK and Curses UIs.
* It will be more efficient on very large command lines, especially on GTK.
* We can now redirect Scintilla messages to the command line view in order
to configure syntax highlighting, the margin, rubout indicator style and
scroll behavior (TODO).
* This will also simplify the configuration of multi-line command lines (TODO).
* Since INDIC_PLAIN is not supported by Scinterm, rubbed out command lines
are now styled with INDIC_STRAIGHTBOX (background color).
|
|
* This requires the new SCI_SETTABDRAWMODE(SCTD_CONTROLCHAR).
* It makes no sense to let TAB indent in TECO code as it can be
the insert-with-tab command (^I).
On the other hand large `I`-blocks could include TABs which are
actually meant as indentations.
|
|
This simplifies teco_interface_cmdline_update() and prepares for backing the
command line macro itself with a Scintilla view (teco_view_t).
The latter will avoid unnecessary recalculations when inserting characters
into the command line and to factor out redundancies with the Curses UI.
|
|
* It was failing on OpenSUSE Tumbleweed i586 on OBS,
resulting in duplicate symbols and build errors.
This was not reproducible with 32-bit builds on OpenSUSE Tumbleweed x86_64.
* Instead of hoping for a compiler warning to be treated as an error,
we now use a static assertion with a _Generic expression.
* The scintilla submodule has also been updated since Neil was asking to
update the documentation as well.
|
|
|
|
* Scintilla had build problems if ptrdiff_t doesn't alias int if it has the
same storage size (e.g. on NetBSD 10 (armv6)).
* Unfortunately, Neil Hodgson refused to merge my previous Scintilla patches that
would have fixed the issue at the core.
See https://groups.google.com/g/scintilla-interest/c/STAv6LgLyCo
* He only agreed to introducing a separate flag to work around the issue
(`-DPTRDIFF_DOESNT_ALIAS_INT`).
* In order to continue to support all standard C/C++ conforming platforms
we therefore need a compile-time check to check for the aliasability
of ptrdiff_t and int.
|
|
URLs can change
|
|
Shouldn't change anything functionally, but allows us to more broadly
test the patch (especially via OBS).
|
|
* When typing nEBfilename$ (n != 0) you would find out that the construct is invalid
only after typing out the entire command.
We now throw an error immediately, ie. only Escape or string termination will be expected
in interactive mode.
* In batch mode, nothing should have changed.
|
|
Should hopefully fix errors about invalid $TERM.
|
|
* There already was --enable-static-executables which would pass `-static`
to the linker, but it did not help with library dependencies (that have to be
pulled in transitively when linking statically).
pkg-config does have `--static` support though.
* Now all pkg-config found libraries will use `pkg-config --static` when
--enable-static-executables, which simplifies linking statically.
Previously you'd either need to set PKG_CONFIG="pkg-config --static"
or you would have to manually list library dependencies.
|
|
* We wouldn't detect the correct flags (ax_cv_curses_enhanced and ax_cv_curses_color)
when CURSES_CFLAGS and CURSES_LIBS are given.
* Allows to force ncurses to the SDK/system one when building
for OS X (20-freebsd14-osx-sciteco).
|
|
|
|
FreeBSD-based runners
|
|
This is what the Github CI workflow did previously.
|
|
* In contrast to the old Github workflow, we can no longer create pkgs,
but instead create tar balls. You don't necessarily have to unpack
it into the root, though, since the binaries are relocatable.
* We cannot execute the resulting binaries, so the testsuite is no
longer run under OS X. It could be executed with Darling, but only
under Linux.
* Resulting binaries are currently apparently fully statically linked.
|
|
* strings are bold (if supported) and bright white
* comments are in italics (if supported by the terminal)
* otherwise this uses the same colors as terminal.tes
* should be well suited for monochrome terminals as well
|
|
|
|
* The Knowledge Base replaces the Github wiki.
* The mailing lists replace the Github bug tracker, discussions and pull requests.
|
|
* They were broken because of a confirmed Clang bug.
* As a workaround, we are switching from libstdc++ to libc++.
This is not the default under MINGW64, but also works.
* See also https://github.com/HolyBlackCat/quasi-msys2/issues/44
|
|
This uses an extracted pkg2appimage, since it would be tricky to get fuse
to work in the Podman containers.
|
|
launcher command (e.g. wine or wine64)
* This can be used for bootstrapping Windows binaries cross-compiled on FreeBSD or Linux
without requiring a native build to be installed first.
It will also allow running the test suite under Wine.
While Linux allows registering Wine as the launcher via binfmt_misc,
on FreeBSD we have no choice than to use --with-launcher.
* Unfortunately, SciTECO cannot currently be properly built with versions running under Wine
and the test suite also fails.
|
|
* Also make sure that we find all DLLs.
* The nightly download URL will now be https://sciteco.fmsbw.de/downloads/nightly/
|
|
Appears to result in new problems with win-clang++.
|
|
Otherwise ./configure will try to execute compiled programs and this
doesn't work since they require Wine. There is no binfmt for FreeBSD
unfortunately and I couldn't get any other hack to work either.
Even when adding build-system support for running SciTECO under Wine
for the usual bootstrapping process, this doesn't yet fully work since
there are some features that do not yet work under Wine.
|
|
CI runner
These testcases can still be run with --valgrind on my PC.
|
|
This hopefully fixes the 10-freebsd14-msys-sciteco CI job.
|
|
* This should really be in a separate job, but doing it here allows us
to --disable-bootstrap since we already installed FreeBSD SciTECO binaries.
* In the future, we should rather tweak the build system so it tries
to invoke the cross-compiled SciTECO via Wine.
* Windows Gtk port is still missing.
|
|
Improves readability of the log files.
|
