<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sciteco/debian/control, branch v2.5.0</title>
<subtitle>Scintilla-based Text Editor and COrrector</subtitle>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/'/>
<entry>
<title>moved most resources to fmsbw.de</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:37:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=c08ce4b183726c9f0eeeb5a40e04e7306c7f5e4e'/>
<id>c08ce4b183726c9f0eeeb5a40e04e7306c7f5e4e</id>
<content type='text'>
* The new official homepage is https://sciteco.fmsbw.de/
* My new contact address is rhaberkorn AT fmsbw.de.
* The scintilla-mirror is now also on https://git.fmsbw.de/scintilla-mirror/
* Added CI script for my server on fmsbw.de that builds
  the website.
  It's run in a FreeBSD container, but does not currently
  distribute FreeBSD binaries.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* The new official homepage is https://sciteco.fmsbw.de/
* My new contact address is rhaberkorn AT fmsbw.de.
* The scintilla-mirror is now also on https://git.fmsbw.de/scintilla-mirror/
* Added CI script for my server on fmsbw.de that builds
  the website.
  It's run in a FreeBSD container, but does not currently
  distribute FreeBSD binaries.
</pre>
</div>
</content>
</entry>
<entry>
<title>bumped minimum Gtk version to 3.24</title>
<updated>2025-08-28T08:26:01+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-08-27T23:40:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=2070d7faf66425c72677c02616a087d30a9aa863'/>
<id>2070d7faf66425c72677c02616a087d30a9aa863</id>
<content type='text'>
* Gtk 3.24 has been introduced accidentally in 9e3746a4
  due to GtkEventControllerScroll.
* It would be possible to still support v3.12 by partially
  reversing 9e3746a4 and conditionally including teco_interface_scroll_cb().
  But it's probably not worth the trouble.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Gtk 3.24 has been introduced accidentally in 9e3746a4
  due to GtkEventControllerScroll.
* It would be possible to still support v3.12 by partially
  reversing 9e3746a4 and conditionally including teco_interface_scroll_cb().
  But it's probably not worth the trouble.
</pre>
</div>
</content>
</entry>
<entry>
<title>bumped minimum GCC version to v8.1</title>
<updated>2025-08-26T14:42:52+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-08-26T14:42:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=f525d8f09ec0e60effe70623a19c700a3a202db0'/>
<id>f525d8f09ec0e60effe70623a19c700a3a202db0</id>
<content type='text'>
Scintilla v5.5.7 officially requires at least GCC v9, but if it's
only the charconv header that's required from newer releases, v8.1
will probably do as well. We assume so until proven wrong.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Scintilla v5.5.7 officially requires at least GCC v9, but if it's
only the charconv header that's required from newer releases, v8.1
will probably do as well. We assume so until proven wrong.
</pre>
</div>
</content>
</entry>
<entry>
<title>support Groff v1.19.2 as still used by default on NetBSD 10</title>
<updated>2025-08-21T23:54:09+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-08-20T07:33:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=ed651bf96f558fd6514d8301c813a175a8a1c51b'/>
<id>ed651bf96f558fd6514d8301c813a175a8a1c51b</id>
<content type='text'>
* They have a newer version in pkgsrc, but it's not even available
  as a binary package on the arm6.
* Has some glitches, e.g. does accept the ASCII 27 in tutorial.ms,
  but it's probably not worth to work around.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* They have a newer version in pkgsrc, but it's not even available
  as a binary package on the arm6.
* Has some glitches, e.g. does accept the ASCII 27 in tutorial.ms,
  but it's probably not worth to work around.
</pre>
</div>
</content>
</entry>
<entry>
<title>Debian: explicitly depend on a C compiler as well</title>
<updated>2025-08-14T12:56:27+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-08-14T12:56:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=635ff6ecb2a172003ec614cade4cb1c683bb968e'/>
<id>635ff6ecb2a172003ec614cade4cb1c683bb968e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>added tutorial document, which is automatically loaded on the first invocation</title>
<updated>2025-03-31T00:23:06+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-03-31T00:23:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=6afa02a161493c646e64fb6afca13de7d33fd699'/>
<id>6afa02a161493c646e64fb6afca13de7d33fd699</id>
<content type='text'>
* This is rendered with ms, so we now need the entire groff on Debian.
  This is not a big deal as it just adds a few kilobytes of build-time dependencies.
  Most platforms do not allow installation of some "groff-base" package anyway
  and always draw in the entire package.
* sciteco.tmac has been extended to disable page breaks on ms.
* The tutorial is installed like any other woman page and can be invoked
  interactively with ?tutorial$.
* It is optimized to be still usable on a plain 80x24 terminal.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* This is rendered with ms, so we now need the entire groff on Debian.
  This is not a big deal as it just adds a few kilobytes of build-time dependencies.
  Most platforms do not allow installation of some "groff-base" package anyway
  and always draw in the entire package.
* sciteco.tmac has been extended to disable page breaks on ms.
* The tutorial is installed like any other woman page and can be invoked
  interactively with ?tutorial$.
* It is optimized to be still usable on a plain 80x24 terminal.
</pre>
</div>
</content>
</entry>
<entry>
<title>rename sample.teco_ini to fallback.teco_ini and mung it by default</title>
<updated>2025-03-03T20:35:04+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-03-02T22:44:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=1b907dae072f2aa93d75d8c056a9bd02555a17f8'/>
<id>1b907dae072f2aa93d75d8c056a9bd02555a17f8</id>
<content type='text'>
* After installation, SciTECO will therefore start into a more userfriendly mode
  even if the user does not create a custom ~/.teco_ini.
  It is hoped that this will scare away less of new users, who
  are not willing to read through all of the documentation.
  Still, users are warned in the absence of ~/.teco_ini.
  This warning however, might not be immediately visible, especially
  not when running gsciteco without an attached console.
  (This will change once I redo the UI and allow a number of messages
  to be queued in the message area.)
* Theoretically, you could also just extend fallback.teco_ini from ~/.teco_ini,
  but that would require installing it into $SCITECOPATH.
* Since the fallback profile will now be munged automatically
  on a wide range of systems, we set up xclip only when detecting X11
  ($DISPLAY is non-empty).
  E.g. when running under Wayland or the Linux console, you still won't
  get the clipboard registers, which is probably better than having the
  clipboard operations fail once you try to use them.
* xclip is now "suggested" on Debian/Ubuntu.
  Unfortunately we cannot pull it in only in the presence of X11.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* After installation, SciTECO will therefore start into a more userfriendly mode
  even if the user does not create a custom ~/.teco_ini.
  It is hoped that this will scare away less of new users, who
  are not willing to read through all of the documentation.
  Still, users are warned in the absence of ~/.teco_ini.
  This warning however, might not be immediately visible, especially
  not when running gsciteco without an attached console.
  (This will change once I redo the UI and allow a number of messages
  to be queued in the message area.)
* Theoretically, you could also just extend fallback.teco_ini from ~/.teco_ini,
  but that would require installing it into $SCITECOPATH.
* Since the fallback profile will now be munged automatically
  on a wide range of systems, we set up xclip only when detecting X11
  ($DISPLAY is non-empty).
  E.g. when running under Wayland or the Linux console, you still won't
  get the clipboard registers, which is probably better than having the
  clipboard operations fail once you try to use them.
* xclip is now "suggested" on Debian/Ubuntu.
  Unfortunately we cannot pull it in only in the presence of X11.
</pre>
</div>
</content>
</entry>
<entry>
<title>Debian: disabled parallel builds when running the test suite</title>
<updated>2024-12-28T01:01:18+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-12-28T00:58:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=9f9b31685d612731c2b3064beb9fa149f4b6e76a'/>
<id>9f9b31685d612731c2b3064beb9fa149f4b6e76a</id>
<content type='text'>
* Hopefully makes the log easier to read in case of failures.
  There may still be 2 runs concurrently since we build Curses and Gtk in parallel.
* Updated homepage.
* Ubuntu plucky builds are failing.
  See https://launchpadlibrarian.net/765999455/buildlog_ubuntu-plucky-amd64.sciteco_2.3.0-0ppa1~plucky1_BUILDING.txt.gz
  This may have been a spurious failure due to xvfb-run.
  It may be less likely with --no-parallel.
  Theoretically we could bump the Debian package version in order to test that,
  but the PPA is practically not used by anybody anyway.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Hopefully makes the log easier to read in case of failures.
  There may still be 2 runs concurrently since we build Curses and Gtk in parallel.
* Updated homepage.
* Ubuntu plucky builds are failing.
  See https://launchpadlibrarian.net/765999455/buildlog_ubuntu-plucky-amd64.sciteco_2.3.0-0ppa1~plucky1_BUILDING.txt.gz
  This may have been a spurious failure due to xvfb-run.
  It may be less likely with --no-parallel.
  Theoretically we could bump the Debian package version in order to test that,
  but the PPA is practically not used by anybody anyway.
</pre>
</div>
</content>
</entry>
<entry>
<title>prefer libncursesw (widechar variant) (refs #5)</title>
<updated>2024-09-09T16:17:03+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-08-28T12:03:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=f79a6f65acde9753ea65887e0e0d4bc7f76ff52b'/>
<id>f79a6f65acde9753ea65887e0e0d4bc7f76ff52b</id>
<content type='text'>
* Some platforms like Ubuntu actually ship widechar and non-widechar versions
  of ncurses with different pkg-config files.
  Other platforms like FreeBSD will ship an "ncursesw" and "ncurses" pkg-config file
  but both point to the same wide-char library anyway.
* Currently we are not using wide-char APIs to ensure maximum compatibility even with
  embedded systems where ncurses might be built without widechar support.
  But in order to handle Unicode correctly, we still need to link against the widechar version
  of ncurses (if available).
* Compilation on platforms without a widechar ncurses is now handled by the common
  AC_CHECK_LIB() fallback (which might actually find a widechar version anyway if it just
  didn't install the pkg-config file).
  If necessary, we could also check for the "ncurses" package if "ncursesw" is not found.
* This fixes Unicode display and input on Ubuntu.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Some platforms like Ubuntu actually ship widechar and non-widechar versions
  of ncurses with different pkg-config files.
  Other platforms like FreeBSD will ship an "ncursesw" and "ncurses" pkg-config file
  but both point to the same wide-char library anyway.
* Currently we are not using wide-char APIs to ensure maximum compatibility even with
  embedded systems where ncurses might be built without widechar support.
  But in order to handle Unicode correctly, we still need to link against the widechar version
  of ncurses (if available).
* Compilation on platforms without a widechar ncurses is now handled by the common
  AC_CHECK_LIB() fallback (which might actually find a widechar version anyway if it just
  didn't install the pkg-config file).
  If necessary, we could also check for the "ncurses" package if "ncursesw" is not found.
* This fixes Unicode display and input on Ubuntu.
</pre>
</div>
</content>
</entry>
<entry>
<title>Debian: updated/modernized config files</title>
<updated>2023-06-20T14:40:54+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2023-06-20T03:03:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=fe9e438e3302b4078e18f1591eb81296da104d1a'/>
<id>fe9e438e3302b4078e18f1591eb81296da104d1a</id>
<content type='text'>
* This resolves must lintian warnings and errors.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* This resolves must lintian warnings and errors.
</pre>
</div>
</content>
</entry>
</feed>
