nysor 0.4__tar.gz

nysor-0.4/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

nysor-0.4/PKG-INFO

@@ -0,0 +1,170 @@
+Metadata-Version: 2.4
+Name: nysor
+Version: 0.4
+Summary: A PyQt GUI for Neovim
+Author-email: Facundo Batista <facundo@taniquetil.com.ar>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/facundobatista/nysor
+Project-URL: Repository, https://github.com/facundobatista/nysor
+Project-URL: Issues, https://github.com/facundobatista/nysor/issues
+Keywords: neovim,gui,pyqt,editor
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: X11 Applications :: Qt
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Text Editors
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyQt6==6.9.1
+Requires-Dist: foffinf==0.1
+Requires-Dist: msgpack==1.1.1
+Requires-Dist: qasync==0.27.1
+Provides-Extra: dev
+Requires-Dist: codespell; extra == "dev"
+Requires-Dist: flake8; extra == "dev"
+Requires-Dist: pydocstyle; extra == "dev"
+Requires-Dist: pytest; extra == "dev"
+Dynamic: license-file
+
+# Welcome to Nysor
+
+Yet another graphical interface for Neovim.
+
+Written in Python, with Qt.
+
+Pronounced similar to "organizer", but without the "orga" and changing the "e" for an "o".
+
+
+# Why another GUI for Neovim?
+
+It's basically a pet project: one aimed to learn about Neovim and how to use it programmatically. But at the same time the idea is to provide a high quality interface for the everyday usage.
+
+
+# What it offers?
+
+Nysor is mainly a GUI with an editor inside. You run it, optionally indicating a file to load, and will edit it using Neovim as backend.
+
+In other words, Nysor does not really *edit* the file, it's Neovim, and Neovim is the one that handlers all your keystrokes and (most of) the mouse actions. Nysor is not an *emulation* of Neovim.
+
+Currently, version 0.1, it's just a window with the editor inside. There is nothing extra so far, but all the basics should work. It may have rough edges, though (there are even two buttons for debugging purposes); see below what to expect in the future.
+
+<div align="center">
+  <img src="media/sshot1.png" alt="Screenshot showing a simple GUI" width="600"/>
+  <p><em>Default init message (the clear background is because of my Neovim config, not a GUI decision)</em></p>
+</div>
+
+## How to run it?
+
+You call it from the project (no packaging yet), but previously you need to create a virtualenv; e.g.:
+
+```
+…/nysor$ python3 -m venv env
+…/nysor$ source env/bin/activate
+(env) …/nysor$ pip install -r requirements.txt
+(env) …/nysor$ python -m nysor
+```
+
+You can indicate it to open a file to edit:
+```
+(env) …/nysor$ python -m nysor myfile.txt
+```
+
+By default, currently, some INFO is sent to the terminal, you can reduce the logs verbosity with `-q/--quiet`, increase it with `-v/--verbose`, or even use `-t/--trace` to see everything that is going one under the hood (specially the interaction with Neovim through the socket).
+
+Nysor will use `nvim` if it's in the PATH, but you can always specify the binary location using `--nvim`.
+
+
+# Roadmap
+
+These are the plans for the future. They are quite informal, the idea is to follow this list, but we can reorder stuff if needed, of if something is requested.
+
+
+## The path to 1.0
+
+The idea is to have a solid editor in one window for version 1.0; there will be not much more functionality than it currently exists, but it should improve in quality.
+
+These are the items lousely grouped to get there:
+
+**For 0.5:**
+
+- present an error window if a `nvim` executable is not Found
+    - include instructions to install it
+    - not yet configurable, but run it with `--nvim`
+- Include the icon, so it's shown in the window decoration
+
+
+**For 0.6:**
+
+- complete "GUI window"
+    - add a very clean menu
+    - File: Exit, About
+    - the About should present name, icon, and versions for Nysor *and* the nvim it's using
+- remove the two debug buttons
+
+
+**For 1.0:**
+
+- Think about "distribution"
+    - upload it to PyPI and check `uvx` and `fades` work to run it
+    - package it with `pyempaq`
+
+
+
+## After 1.0
+
+The path after that is less descriptive. The following are the big items I want to add to the editor in the following versions:
+
+**For version 2:**
+- try to separate, if possible, the command bar from Neovim's grid itself
+    - add better history and ways to search/filter previous commands
+- try to separate, if possible, the windows for messages from the editor
+    - not only from the Neovim *itself* (like `myfile.txt 23L, 10023B written`) but also from plugins, like linters
+    - these windows should be easily resizeable, and with buttons somewhere to turn them on/off
+    - improve error management around "opening a file that was left open previously because of crashing or similar"
+- add a treeview in the left of the window
+    - simple, showing the directory where the process is run
+    - if double click in a file, it should open a new window/tab with the new buffer
+- support multiple buffers open
+    - FIXME.90
+    - switch back and forward clicking on tabs
+    - when going back to a tab, it should check if underneath file changed
+    - support closing properly, each tab or the whole program, asking for the buffers that are not properly saved
+- remove the "debug buttons"
+    - FIXME.91
+
+**For version 3:**
+- it should open more than a file if it's given in the command line
+    - each file should be a separate window in the "right pane zone"
+- double clicking in the tree view should also edit the file
+- when open from a terminal, the layout should change according to the indicated parameters
+    - if it's one or more files, open them as (multiple) windows, without a treeview
+    - if it's a directory, open it with a treeview based in that directory
+        - if this is not the first time the directory is "opened", it should remember which files were previosly open
+    - if nothing is indicated, open it empty, with no treeview
+    - if "`-`" is the parameter, it should handle `stdin`
+        - let's see if Neovim supports through API telling it to open stdin
+        - otherwise just make it work: open a temporary file with content retrieved from `stdin` and tell Neovim to use that
+        - no treeview
+        - FIXME.92
+
+**For version 4:**
+- different Nysor runs should be different processes, but aware of them
+    - if you're trying to open the same file twice, it should not, the other editor should get focus
+- add functionality to the contextual window (when you right click on a word)
+    - FIXME.93
+    - to search that token in all the proyect ... maybe also in the project's virtual env?
+    - to jump to the definition of that word (function, class, module, etc)
+
+**For version 5:**
+- automatically run linters
+    - if the standard ones are in the virtual environment, use them, add decorations for their results
+- minimum github support
+    - decoration of lines added/removed/changed
+- support minimal configuration
+    - overrid automatic detections, like virtualenv directories, linters to run, etc
+    - placement of decoration for line length
+    - scrollbars behaviour (never, always, dynamic)
+    - nvim exec path

nysor-0.4/README.md

@@ -0,0 +1,139 @@
+# Welcome to Nysor
+
+Yet another graphical interface for Neovim.
+
+Written in Python, with Qt.
+
+Pronounced similar to "organizer", but without the "orga" and changing the "e" for an "o".
+
+
+# Why another GUI for Neovim?
+
+It's basically a pet project: one aimed to learn about Neovim and how to use it programmatically. But at the same time the idea is to provide a high quality interface for the everyday usage.
+
+
+# What it offers?
+
+Nysor is mainly a GUI with an editor inside. You run it, optionally indicating a file to load, and will edit it using Neovim as backend.
+
+In other words, Nysor does not really *edit* the file, it's Neovim, and Neovim is the one that handlers all your keystrokes and (most of) the mouse actions. Nysor is not an *emulation* of Neovim.
+
+Currently, version 0.1, it's just a window with the editor inside. There is nothing extra so far, but all the basics should work. It may have rough edges, though (there are even two buttons for debugging purposes); see below what to expect in the future.
+
+<div align="center">
+  <img src="media/sshot1.png" alt="Screenshot showing a simple GUI" width="600"/>
+  <p><em>Default init message (the clear background is because of my Neovim config, not a GUI decision)</em></p>
+</div>
+
+## How to run it?
+
+You call it from the project (no packaging yet), but previously you need to create a virtualenv; e.g.:
+
+```
+…/nysor$ python3 -m venv env
+…/nysor$ source env/bin/activate
+(env) …/nysor$ pip install -r requirements.txt
+(env) …/nysor$ python -m nysor
+```
+
+You can indicate it to open a file to edit:
+```
+(env) …/nysor$ python -m nysor myfile.txt
+```
+
+By default, currently, some INFO is sent to the terminal, you can reduce the logs verbosity with `-q/--quiet`, increase it with `-v/--verbose`, or even use `-t/--trace` to see everything that is going one under the hood (specially the interaction with Neovim through the socket).
+
+Nysor will use `nvim` if it's in the PATH, but you can always specify the binary location using `--nvim`.
+
+
+# Roadmap
+
+These are the plans for the future. They are quite informal, the idea is to follow this list, but we can reorder stuff if needed, of if something is requested.
+
+
+## The path to 1.0
+
+The idea is to have a solid editor in one window for version 1.0; there will be not much more functionality than it currently exists, but it should improve in quality.
+
+These are the items lousely grouped to get there:
+
+**For 0.5:**
+
+- present an error window if a `nvim` executable is not Found
+    - include instructions to install it
+    - not yet configurable, but run it with `--nvim`
+- Include the icon, so it's shown in the window decoration
+
+
+**For 0.6:**
+
+- complete "GUI window"
+    - add a very clean menu
+    - File: Exit, About
+    - the About should present name, icon, and versions for Nysor *and* the nvim it's using
+- remove the two debug buttons
+
+
+**For 1.0:**
+
+- Think about "distribution"
+    - upload it to PyPI and check `uvx` and `fades` work to run it
+    - package it with `pyempaq`
+
+
+
+## After 1.0
+
+The path after that is less descriptive. The following are the big items I want to add to the editor in the following versions:
+
+**For version 2:**
+- try to separate, if possible, the command bar from Neovim's grid itself
+    - add better history and ways to search/filter previous commands
+- try to separate, if possible, the windows for messages from the editor
+    - not only from the Neovim *itself* (like `myfile.txt 23L, 10023B written`) but also from plugins, like linters
+    - these windows should be easily resizeable, and with buttons somewhere to turn them on/off
+    - improve error management around "opening a file that was left open previously because of crashing or similar"
+- add a treeview in the left of the window
+    - simple, showing the directory where the process is run
+    - if double click in a file, it should open a new window/tab with the new buffer
+- support multiple buffers open
+    - FIXME.90
+    - switch back and forward clicking on tabs
+    - when going back to a tab, it should check if underneath file changed
+    - support closing properly, each tab or the whole program, asking for the buffers that are not properly saved
+- remove the "debug buttons"
+    - FIXME.91
+
+**For version 3:**
+- it should open more than a file if it's given in the command line
+    - each file should be a separate window in the "right pane zone"
+- double clicking in the tree view should also edit the file
+- when open from a terminal, the layout should change according to the indicated parameters
+    - if it's one or more files, open them as (multiple) windows, without a treeview
+    - if it's a directory, open it with a treeview based in that directory
+        - if this is not the first time the directory is "opened", it should remember which files were previosly open
+    - if nothing is indicated, open it empty, with no treeview
+    - if "`-`" is the parameter, it should handle `stdin`
+        - let's see if Neovim supports through API telling it to open stdin
+        - otherwise just make it work: open a temporary file with content retrieved from `stdin` and tell Neovim to use that
+        - no treeview
+        - FIXME.92
+
+**For version 4:**
+- different Nysor runs should be different processes, but aware of them
+    - if you're trying to open the same file twice, it should not, the other editor should get focus
+- add functionality to the contextual window (when you right click on a word)
+    - FIXME.93
+    - to search that token in all the proyect ... maybe also in the project's virtual env?
+    - to jump to the definition of that word (function, class, module, etc)
+
+**For version 5:**
+- automatically run linters
+    - if the standard ones are in the virtual environment, use them, add decorations for their results
+- minimum github support
+    - decoration of lines added/removed/changed
+- support minimal configuration
+    - overrid automatic detections, like virtualenv directories, linters to run, etc
+    - placement of decoration for line length
+    - scrollbars behaviour (never, always, dynamic)
+    - nvim exec path

nysor-0.4/nysor/__main__.py

@@ -0,0 +1,11 @@
+# Copyright 2025-2026 Facundo Batista
+# Licensed under the Apache v2 License
+# For further info, check https://github.com/facundobatista/nysor
+
+"""Init file to allow project's execution as a module."""
+
+import sys
+
+from nysor import main
+
+sys.exit(main.start())

nysor-0.4/nysor/logical_lines.py

@@ -0,0 +1,107 @@
+# Copyright 2025-2026 Facundo Batista
+# Licensed under the Apache v2 License
+# For further info, check https://github.com/facundobatista/nysor
+
+"""Logical lines."""
+
+import logging
+from dataclasses import dataclass
+
+from PyQt6.QtGui import QColor
+
+logger = logging.getLogger(__name__)
+
+
+@dataclass
+class CharUnderline:
+    """Represent the underlyne style of a single char."""
+    color: QColor
+    style: str  # "underline", "undercurl", "underdouble", "underdotted", "underdashed"
+
+
+@dataclass
+class CharFormat:
+    """Represent the overall format of a single char."""
+    foreground: QColor
+    background: QColor
+    strikethrough: bool = False
+    italic: bool = False
+    bold: bool = False
+    underline: CharUnderline | None = None
+
+
+@dataclass
+class LogicalChar:
+    """Represent a logical character with its format and wide indication."""
+
+    char: str
+    format: CharFormat
+    is_wide: bool = False
+
+    def __hash__(self):
+        return hash((self.char, self.is_wide))
+
+    def __eq__(self, other):
+        return (self.char, self.is_wide) == (other.char, other.is_wide)
+
+
+class LogicalLines:
+    """Hold the lines to show in the grid."""
+
+    def __init__(self, q_rows, q_cols, fmt):
+        self._lines = {
+            idx: [LogicalChar(" ", fmt) for _ in range(q_cols)] for idx in range(q_rows)
+        }
+
+    @classmethod
+    def empty(cls):
+        """Return an empty line."""
+        return cls(0, 0, None)
+
+    def get(self, row):
+        """Return the logical line for the indicated row."""
+        return self._lines.get(row)
+
+    def add(self, row, col, textinfo):
+        """Add text info to the grid."""
+        # expand the textinfo so we have one format per character, to keep our logical grid
+        expanded = []
+        for text, fmt in textinfo:
+            if text is None:
+                # special "char" that comes after others to indicate those are width: we flag
+                # the previous item and keep the position with None for the slice assignment
+                # below to work correctly
+                expanded[-1].is_wide = True
+                expanded.append(None)
+            else:
+                expanded.extend(LogicalChar(char, fmt) for char in text)
+
+        # it's fine to create new lines in the map, because gaps are created when scrolling
+        prvline = self._lines.setdefault(row, [])
+
+        if col > len(prvline):
+            raise ValueError("Trying to write outside the line; needs to rethink model!!!")
+        prvline[col: col + len(expanded)] = expanded
+
+    def scroll_vertical(self, top, bottom, delta):
+        """Scroll vertically some lines in the grid."""
+        if abs(delta) >= bottom - top:
+            raise ValueError("Overflow scrolling; not supported yet")
+
+        if delta > 0:
+            # goes up; move N lines up and then remove "hole"
+            for idx in range(top + delta, bottom):
+                self._lines[idx - delta] = self._lines[idx]
+            for idx in range(bottom - delta, bottom):
+                del self._lines[idx]
+
+        elif delta < 0:
+            # goes down; move N lines down and then remove "hole"
+            for idx in reversed(range(top, bottom + delta)):
+                self._lines[idx - delta] = self._lines[idx]
+            for idx in range(top, top - delta):
+                del self._lines[idx]
+
+        else:
+            logger.warning("Called scroll vertical with delta=0, shouldn't happen")
+            return

nysor-0.4/nysor/logtools.py

@@ -0,0 +1,46 @@
+# Copyright 2026 Facundo Batista
+# Licensed under the Apache v2 License
+# For further info, check https://github.com/facundobatista/nysor
+
+"""Tools related to logging."""
+
+import logging
+import sys
+
+import foffinf
+
+logger = logging.getLogger(__name__)
+
+_TRACE_LEVEL = 5
+LOG_LEVELS = {
+    "quiet": (logging.WARNING, "Set logging to be quiet."),
+    "verbose": (logging.DEBUG, "Set logging to verbose."),
+    "trace": (_TRACE_LEVEL, "Set logging for tracing (beware, there may be too many messages)."),
+    None: (logging.INFO, None),  # default no-option-set
+}
+
+
+def logsetup(selected_level):
+    """Prepare all logging."""
+    # add trace level to logging
+    logging.addLevelName(_TRACE_LEVEL, "TRACE")
+    logging.TRACE = _TRACE_LEVEL
+
+    # config
+    logging.basicConfig(
+        format='%(asctime)s.%(msecs)03d %(levelname)-5s %(message)s',
+        datefmt='%H:%M:%S', stream=sys.stdout)
+
+    # set proper level to the whole app
+    level, _ = LOG_LEVELS[selected_level]
+    logging.getLogger("nysor").setLevel(level)
+
+    # use new format styles
+    foffinf.formatize("nysor", scatter=True)
+
+
+def log_notdone(msg, **items):
+    """Nicely log a not implemented error."""
+    reprs = [f"{k}={{!r}}" for k in items.keys()]
+    fullmsg = f"Not Implemented! {msg}: {' '.join(reprs)}"
+    logger.error(fullmsg, *items.values())