Nvui: A NeoVim GUI written in C++ and Qt

Post by 7kay » Mon, Aug 30, 2021, 2:52 PM UTC

da39a3ee wrote: post #87

WhyNotHugo wrote: post #85

I don't quite get what the advantage / goal of this is. I find the fact that neovim runs in a terminal an advantage; they share font configuration and colour and other settings, and I can quickly jump in and out of nvim from a terminal. Having it run in a separate window just means I now have an extra window lying around (the terminal where I typed `nvui`). And smooth scrolling works on regular neovim with https://gi…

> the terminal where I typed `nvui` Maybe you'll find some advantages in having a long-running editor process, rather than starting one from the terminal whenever you want to edit? For example, ctr+click on a compiler error message in the terminal could open the file at the correct line in the (already running) nvui process.

Post by jcelerier » Mon, Aug 30, 2021, 2:58 PM UTC

MontyCarloHall wrote: post #97

chrisseaton wrote: post #94

Earlier quoted context omitted.

You mean do all the text rendering yourself and stream the image to the terminal? At that point why use a terminal rather than a graphics window?

Remote access is the big one. It’s 2021 and ssh somehow still remains by far the most robust protocol for remote interaction. X forwarding is awful, and VNC and its ilk require forwarding an entire desktop, which is inconvenient if you’re just interested in working in a single application, or having your client machine do its own window management. I agree, it’s an ironic state of affairs that in the era of cloud com…

Post by emi2k01 » Mon, Aug 30, 2021, 3:17 PM UTC

yawaramin wrote: post #103

chrismorgan wrote: post #62

Earlier quoted context omitted.

The author deliberately added the files to the repository. That’s (part of) the problem. .gitignore is about saying “I don’t want to add matching files to the repository, so stop telling me they’re not in the repository”.

What problem? It’s their repo—they can add what they like…

  git clone $URL

Post by maccam94 » Mon, Aug 30, 2021, 3:30 PM UTC

alpaca128 wrote: post #74

ur-whale wrote: post #68

Earlier quoted context omitted.

There was quite a few, but off the top of my head: 1. searching for stuff with / jumps prematurely to destination, drives me nuts. 2. I have most "smart" features (auto-indent type stuff) disabled for C++ mode in my .vimrc, which works fine in vim but is completely ignored by neovim. It requires futzing around with post/pre loading of plugins, which - 1.who has the time to do these things 2. makes for incompatible in…

Ah, coincidentally my preferences make the first two non-issues: I always set Vim to jump to the first search result in realtime because that lets me take a glance at another part of the file and then immediately jump back with Esc. So that way I didn't notice this apparently became a default setting in NeoVim. Which is still a weird thing and shouldn't happen imho. And I always have all kinds of smart features disab…

Post by da39a3ee » Mon, Aug 30, 2021, 4:23 PM UTC

sagarm wrote: post #95

da39a3ee wrote: post #89

Earlier quoted context omitted.

If you run your editor in a terminal, how do you do things like ctrl+click on a compiler error in the terminal and have the file opened in your editor at the correct line?

People who prefer the terminal don't click on things much. Vanilla Vi users would use :make to populate the location list, and then :cn or :cp to navigate back and forth. :cope to open up the quick fix window where you can use all your regular VI keybindings to navigate. Enter opens the location under the cursor in your previous VIM split. There are also plenty of plugins that add inline diagnostics. It's common to u…