Can't put `vim9script` as first line in Vim configuration

[cideM]

Vim now ships with a new and improved version of Vimscript. A script file where the first line is vim9script will be interpreted with that new scripting language.

But because of the way the config file is generated it is seemingly impossible to achieve this in Home Manager, unless you go back to just using xdg.configFile.

As far as I can tell, there are two things standing in the way:

• Adding the few settings that are, for some reason, blessed by HM
• Adding the setpackpath and set runtimepath commands

I think that adjusting the paths could also be achieved by doing:

$ vim --cmd 'set runtimepath+=/foo'
:set rtp?
runtimepath=....,/foo

The known settings is something I'd personally just remove. Maybe there's a good reason these are there but I think it would be more consistent and simpler if users would simply put whatever they want in their configuration file, using Vim script (or Vim9 script).

You could also add a new option that let's you indicate to HM that you want to use a Vim9script configuration file but I think that removing all generated code from the config file is ultimately simpler.

What do you think?

EDIT: I didn't actually want to assign anyone, I guess this was somehow done for me by the GitHub UI

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.