Cool!

If you want to get autocomplete working though, then you might have to engage 
in some voodoo, depending on which completion engine you're using. I use 
nvim-cmp, which makes it necessary to enlist the cmp-dicitionary source, and 
specify all the dictionary files in the configuration:

require('cmp_dictionary').switcher({
     filetype = {
         lilypond = {
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/grobs",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/keywords",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/musicFunctions",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/articulations",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/grobProperties",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/paperVariables",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/headerVariables",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/contextProperties",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/clefs",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/repeatTypes",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/languageNames",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/accidentalsStyles",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/scales",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/musicCommands",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/markupCommands",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/contextsCmd",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/dynamics",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/contexts",
             
"~/.local/share/nvim/site/pack/packer/start/nvim-lilypond-suite/lilywords/translators",
         }
     }
})

... and setting `dictionary` as a completion source in the cmp.setup function...

I also highly recommend setting up one of the many snippet plugins.

Best,
Kenneth

-- 
Roosna & Flak - Contemporary Dance & Music
Web: roosnaflak.com
Code: {github,gitlab}.com/kflak
Mastodon: @k...@sonomu.club
On  6 May 2023  01:02, Andrew Bernard wrote:
>No - this is great. By no means hijacked. I'll go with that. Thanks! I
>only bring up Sublime Text because I couldn;t find the relevant neovim
>documentation.
>
>Neovim is pretty good.
>
>Andrew
>
>
>On 6/05/2023 12:56 am, Kenneth Flak wrote:
>> As a matter of fact, I tried the neovim-remote version now. It's pretty 
>> straightforward to set up, and it works! Sorry to hijack the sublime text 
>> thread, but since y'all were already going on about gvim, I thought I'd butt 
>> in :-)
>


Reply via email to