Comment by petcat
1 month ago
I love the resurgence of TUI apps, but I wonder what the definition of "modern TUI" means in these cases. Does it basically mean just not using curses?
1 month ago
I love the resurgence of TUI apps, but I wonder what the definition of "modern TUI" means in these cases. Does it basically mean just not using curses?
It means it has a dependency on X11.
That has nothing to do with the UI framework. The X11 dependency comes as part of the clipboard integration (which I'd argue should be optional or even removed). Still, I wouldn't call it modern if Wayland is outright not supported.
I think this is only a problem when building from source, right? It is indeed because of the dependency on https://github.com/golang-design/clipboard.
I hesitated a bit bringing in this feature. On one hand, I really like to have clipboard support, on the other hand, I don't like that it requires you to change from static to dynamic linking (and have the x11 dependency).
Maybe I could write an install.sh script for installation that detects the OS and fetches the correct version/tarball from the Github release.
2 replies →
What's modern about Wayland?
Yikes, so it's a "TUI" app... that still requires a display server? So I can't run this TUI over SSH or a virtual terminal. Wondering what the point of a tui is that still requires a gui environment to run?
Sorry, I was unhelpfully flippant. You totally can, and I don't want to distract from the great app that has been shared. This bug was just a compile time issue, which needed X libs to bake in clipboard support which is optional at runtime.
Just released version v0.2.1 eliminating the need for CGO, thanks for your contribution!
this stopped me from go installing it too on nixos. I'm not gonna put the effort in to run it.
There should be a build tag to disable clipboard, that'd be the easiest way around this.
Same, I also had the same issue on NixOS :)