[Feature]: Support for VimR and neovide

[vlaw]

Feature motivation

Since LunarVim uses a custom directory (~/.local/share/lunarvim/lvim), the LunarVim configuration cannot be loaded when opening vimr (a Neovim GUI for macOS) directly.
Even I copy it into ~/.config/nvim, it doesn't work,
because the path has been remove from packpath and runtimepath

https://github.com/ChristianChiarulli/LunarVim/blob/7cd03ff4e332e1427497b54d5ca8b037afbc0982/init.lua#L2
https://github.com/ChristianChiarulli/LunarVim/blob/7cd03ff4e332e1427497b54d5ca8b037afbc0982/init.lua#L8

PS. the command vimr --nvim -u ~/.local/share/lunarvim/lvim/init.lua --cmd "set runtimepath+=~/.local/share/lunarvim/lvim" works fine.

Describe the expected solution

No response

Describe the alternatives you've considered

an installation switch option to choose directory between ~/.local/share/lunarvim/lvim and ~/.config/nvim ?

Additional context

No response

[sa-mendez]

I second this. I use neovide, and would like to be able to just run with the lunarvim setup by default.

I actually ended up getting this to work by changing a few paths in a few of the files (in lunarvim 0.5.1 release), but the moment I get the next release, I know I will have to do some merges. It would be nice to have user configurable root, so that some of us that just want to use lunarvim full-time, can do so without running a different executable (lvim) and/or aliasing nvim.

[rebuilt]

I actually ended up getting this to work by changing a few paths in a few of the files (in lunarvim 0.5.1 release), but the moment I get the next release, I know I will have to do some merges. It would be nice to have user configurable root, so that some of us that just want to use lunarvim full-time, can do so without running a different executable (lvim) and/or aliasing nvim.

Does this launch neovide correctly for you (without the altering of paths?)

neovide -- -u ~/.local/share/lunarvim/lvim/init.lua --cmd "set runtimepath+=~/.local/share/lunarvim/lvim"

[kylo252]

PS. the command vimr --nvim -u ~/.local/share/lunarvim/lvim/init.lua --cmd "set runtimepath+=~/.local/share/lunarvim/lvim" works fine.

By the way, if that command works for you then you can add this shell function to your bashrc/zshrc

function lvimr(){
	vimr --nvim -u ~/.local/share/lunarvim/lvim/init.lua --cmd "set runtimepath+=~/.local/share/lunarvim/lvim" "@"
}

It would still take arguments like any typical vimr invocation. You can even have autocomplete for zsh, assuming vimr supports it, with something like this:

compdef _vimr lvimr

[vlaw]

PS. the command vimr --nvim -u ~/.local/share/lunarvim/lvim/init.lua --cmd "set runtimepath+=~/.local/share/lunarvim/lvim" works fine.

By the way, if that command works for you then you can add this shell function to your bashrc/zshrc

function lvimr(){

	vimr --nvim -u ~/.local/share/lunarvim/lvim/init.lua --cmd "set runtimepath+=~/.local/share/lunarvim/lvim" "@"

}

It would still take arguments like any typical vimr invocation. You can even have autocomplete for zsh, assuming vimr supports it, with something like this:

compdef _vimr lvimr

thanks.

BUT what I mean is there are so many cases people want to open the GUI application from GUI environment, and get lunarVim loaded automatically (I guess so IMHO) 😀
And my case is, I set VimR as my default text editor, when I open a text file from Finder, VimR can't load luarvim any more😔

[sa-mendez]

I actually ended up getting this to work by changing a few paths in a few of the files (in lunarvim 0.5.1 release), but the moment I get the next release, I know I will have to do some merges. It would be nice to have user configurable root, so that some of us that just want to use lunarvim full-time, can do so without running a different executable (lvim) and/or aliasing nvim.

Does this launch neovide correctly for you (without the altering of paths?)

neovide -- -u ~/.local/share/lunarvim/lvim/init.lua --cmd "set runtimepath+=~/.local/share/lunarvim/lvim"

I have not tried doing that, but if I did I would still have to alias it, or create a function (as was suggested earlier). By having the paths (really the root) be configurable, there would be no need for that. Also, it would basically have any GUI vim application (such as neovide, or VimR) just work out of the box.

I realize that this is perhaps no longer the direction that lunarvim wants to go in (though pre-0.5, it did work this way), and that I can always just grab the latest code and manually update the paths in the code myself. But it would be nice if that flexibility was re-introduced.

[rebuilt]

And my case is, I set VimR as my default text editor, when I open a text file from Finder, VimR can't load luarvim any morepensive

If you use the code from above. Also set your editor to lvimr. That should make finder use this alias.

[vlaw]

And my case is, I set VimR as my default text editor, when I open a text file from Finder, VimR can't load luarvim any morepensive

If you use the code from above. Also set your editor to lvimr. That should make finder use this alias.

As far as I know, changing the default app needs the bundle ID of an app, not a function in shell,

$ duti -x .md
VimR
/Applications/VimR.app
com.qvacua.VimR

Can you tell me more details on how to do it? Many thanks~

[rebuilt]

Can you tell me more details on how to do it? Many thanks~

Ah, sorry. I'm misleading you. That will only work from the command line, not finder.

[kylo252]

I'm not sure about osx, but on Linux you can just add an entry like this one here and give it any flags you want for Exec

LunarVim/utils/desktop/lvim.desktop

Lines 1 to 13 in 2345d8c

	[Desktop Entry]
	Name=LunarVim
	GenericName=Text Editor
	Comment=An IDE layer for Neovim with sane defaults. Completely free and community driven.
	TryExec=lvim
	Exec=lvim %F
	Terminal=false
	Type=Application
	Keywords=Text;editor;
	Icon=nvim
	Categories=Utility;TextEditor;
	StartupNotify=false
	MimeType=text/english;text/plain;text/x-makefile;text/x-c++hdr;text/x-c++src;text/x-chdr;text/x-csrc;text/x-java;text/x-moc;text/x-pascal;text/x-tcl;text/x-tex;application/x-shellscript;text/x-c;text/x-c++;

Another approach is to wrap that call in a shell "launcher" script, just like how lvim is run, see:

LunarVim/utils/bin/lvim

Lines 1 to 3 in 2345d8c

	#!/bin/sh
	exec nvim -u ~/.local/share/lunarvim/lvim/init.lua --cmd "set runtimepath+=~/.local/share/lunarvim/lvim" "$@"

[nwaywood]

I would like to request support for Goneovim as well please :) https://github.com/akiyosi/goneovim

[kylo252]

This should probably work now after #1381.

Clone the repo into ~/.config/nvim and start nvim or goneovim like usual. It probably still needs some polishing, but it should hopefully work.

[nwaywood]

@kylo252 wait are you saying clone the lunarvim repo into ~/.config/nvim? If it's possible I would still like to be able to have a seperate nvim config for command line and use lunarvim in the gui

[sa-mendez]

This should probably work now after #1381.

Clone the repo into ~/.config/nvim and start nvim or goneovim like usual. It probably still needs some polishing, but it should hopefully work.

It kind of works but not without some tweaks. Some of the things like reloading the configs, and running LvimUpdate will fail

Here is what I did to get this to work:

1. Cloned rolling into ~/.config/nvim
2. Added the following export to my zsh (or bash) exports:

export LUNARVIM_RUNTIME_DIR=$HOME/.config/nvim

3. This fixes the config reloading on save. In utils/init.lua, edit the function reload_lv_config() :

vim.cmd("source " .. utils.join_paths(get_runtime_dir(), "lvim", "lua", "plugins.lua"))

becomes

vim.cmd("source " .. utils.join_paths(get_runtime_dir(), "lua", "plugins.lua"))

4. This fixes LvimUpdate command. In bootstrap.lua edit the function git_cmd(subcmd) :

local repo_dir = join_paths(get_runtime_dir(), "lvim")

becomes

local repo_dir = get_runtime_dir()

After these changes, everything works. I launch nvim, and I get lunarvim (no aliases or using lvim script). I launch neovide and it automatically uses lunarvim. Just gotta make sure that the LUNARVIM_RUNTIME_DIR variable is set.