<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sciteco/lib/lexers, 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>SciTECO lexer: braces and two-character operators are now actually styled as operators</title>
<updated>2025-12-11T14:13:09+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-12-10T01:15:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=376c62bc63870fa1121548fc8b53271c21ed79a6'/>
<id>376c62bc63870fa1121548fc8b53271c21ed79a6</id>
<content type='text'>
* For consistency with other lexers, like the C/C++ lexer.
* `^*`, `^/` and `^#` are also true operators and shouldn't be styled
  as regular commands.
  This required introducing a new operator style (3).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* For consistency with other lexers, like the C/C++ lexer.
* `^*`, `^/` and `^#` are also true operators and shouldn't be styled
  as regular commands.
  This required introducing a new operator style (3).
</pre>
</div>
</content>
</entry>
<entry>
<title>refactored some lexer configurations to make them more pleasurable to look at</title>
<updated>2025-11-19T00:19:49+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-11-19T00:19:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=e06e7ab1ee41aeff9e29f43de47ac25eef474808'/>
<id>e06e7ab1ee41aeff9e29f43de47ac25eef474808</id>
<content type='text'>
* 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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* 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.
</pre>
</div>
</content>
</entry>
<entry>
<title>updated Scintilla: tabs in command lines and SciTECO buffers are now rendered as "TAB" without any indentation</title>
<updated>2025-11-12T00:05:52+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-11-11T23:43:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=f5ebfce42ded9c146487c02f01f1e335e789084e'/>
<id>f5ebfce42ded9c146487c02f01f1e335e789084e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>render tabs as "TAB" in the command-line and in SciTECO macros</title>
<updated>2025-11-02T22:21:21+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>rhaberkorn@fmsbw.de</email>
</author>
<published>2025-11-02T22:21:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=1391e9c6ea1f9bef965f96e70f4e27141abcb5cd'/>
<id>1391e9c6ea1f9bef965f96e70f4e27141abcb5cd</id>
<content type='text'>
* 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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* 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.
</pre>
</div>
</content>
</entry>
<entry>
<title>YAML lexer: default to 2 character soft tabs</title>
<updated>2025-08-13T17:49:36+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-08-13T17:49:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=a4cdec021de715d865aed26b2b7d8ad7768c2dc8'/>
<id>a4cdec021de715d865aed26b2b7d8ad7768c2dc8</id>
<content type='text'>
Hard tabs would even cause YAML syntax errors.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Hard tabs would even cause YAML syntax errors.
</pre>
</div>
</content>
</entry>
<entry>
<title>added LaTeX lexer config</title>
<updated>2025-06-02T23:13:20+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-06-02T08:38:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=bf4ce2f28a5d4cc3f1f4a7a1d2450e6893ff5d7b'/>
<id>bf4ce2f28a5d4cc3f1f4a7a1d2450e6893ff5d7b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>&lt;EI&gt; has been repurposed and is the macro file inclusion (indirect file) command now</title>
<updated>2025-05-24T14:22:52+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-05-24T13:24:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=6e3da17a2fae11af9ae00d9b59bd0d752022e16b'/>
<id>6e3da17a2fae11af9ae00d9b59bd0d752022e16b</id>
<content type='text'>
* Improves DEC TECO-11 compatibility.
* &lt;EM&gt; is still supported as a synonym, but considered deprecated and is no longer documented.
  A warning is printed when invoked.
  It can be repurposed at any time in the future.
* `EI$` is not yet supported.
  I am unsure whether this makes any sense.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Improves DEC TECO-11 compatibility.
* &lt;EM&gt; is still supported as a synonym, but considered deprecated and is no longer documented.
  A warning is printed when invoked.
  It can be repurposed at any time in the future.
* `EI$` is not yet supported.
  I am unsure whether this makes any sense.
</pre>
</div>
</content>
</entry>
<entry>
<title>python lexer: fixed block comment styling</title>
<updated>2025-05-15T22:46:49+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-05-15T22:46:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=02cdecf47c8dc430bd4b80eb1377a89b94c990f9'/>
<id>02cdecf47c8dc430bd4b80eb1377a89b94c990f9</id>
<content type='text'>
Also, unterminated strings are highlighted with the "error" color now.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Also, unterminated strings are highlighted with the "error" color now.
</pre>
</div>
</content>
</entry>
<entry>
<title>implemented email and git lexer folding</title>
<updated>2025-05-01T19:59:31+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-05-01T19:59:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=d734f9904bbe0ba33dd86083e44d89cf2da3cbb2'/>
<id>d734f9904bbe0ba33dd86083e44d89cf2da3cbb2</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Gtk: monospaced sections in womanpages now respect lexer.font and variable-width font is configurable via lexer.woman.font (refs #34)</title>
<updated>2025-04-22T17:50:48+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2025-04-22T17:50:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=93d3cbd390e65576d0c8740233b0a7569d9bdd89'/>
<id>93d3cbd390e65576d0c8740233b0a7569d9bdd89</id>
<content type='text'>
* grosciteco was just hardcoding "Monospace", regardless of what was configured via lexer.font in ~/.teco_ini
* The variable-width font used for ordinary "womanpage" body texts was hardcoded to "Serif".
  It is now configurable via the lexer.woman.font register.
* There is a difference, though:
  lexer.font has no default value and must therefore be checked everywhere.
  This is so you can set it even before munging lexer.tes.
  lexer.woman.font however has a default (Serif), so it can only be overridden after
  munging lexer.tes.
  Perhaps it would be easier and more consistent to have a default for lexer.font as well.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* grosciteco was just hardcoding "Monospace", regardless of what was configured via lexer.font in ~/.teco_ini
* The variable-width font used for ordinary "womanpage" body texts was hardcoded to "Serif".
  It is now configurable via the lexer.woman.font register.
* There is a difference, though:
  lexer.font has no default value and must therefore be checked everywhere.
  This is so you can set it even before munging lexer.tes.
  lexer.woman.font however has a default (Serif), so it can only be overridden after
  munging lexer.tes.
  Perhaps it would be easier and more consistent to have a default for lexer.font as well.
</pre>
</div>
</content>
</entry>
</feed>
