<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sciteco/src, branch v2.1.0</title>
<subtitle>Scintilla-based Text Editor and COrrector</subtitle>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/'/>
<entry>
<title>Revert "replaced bool completely with gboolean"</title>
<updated>2024-10-16T16:24:16+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-16T16:24:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=caee6fbff7cf0a10bf568b1ed9643d15061f305c'/>
<id>caee6fbff7cf0a10bf568b1ed9643d15061f305c</id>
<content type='text'>
This reverts commit 024d26ac0cd869826801889f1299df34676fdf57.

This was re-introducing Clang warnings since gboolean is signed.
I should have read the git blame before re-introducing gboolean...
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 024d26ac0cd869826801889f1299df34676fdf57.

This was re-introducing Clang warnings since gboolean is signed.
I should have read the git blame before re-introducing gboolean...
</pre>
</div>
</content>
</entry>
<entry>
<title>fixup: use teco_machine_t::must_undo instead of trying to identify the current state machine</title>
<updated>2024-10-16T08:40:52+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-16T08:40:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=d714bb48a4b8629f6345a28bc21a24537207176b'/>
<id>d714bb48a4b8629f6345a28bc21a24537207176b</id>
<content type='text'>
* The previous solution was not wrong, but unnecessarily complex. We already have a flag
  for exactly this purpose.
* Avoid redundancies by introducing teco_machine_stringbuilding_set_codepage().
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* The previous solution was not wrong, but unnecessarily complex. We already have a flag
  for exactly this purpose.
* Avoid redundancies by introducing teco_machine_stringbuilding_set_codepage().
</pre>
</div>
</content>
</entry>
<entry>
<title>fixed memory corruptions due to undoing the teco_machine_stringbuilding_t::codepage</title>
<updated>2024-10-15T20:33:43+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-15T20:33:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=d556aee67e615b48c25861741d28d103109235e3'/>
<id>d556aee67e615b48c25861741d28d103109235e3</id>
<content type='text'>
* It's contained in teco_machine_main_t which is created per macro call frame.
  So after macro calls, the machine no longer exists.
  It is therefore unsafe to undo its members indiscriminately.
* On the other hand, we must undo the codepage setting when run interactively,
  so it is now only undone when belonging to the commandline macro frame.
* This was actually causing memory corruptions on every fnkeys cursor movement, but never
  caused crashes - probably because the invalid pointers are always pointing to unused
  parts of the C call stack.
* Initially broken in b31b8871.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* It's contained in teco_machine_main_t which is created per macro call frame.
  So after macro calls, the machine no longer exists.
  It is therefore unsafe to undo its members indiscriminately.
* On the other hand, we must undo the codepage setting when run interactively,
  so it is now only undone when belonging to the commandline macro frame.
* This was actually causing memory corruptions on every fnkeys cursor movement, but never
  caused crashes - probably because the invalid pointers are always pointing to unused
  parts of the C call stack.
* Initially broken in b31b8871.
</pre>
</div>
</content>
</entry>
<entry>
<title>fixed memory leak when replacing command lines</title>
<updated>2024-10-15T17:02:50+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-15T17:02:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=7413b9cab2690f7bed6d82e903b0fc08b1590360'/>
<id>7413b9cab2690f7bed6d82e903b0fc08b1590360</id>
<content type='text'>
* this would also leak a few bytes on every of fnkeys.tes' movement commands
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* this would also leak a few bytes on every of fnkeys.tes' movement commands
</pre>
</div>
</content>
</entry>
<entry>
<title>netbsd-curses: fixed the default escape delay</title>
<updated>2024-10-15T08:30:18+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-15T08:30:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=e307e56d5591f844c77425a9e72dca6c1cabd766'/>
<id>e307e56d5591f844c77425a9e72dca6c1cabd766</id>
<content type='text'>
* Apparently, netbsd-curses overwrites the escdelay on initscr() (if $ESCDELAY is not set),
  so we have to apply the default 25ms after screen initialization.
* The info line is not drawn correctly on netbsd-curses, but only on st/simpleterm.
  I assume this is just a shortcoming of the included terminfo entry.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Apparently, netbsd-curses overwrites the escdelay on initscr() (if $ESCDELAY is not set),
  so we have to apply the default 25ms after screen initialization.
* The info line is not drawn correctly on netbsd-curses, but only on st/simpleterm.
  I assume this is just a shortcoming of the included terminfo entry.
</pre>
</div>
</content>
</entry>
<entry>
<title>improved support for braces within loops: warn about unclosed braces and allow breaking from within braces</title>
<updated>2024-10-14T22:46:52+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-14T22:46:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=820f716dd16008eef386f6541fa76dcbac793a9b'/>
<id>820f716dd16008eef386f6541fa76dcbac793a9b</id>
<content type='text'>
For instance, you can now write &lt;23(1;)&gt; without leaving anything on the stack.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
For instance, you can now write &lt;23(1;)&gt; without leaving anything on the stack.
</pre>
</div>
</content>
</entry>
<entry>
<title>fixup b36ff2502ae3b0e18fa862a01fba9cc2c9067e31: fixes pattern match characters after escaped characters</title>
<updated>2024-10-06T10:00:13+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-06T10:00:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=9a25dfdc41048e659a4f6b50f87c8a3ea771b01a'/>
<id>9a25dfdc41048e659a4f6b50f87c8a3ea771b01a</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Gtk UI: support setting and getting clipboards containing null bytes</title>
<updated>2024-10-05T16:27:18+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-05T16:27:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=52d73e8b5d82aba0ec3c1b0efd8b6b0a1ee5b5a2'/>
<id>52d73e8b5d82aba0ec3c1b0efd8b6b0a1ee5b5a2</id>
<content type='text'>
* added TECO_ERROR_CLIPBOARD for all clipboard-related errors
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* added TECO_ERROR_CLIPBOARD for all clipboard-related errors
</pre>
</div>
</content>
</entry>
<entry>
<title>pattern match characters support ^Q/^R now as well</title>
<updated>2024-10-04T19:41:16+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-04T19:41:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=b36ff2502ae3b0e18fa862a01fba9cc2c9067e31'/>
<id>b36ff2502ae3b0e18fa862a01fba9cc2c9067e31</id>
<content type='text'>
* makes it possible, albeit cumbersome, to escape pattern match characters
* For instance, to search for ^Q, you now have to type
  S^Q^Q^Q^Q$.
  To search for ^E you have to type
  S^Q^Q^Q^E$.
  But the last character cannot be typed with carets currently (FIXME?).
  For pattern-only characters, two ^Q should be sufficient as in
  S^Q^Q^X$.
* Perhaps it would be more elegant to abolish the difference between string building
  and pattern matching characters to avoid double quoting.
  But then all string building constructs like ^EQq should operate at the pattern level
  as well (ie. match the contents of register q verbatim instead of being interpreted as a pattern).
  TECOC and TECO-64 don't do that either.
  If we leave everything as it is, at least a new string building construct should be added for
  auto-quoting patterns (analoguous to ^EN and ^E@).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* makes it possible, albeit cumbersome, to escape pattern match characters
* For instance, to search for ^Q, you now have to type
  S^Q^Q^Q^Q$.
  To search for ^E you have to type
  S^Q^Q^Q^E$.
  But the last character cannot be typed with carets currently (FIXME?).
  For pattern-only characters, two ^Q should be sufficient as in
  S^Q^Q^X$.
* Perhaps it would be more elegant to abolish the difference between string building
  and pattern matching characters to avoid double quoting.
  But then all string building constructs like ^EQq should operate at the pattern level
  as well (ie. match the contents of register q verbatim instead of being interpreted as a pattern).
  TECOC and TECO-64 don't do that either.
  If we leave everything as it is, at least a new string building construct should be added for
  auto-quoting patterns (analoguous to ^EN and ^E@).
</pre>
</div>
</content>
</entry>
<entry>
<title>replaced bool completely with gboolean</title>
<updated>2024-09-28T19:10:42+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-09-28T19:10:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=024d26ac0cd869826801889f1299df34676fdf57'/>
<id>024d26ac0cd869826801889f1299df34676fdf57</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
