neovim-qt
i3
neovim-qt | i3 | |
---|---|---|
19 | 200 | |
1,773 | 9,079 | |
- | 1.4% | |
7.4 | 7.6 | |
about 2 months ago | 8 days ago | |
C++ | C | |
ISC License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
neovim-qt
-
Neovide – a simple, no-nonsense, cross-platform GUI for Neovim
While we are on the subject, there's also neovim-qt: https://github.com/equalsraf/neovim-qt
-
Why do I get this invalid text height error message on startup?
There's an issue here about "Invalid Font Height" but It seems already fixed.
-
Does anyone have an example of a Neovide lua configuration?
Otherwise it's recommended to do it on UIEnter
-
Why keeps you using vim vs neovim?
:X, for one, which was rejected for idiotic reasons. I was also stupid errors from my vimrc, from bugs that were closed without fixing. Just no point trying to figure out how to get Neovim to behave like Vim when I already have Vim. *shrug*
-
linux c++ devs, what does your dev environment look like?
Neovim in tmux, or neovim-qt if I don't need to be able to attach to the session remotely. I occasionally bounce back to Emacs, but that's becoming less often now that the TreeSitter and LSP plugins for Neovim have gotten so good. All of that lives in an Xorg session managed by i3. Docs live in zeal.
- :menu doesnt work in neovim
-
AltGr + <key> wont print out ' [ '
So apparently this is an open issue on github, hopefully it gets solved. At least I know its not my computer doing weird things
-
What terminal emulator do you use?
I prefer using neovim in a ui most of the time. Neovim-Qt served me quite well. For ligatures you have to use the latest release but it is easy to compile and install.
- "Firacode NF" reports bad fixed pitch metrics.
- Gui detect when has('gui_running') equals 0 · Issue #219 · equalsraf/neovim-qt
i3
-
Show HN: Chrome Reaper
While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:
https://github.com/i3/i3/issues/4353
-
Firefox 121 defaults to Wayland on Linux
> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).
Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393
It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."
It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.
But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.
The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.
-
"We understand" ;)
This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.
-
what machines have you used for development, and what do you prefer?
I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.
-
The future of /r/i3wm
Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.
- while in i3wm, krita dockers move downwards a bit each time they're spawned - how do I fix this?
- i3wm-like window switching for Windows
-
egui_overlay - A transparent Overlay window where you can only click the "egui parts"
for example, take i3. https://github.com/i3/i3/issues/4478
- How to start on a Linux desktop environment?
-
Machine for pentesting and general use?
For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it
What are some alternatives?
neovide - No Nonsense Neovim Client in Rust
sway - i3-compatible Wayland compositor
neovim - Vim-fork focused on extensibility and usability
awesome - awesome window manager
nvui - A modern frontend for Neovim.
bspwm - A tiling window manager based on binary space partitioning
goneovim - A GUI frontend for neovim.
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
firenvim - Embed Neovim in Chrome, Firefox & others.
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
instant.nvim - collaborative editing in Neovim using built-in capabilities
tmux - tmux source code