Re:Interview with TJ DeVries, Neovim core maintainer
by AJRF on Monday September 06, 2021 @01:03PM
(#28435725)
Nothing to ask but just wanted to say you seem like one of the most approachable people in open source. You are creating a great model to follow for developers of all walks of life, thanks for everything you do!
Re:Interview with TJ DeVries, Neovim core maintainer
by jez on Monday September 06, 2021 @01:22PM
(#28435914)
Has Neovim ever considered to a rolling release model?
Where I work, it’s considerably less of a headache to install Homebrew bottles instead of source/HEAD packages. There was a bug in Neovim 0.4 that I ran into every day for years—it was fixed in master but unreleased for a long time. I just had the same thing happen in 0.5.0: there’s a bug, it’s already fixed in master, but I can’t upgrade to HEAD.
The 0.5.0 release was obviously a historic release (tree sitter integration, LSP built-in, lua config engine) but the release was delayed for a long time. I’d love to know the team’s thoughts for or against having some sort of rolling release schedule (or other strategy) to release earlier and/or more frequently.
Re:Interview with TJ DeVries, Neovim core maintainer
by tjdevries on Monday September 06, 2021 @02:01PM
(#28436314)
Rolling release is kind of hard. We want to make sure that we keep our promises that we've set forth in `:help api-contract` and other expectations about semver. We think this is very beneficial for the plugin writing community. It's also hard because sometimes we merge something into master, before a release, and then recognize that a change to an API, an extension, etc. may be necessary for a feature to truly be great. Rolling release can make some of these things very hard.
However, we're hoping to release more often now to prevent this kind of situation.
I'm not 100% the person to talk to about releases, I primarily just try and write code to make Lua more fun to use :)
Side Note: You can install the HEAD of neovim easily with brew. `brew install neovim --HEAD` I think will do that for you. I'm not sure if that's what you mean by source/HEAD packages or not (I have no idea anything about Mac).
Re:Interview with TJ DeVries, Neovim core maintainer
by dfdz on Monday September 06, 2021 @02:24PM
(#28436497)
Hi tjdevries, I have been thinking about switching to neovim from vim.
Do you have any advice/reference for setting up Latex Synctex (Forward and Backwards search) for neovim and evince (on Linux)?
From looking online there seem to be several possible approaches for doing this in neovim (currently in Vim I use an adapted version of evince_dbus.py from the latex gedit latex plugin but it was a pain to get set up!)
Re:Interview with TJ DeVries, Neovim core maintainer
by dfdz on Monday September 06, 2021 @05:58PM
(#28438555)
Just to follow up, my attempts to get vimtex to work unfortunately were unsuccessful. However, along the way reading neovim plugin docs I started to figure out the difference between neovim and vim and was able to get things working via the following process:
Re:Interview with TJ DeVries, Neovim core maintainer
by Karsteski on Monday September 06, 2021 @03:26PM
(#28437051)
Hey TJ, I'm a newb programmer that's switching to Neovim from VS Code. I just want to say thanks for making vim more accessible. You have done great work :)
Re:Interview with TJ DeVries, Neovim core maintainer
by xvilka on Monday September 06, 2021 @10:03PM
(#28440058)
For anyone who wants to help the project - they accept donations via GitHub Sponsors[1], targeting $6k a month to hire a full-time developer, but falling short of it.
Happy to try and answer any questions about the podcast or neovim generally :)
I really appreciate it and hope I can live up to the standard I'm trying to set. Hope you have a really great day!
Where I work, it’s considerably less of a headache to install Homebrew bottles instead of source/HEAD packages. There was a bug in Neovim 0.4 that I ran into every day for years—it was fixed in master but unreleased for a long time. I just had the same thing happen in 0.5.0: there’s a bug, it’s already fixed in master, but I can’t upgrade to HEAD.
The 0.5.0 release was obviously a historic release (tree sitter integration, LSP built-in, lua config engine) but the release was delayed for a long time. I’d love to know the team’s thoughts for or against having some sort of rolling release schedule (or other strategy) to release earlier and/or more frequently.
However, we're hoping to release more often now to prevent this kind of situation.
I'm not 100% the person to talk to about releases, I primarily just try and write code to make Lua more fun to use :)
Side Note: You can install the HEAD of neovim easily with brew. `brew install neovim --HEAD` I think will do that for you. I'm not sure if that's what you mean by source/HEAD packages or not (I have no idea anything about Mac).
Do you have any advice/reference for setting up Latex Synctex (Forward and Backwards search) for neovim and evince (on Linux)?
From looking online there seem to be several possible approaches for doing this in neovim (currently in Vim I use an adapted version of evince_dbus.py from the latex gedit latex plugin but it was a pain to get set up!)
I pinged a buddy of mine to hopefully be able to respond here though!
vimtex works perfectly on neovim (in fact, the main developer uses neovim) and is very well documented
texlab (the latex lsp server) also does build and forward search (although there's a small bug at the moment)
Oh, and backward search needs neovim-remote (\o/ mhinz); just use nvr --remote +"%line" "%file" as backward search command
https://github.com/lervag/vimtex/blob/5d1335d095d11f48a6744f...
(the vimtex dev uses Zathura, so that may be an alternative viewer to look into)
It it great to know that the main developer for vimtex uses neovim.
I will try the neovim/vimtex/zathura combination used by the dev!
sudo dnf install neovim
sudo dnf install python3-neovim
mkdir -p ~/.config/pack/foo/opt/mytex
cd ~/.config/pack/foo/opt/mytex
[download https://github.com/peterbjorgensen/sved/ftplugin]
cp ~/.vimrc ~/.config/nvim/init.vim
add the line "packadd mytex" to init.vim
add the line "alias vim='nvim'" to ~/.bashrc :)
One of us! One of us! One of us! ;)
https://changelog.com/podcast/450
[1] https://github.com/sponsors/neovim