On Sun, Nov 15, 2020 at 12:35:56PM +0100, Jonas Hahnfeld wrote:
> > yes, removing the initial 'filetype off' from .vimrc fixed it. So is
> > that a mistake
> > in https://lilypond.org/doc/v2.21/Documentation/usage/text-editor-
> > support ?
I use the exact code specified in that document (which
Hi Damian,
I cannot confirm this, removing the toggle of 'filetype' completely
breaks the file type detection for me if I don't have pacman's lilypond
installed. I'd guess this is probably because switching it from off to
on makes vim re-evaluate the type for the current buffer (after adding
the
Hi Jonasyes, removing the initial 'filetype off' from .vimrc fixed it. So is that a mistake in https://lilypond.org/doc/v2.21/Documentation/usage/text-editor-support ?thanksDamianOn 14 November 2020 at 20:25, Jonas Hahnfeld wrote:Hi,Am Donnerstag, den 12.11.2020, 16:26 + schrieb
Hi,
Am Donnerstag, den 12.11.2020, 16:26 + schrieb damianlegassick:
> Hi
>
> when installing Lilypond 2.21.80 from linux64 shellscript
> the /usr/local/lilypond/usr/share/lilypond/current/vim/ folder has a
> subfolder 'ftplugin'. On my Arch system I have to rename this folder
> to 'plugin'
Hi
when installing Lilypond 2.21.80 from linux64 shellscript the
/usr/local/lilypond/usr/share/lilypond/current/vim/ folder has a subfolder
'ftplugin'. On my Arch system I have to rename this folder to 'plugin' for the
:maps to work
Is this a general error or just my distro or just me?
