<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sciteco/tests, branch v2.5.1</title>
<subtitle>Scintilla-based Text Editor and COrrector</subtitle>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/'/>
<entry>
<title>Haiku is officially supported again from now on</title>
<updated>2026-01-09T11:07:54+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2026-01-09T11:07:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=acc6f6e83b9cabdc78b6a4f331c510c69e5ff757'/>
<id>acc6f6e83b9cabdc78b6a4f331c510c69e5ff757</id>
<content type='text'>
* Turns out that it works perfectly with the default --enable-malloc-replacement
  as malloc() is replaced globally.
* Added note to configure.ac that malloc() replacement may be useful on platforms
  without a global symbol namespace - you just have to link statically (--enable-static-executables)
  as well.
  This wasn't necessary on Haiku, though.
* Only the test suite required a minor fix since Haiku doesn't support `ulimit`.
* The Gtk interface is broken though on Haiku: You cannot type dead keys,
  Ctrl and AltGr combinations.
  Doesn't appear to be SciTECO-specific though. The libraries simply doesn't
  report modifiers. Appears to be a bug in Haiku's GTK 3 port,
  at least in their Beta5 branch. It can be reproduced with gtk-demo as well.
* This opens the door for contributing a port into HaikuPorts.
  This will probably be Curses-only for the time being (see above).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Turns out that it works perfectly with the default --enable-malloc-replacement
  as malloc() is replaced globally.
* Added note to configure.ac that malloc() replacement may be useful on platforms
  without a global symbol namespace - you just have to link statically (--enable-static-executables)
  as well.
  This wasn't necessary on Haiku, though.
* Only the test suite required a minor fix since Haiku doesn't support `ulimit`.
* The Gtk interface is broken though on Haiku: You cannot type dead keys,
  Ctrl and AltGr combinations.
  Doesn't appear to be SciTECO-specific though. The libraries simply doesn't
  report modifiers. Appears to be a bug in Haiku's GTK 3 port,
  at least in their Beta5 branch. It can be reproduced with gtk-demo as well.
* This opens the door for contributing a port into HaikuPorts.
  This will probably be Curses-only for the time being (see above).
</pre>
</div>
</content>
</entry>
<entry>
<title>fixup: disabled the --detach test case again</title>
<updated>2025-12-30T10:53:52+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-12-30T10:53:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=2d0c67e2e4d705276171e67aa81da8bf90b4d7d0'/>
<id>2d0c67e2e4d705276171e67aa81da8bf90b4d7d0</id>
<content type='text'>
It causes build failures on OBS for several Linux distributions.
It generally works on Linux, so it's probably related to Xvfb.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It causes build failures on OBS for several Linux distributions.
It generally works on Linux, so it's probably related to Xvfb.
</pre>
</div>
</content>
</entry>
<entry>
<title>fixup: wait for test.txt in detached SciTECO instance for up to 10 seconds</title>
<updated>2025-12-30T09:32:05+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-12-30T09:32:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=aa6c8d47ea120670c0858d50bc33072ca2ba718d'/>
<id>aa6c8d47ea120670c0858d50bc33072ca2ba718d</id>
<content type='text'>
Hopefully fixes the OBS build errors.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Hopefully fixes the OBS build errors.
</pre>
</div>
</content>
</entry>
<entry>
<title>GTK: implemented --detach|-d option for detaching from controlling terminal</title>
<updated>2025-12-29T23:42:34+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-12-29T11:01:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=a7202a1fb911f72c309380b42c0ff995c05ba94c'/>
<id>a7202a1fb911f72c309380b42c0ff995c05ba94c</id>
<content type='text'>
This is useful to launch from a terminal without "blocking" this terminal.
There are tools like nohup and daemonize (BSD) to do the same, but having it
builtin is shorter to write.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is useful to launch from a terminal without "blocking" this terminal.
There are tools like nohup and daemonize (BSD) to do the same, but having it
builtin is shorter to write.
</pre>
</div>
</content>
</entry>
<entry>
<title>fixed ^S/^Y for search-replacement commands</title>
<updated>2025-12-25T21:55:32+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-12-25T21:55:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=44166f53d5923be4685a69b85166ada40dc1cc10'/>
<id>44166f53d5923be4685a69b85166ada40dc1cc10</id>
<content type='text'>
It was returning the range of the search, but not of the inserted text.
Since the searched text is deleted, the range of the insertion is more useful.
It's also what was documented and what DEC TECO does.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It was returning the range of the search, but not of the inserted text.
Since the searched text is deleted, the range of the insertion is more useful.
It's also what was documented and what DEC TECO does.
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "testsuite: disable testcases with Valgrind only when detecting the fmsbw.de CI runner"</title>
<updated>2025-11-09T20:14:38+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-11-09T20:14:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=939134b87821a32b84a2f14a48ea705eb0d49d7c'/>
<id>939134b87821a32b84a2f14a48ea705eb0d49d7c</id>
<content type='text'>
This reverts commit 092f7d9919d9572219b7bf516933c37180e6f400.

Turns out that the "Memory limiting" test cases won't even successfully run on my PC under Valgrind.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 092f7d9919d9572219b7bf516933c37180e6f400.

Turns out that the "Memory limiting" test cases won't even successfully run on my PC under Valgrind.
</pre>
</div>
</content>
</entry>
<entry>
<title>throw an error immediately after nEB if n != 0</title>
<updated>2025-10-06T21:58:11+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-10-06T21:58:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=a62323baa454b4a6ac698067043c8d4cf50c6561'/>
<id>a62323baa454b4a6ac698067043c8d4cf50c6561</id>
<content type='text'>
* 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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* 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.
</pre>
</div>
</content>
</entry>
<entry>
<title>./configure --with-launcher=LAUNCHER can be used to run SciTECO with a launcher command (e.g. wine or wine64)</title>
<updated>2025-09-24T00:13:40+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-09-24T00:13:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=8159f5930df5cc8bde25c69e064a203dcbfdd6bf'/>
<id>8159f5930df5cc8bde25c69e064a203dcbfdd6bf</id>
<content type='text'>
* 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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* 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.
</pre>
</div>
</content>
</entry>
<entry>
<title>testsuite: disable testcases with Valgrind only when detecting the fmsbw.de CI runner</title>
<updated>2025-09-22T20:09:43+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-09-22T20:09:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=092f7d9919d9572219b7bf516933c37180e6f400'/>
<id>092f7d9919d9572219b7bf516933c37180e6f400</id>
<content type='text'>
These testcases can still be run with --valgrind on my PC.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
These testcases can still be run with --valgrind on my PC.
</pre>
</div>
</content>
</entry>
<entry>
<title>testsuite: disable test cases when running with --valgrind</title>
<updated>2025-09-21T14:30:15+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-09-21T09:50:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=6b030fe1a7b72c039cf0aa7c353b11fbfe46d20c'/>
<id>6b030fe1a7b72c039cf0aa7c353b11fbfe46d20c</id>
<content type='text'>
Should fix the freebsd14-sciteco CI job.
On the other hand, these test cases do run through on my workstation,
so we might want to disable them *only* when running via CI.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Should fix the freebsd14-sciteco CI job.
On the other hand, these test cases do run through on my workstation,
so we might want to disable them *only* when running via CI.
</pre>
</div>
</content>
</entry>
</feed>
