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 does it offer?

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.

Default init message (the clear background is because of my Neovim config, not a GUI decision)

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 -e ".[dev]"
(env) …/nysor$ python -m nysor

It should work just fine in Linux and MacOS. See below for Windows.

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.8:

• fix vsplit / hsplit
• font size with ctrl-+/-
• Improve swarm discover latency

For 0.9:

• FIXME.94 allow logging system to use logger.trace
• allow double-level logging (user selected to terminal, debug to a file if configured)
• docs/2026-08-24-optimizations.md

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:

• 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
• split command bar / messages
  • 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
    • have a pane specifically for "errors"? (what today is a pop-up) https://neovim.io/doc/user/api-ui-events/#ui-cmdline https://neovim.io/doc/user/api-ui-events/#ui-messages

For version 3:

• 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

For version 4:

• 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 git 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

For version 6:

• incorporate the possibility of AIs to read/write code

What about Windows?

Windows is tricky. I want Nysor to run in Windows, but it's not my main platform, and I don't enjoy overcoming the issues there.

We would need a champion to take the project in that platform. Somebody that would want for Nysor to work in Windows and push it to make it possible. Are you that person? Let's talk.

I started this branch that solves the network/process details of running Neovim in Windows, but there are other glitches that need to be understood and fixed. Check that out, and send me a message if you are interested in this endeavour. Thanks in advance!