<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sciteco/freebsd/pkg-plist, branch v2.3.0</title>
<subtitle>Scintilla-based Text Editor and COrrector</subtitle>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/'/>
<entry>
<title>Curses: don't install PNG icons</title>
<updated>2024-12-23T01:07:44+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-12-23T01:07:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=e5d1253d363a209ecd1288278808e38ac87b34d9'/>
<id>e5d1253d363a209ecd1288278808e38ac87b34d9</id>
<content type='text'>
* They are used at runtime only by the GTK port.
* Their existence can cause problems if OS-specific build systems
  have to clean these files from the staging directory afterwards.
  This was the case on FreeBSD where the committer refused to remove
  these files after installation.
  In the official FreeBSD port, we therefore currently ship the
  PNG icons unnecessarily.
* They are now installed and shipped only on GTK builds.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* They are used at runtime only by the GTK port.
* Their existence can cause problems if OS-specific build systems
  have to clean these files from the staging directory afterwards.
  This was the case on FreeBSD where the committer refused to remove
  these files after installation.
  In the official FreeBSD port, we therefore currently ship the
  PNG icons unnecessarily.
* They are now installed and shipped only on GTK builds.
</pre>
</div>
</content>
</entry>
<entry>
<title>freebsd port: synced with the version in FreeBSD ports</title>
<updated>2024-12-17T18:45:56+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-12-17T18:45:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=d8f747eea898717f96d8328e5ee52e17dfb37237'/>
<id>d8f747eea898717f96d8328e5ee52e17dfb37237</id>
<content type='text'>
Rodrigo Osorio re-included the PNGs even for sciteco-curses.
Should be fixed at the Autoconf-level, by only installing the PNGs on GTK.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Rodrigo Osorio re-included the PNGs even for sciteco-curses.
Should be fixed at the Autoconf-level, by only installing the PNGs on GTK.
</pre>
</div>
</content>
</entry>
<entry>
<title>implemented Scintilla lexer for SciTECO code, i.e. TECO syntax highlighting</title>
<updated>2024-12-12T21:58:14+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-12-09T09:58:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=244a54a18b7db6af177c9d10f3224772f08d7484'/>
<id>244a54a18b7db6af177c9d10f3224772f08d7484</id>
<content type='text'>
* this works by embedding the SciTECO parser and driving it always (exclusively)
  in parse-only mode.
* A new teco_state_t::style determines the Scintilla style for any character
  accepted in the given state.
* Therefore, the SciTECO lexer is always 100% exact and corresponds to the current
  SciTECO grammer - it does not have to be maintained separately.
  There are a few exceptions and tweaks, though.
* The contents of curly-brace escapes (`@^Uq{...}`) are rendered as ordinary
  code using a separate parser instance.
  This can be disabled with the lexer.sciteco.macrodef property.
  Unfortunately, SciTECO does not currently allow setting lexer properties (FIXME).
* Labels and comments are currently styled the same.
  This could change in the future once we introduce real comments.
* Lexers are usually implemented in C++, but I did not want to draw in C++.
  Especially not since we'd have to include parser.h and other SciTECO headers,
  that really do not want to keep C++-compatible.
  Instead, the lexer is implemented "in the container".
  @ES/SCI_SETILEXER/sciteco/ is internally translated to SCI_SETILEXER(NULL)
  and we get Scintilla notifications when styling the view becomes necessary.
  This is then centrally forwarded to the teco_lexer_style() which
  uses the ordinary teco_view_ssm() API for styling.
* Once the command line becomes a Scintilla view even on Curses,
  we can enabled syntax highlighting of the command line macro.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* this works by embedding the SciTECO parser and driving it always (exclusively)
  in parse-only mode.
* A new teco_state_t::style determines the Scintilla style for any character
  accepted in the given state.
* Therefore, the SciTECO lexer is always 100% exact and corresponds to the current
  SciTECO grammer - it does not have to be maintained separately.
  There are a few exceptions and tweaks, though.
* The contents of curly-brace escapes (`@^Uq{...}`) are rendered as ordinary
  code using a separate parser instance.
  This can be disabled with the lexer.sciteco.macrodef property.
  Unfortunately, SciTECO does not currently allow setting lexer properties (FIXME).
* Labels and comments are currently styled the same.
  This could change in the future once we introduce real comments.
* Lexers are usually implemented in C++, but I did not want to draw in C++.
  Especially not since we'd have to include parser.h and other SciTECO headers,
  that really do not want to keep C++-compatible.
  Instead, the lexer is implemented "in the container".
  @ES/SCI_SETILEXER/sciteco/ is internally translated to SCI_SETILEXER(NULL)
  and we get Scintilla notifications when styling the view becomes necessary.
  This is then centrally forwarded to the teco_lexer_style() which
  uses the ordinary teco_view_ssm() API for styling.
* Once the command line becomes a Scintilla view even on Curses,
  we can enabled syntax highlighting of the command line macro.
</pre>
</div>
</content>
</entry>
<entry>
<title>updated FreeBSD port for v2.1.0 release</title>
<updated>2024-10-16T16:30:18+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-10-16T16:30:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=57e7dc1219dcde7c9ca7628f16d78acdf1fc848f'/>
<id>57e7dc1219dcde7c9ca7628f16d78acdf1fc848f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>FreeBSD package: add the git.tes lexer config</title>
<updated>2024-09-15T09:30:28+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-09-15T09:30:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=909a4a6657b0912aee6435bff15ef3d054aa077e'/>
<id>909a4a6657b0912aee6435bff15ef3d054aa077e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>added troff/nroff lexer</title>
<updated>2024-08-18T16:48:06+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2024-08-18T16:34:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=bbcf801ddfd3eb50203518c130beb400de7ca53f'/>
<id>bbcf801ddfd3eb50203518c130beb400de7ca53f</id>
<content type='text'>
* This is optimized for Groff, but works for Heirloom Troff and Neatroff as well.
  Currently, the Heirloom and Neatroff requests are just added ontop of the Groff
  ones. Theoretically, we could also try to separate the keyword lists into
  a base K&amp;R set with Groff, Heirloom and Neatroff ontop.
* The lexer necessarily has many restrictions, as Troff is fundamentally unparseable
  (like classic TECO) and needs a lot of per-request knowledge.
* The "*.mm" extension has been removed from the lexers/cpp.tes.
  I don't know what language this was for, and I prefer `*.mm` files
  to be considered Troff.
* Temporarily changed the lexilla submodule URL.
  The corresponding Lexila lexer is in the process of being upstreamed.
  Once it is, I will probably revert the submodule to the official repository,
  as the "troff" branch is not stable (can be rebased).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* This is optimized for Groff, but works for Heirloom Troff and Neatroff as well.
  Currently, the Heirloom and Neatroff requests are just added ontop of the Groff
  ones. Theoretically, we could also try to separate the keyword lists into
  a base K&amp;R set with Groff, Heirloom and Neatroff ontop.
* The lexer necessarily has many restrictions, as Troff is fundamentally unparseable
  (like classic TECO) and needs a lot of per-request knowledge.
* The "*.mm" extension has been removed from the lexers/cpp.tes.
  I don't know what language this was for, and I prefer `*.mm` files
  to be considered Troff.
* Temporarily changed the lexilla submodule URL.
  The corresponding Lexila lexer is in the process of being upstreamed.
  Once it is, I will probably revert the submodule to the official repository,
  as the "troff" branch is not stable (can be rebased).
</pre>
</div>
</content>
</entry>
<entry>
<title>FreeBSD port: fixed the LEXILLA option</title>
<updated>2023-07-23T11:08:53+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2023-07-23T11:08:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=fe62b2451ac200f846a5bae1d08ec9c3201e26c9'/>
<id>fe62b2451ac200f846a5bae1d08ec9c3201e26c9</id>
<content type='text'>
* The lexer scripts are not installed if the LEXILLA option is disabled,
  so they need to be excluded from pkg-plist.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* The lexer scripts are not installed if the LEXILLA option is disabled,
  so they need to be excluded from pkg-plist.
</pre>
</div>
</content>
</entry>
<entry>
<title>added FreBSD port (for ports tree)</title>
<updated>2023-07-02T12:15:00+00:00</updated>
<author>
<name>Robin Haberkorn</name>
<email>robin.haberkorn@googlemail.com</email>
</author>
<published>2023-07-02T12:15:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.fmsbw.de/sciteco/commit/?id=69b4bbb8341cfda5d8456ccbf951034d63e4340c'/>
<id>69b4bbb8341cfda5d8456ccbf951034d63e4340c</id>
<content type='text'>
* it is supposed to be mainstreamed, but this did not yet happen
* even if it will eventually become part of the ports tree, I won't
  have access to this repo and could not keep it up to date.
  But I can keep this copy here up to date and it can serve as an
  upstream source for the ports tree maintainer.
* Also, it can be used to build FreeBSD binary packages even now
  without being part of the official ports tree.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* it is supposed to be mainstreamed, but this did not yet happen
* even if it will eventually become part of the ports tree, I won't
  have access to this repo and could not keep it up to date.
  But I can keep this copy here up to date and it can serve as an
  upstream source for the ports tree maintainer.
* Also, it can be used to build FreeBSD binary packages even now
  without being part of the official ports tree.
</pre>
</div>
</content>
</entry>
</feed>
