FM / doc

/usr/share/vim/vim91/doc

Name	Size	Mode	Actions
arabic.txt	12204	0644	edit dl rm
autocmd.txt	77872	0644	edit dl rm
builtin.txt	432001	0644	edit dl rm
change.txt	80714	0644	edit dl rm
channel.txt	59103	0644	edit dl rm
cmdline.txt	53181	0644	edit dl rm
debug.txt	6896	0644	edit dl rm
debugger.txt	5443	0644	edit dl rm
develop.txt	23118	0644	edit dl rm
diff.txt	18341	0644	edit dl rm
digraph.txt	62443	0644	edit dl rm
editing.txt	77499	0644	edit dl rm
eval.txt	173232	0644	edit dl rm
farsi.txt	523	0644	edit dl rm
filetype.txt	30622	0644	edit dl rm
fold.txt	24730	0644	edit dl rm
ft_ada.txt	18212	0644	edit dl rm
ft_context.txt	5161	0644	edit dl rm
ft_mp.txt	4706	0644	edit dl rm
ft_ps1.txt	2187	0644	edit dl rm
ft_raku.txt	4219	0644	edit dl rm
ft_rust.txt	19800	0644	edit dl rm
ft_sql.txt	30694	0644	edit dl rm
gui.txt	53499	0644	edit dl rm
gui_w32.txt	19123	0644	edit dl rm
gui_x11.txt	29318	0644	edit dl rm
hangulin.txt	598	0644	edit dl rm
hebrew.txt	5666	0644	edit dl rm
help.txt	9491	0644	edit dl rm
help.txt.vim-tiny	1350	0644	edit dl rm
helphelp.txt	16060	0644	edit dl rm
howto.txt	2916	0644	edit dl rm
if_cscop.txt	19325	0644	edit dl rm
if_lua.txt	18546	0644	edit dl rm
if_mzsch.txt	11941	0644	edit dl rm
if_ole.txt	7117	0644	edit dl rm
if_perl.txt	11451	0644	edit dl rm
if_pyth.txt	40820	0644	edit dl rm
if_ruby.txt	8516	0644	edit dl rm
if_sniff.txt	271	0644	edit dl rm
if_tcl.txt	22948	0644	edit dl rm
indent.txt	43699	0644	edit dl rm
index.txt	82373	0644	edit dl rm
insert.txt	88124	0644	edit dl rm
intro.txt	39623	0644	edit dl rm
map.txt	81176	0644	edit dl rm
mbyte.txt	58640	0644	edit dl rm
message.txt	31931	0644	edit dl rm
mlang.txt	8160	0644	edit dl rm
motion.txt	54387	0644	edit dl rm
netbeans.txt	37957	0644	edit dl rm
options.txt	419402	0644	edit dl rm
os_390.txt	4741	0644	edit dl rm
os_amiga.txt	5466	0644	edit dl rm
os_beos.txt	293	0644	edit dl rm
os_dos.txt	15495	0644	edit dl rm
os_haiku.txt	8543	0644	edit dl rm
os_mac.txt	6856	0644	edit dl rm
os_mint.txt	391	0644	edit dl rm
os_msdos.txt	523	0644	edit dl rm
os_os2.txt	299	0644	edit dl rm
os_qnx.txt	4071	0644	edit dl rm
os_risc.txt	328	0644	edit dl rm
os_unix.txt	2607	0644	edit dl rm
os_vms.txt	33743	0644	edit dl rm
os_win32.txt	14912	0644	edit dl rm
pattern.txt	63653	0644	edit dl rm
pi_getscript.txt	21077	0644	edit dl rm
pi_gzip.txt	1547	0644	edit dl rm
pi_logipat.txt	4196	0644	edit dl rm
pi_netrw.txt	181735	0644	edit dl rm
pi_paren.txt	2274	0644	edit dl rm
pi_spec.txt	4127	0644	edit dl rm
pi_tar.txt	7191	0644	edit dl rm
pi_vimball.txt	11859	0644	edit dl rm
pi_zip.txt	7778	0644	edit dl rm
popup.txt	40382	0644	edit dl rm
print.txt	31445	0644	edit dl rm
quickfix.txt	85701	0644	edit dl rm
quickref.txt	73061	0644	edit dl rm
quotes.txt	12748	0644	edit dl rm
README.Debian	324	0644	edit dl rm
recover.txt	10727	0644	edit dl rm
remote.txt	8626	0644	edit dl rm
repeat.txt	46502	0644	edit dl rm
rileft.txt	5063	0644	edit dl rm
russian.txt	3024	0644	edit dl rm
scroll.txt	14356	0644	edit dl rm
sign.txt	26860	0644	edit dl rm
spell.txt	64205	0644	edit dl rm
sponsor.txt	6776	0644	edit dl rm
starting.txt	74540	0644	edit dl rm
syntax.txt	237597	0644	edit dl rm
tabpage.txt	17246	0644	edit dl rm
tags	391091	0644	edit dl rm
tags.vim-tiny	1935	0644	edit dl rm
tagsrch.txt	40475	0644	edit dl rm
term.txt	55685	0644	edit dl rm
terminal.txt	63169	0644	edit dl rm
testing.txt	22507	0644	edit dl rm
textprop.txt	20478	0644	edit dl rm
tips.txt	21336	0644	edit dl rm
todo.txt	316358	0644	edit dl rm
uganda.txt	13052	0644	edit dl rm
undo.txt	17811	0644	edit dl rm
userfunc.txt	20624	0644	edit dl rm
usr_01.txt	7076	0644	edit dl rm
usr_02.txt	24228	0644	edit dl rm
usr_03.txt	23934	0644	edit dl rm
usr_04.txt	19131	0644	edit dl rm
usr_05.txt	27946	0644	edit dl rm
usr_06.txt	10639	0644	edit dl rm
usr_07.txt	15995	0644	edit dl rm
usr_08.txt	19379	0644	edit dl rm
usr_09.txt	11502	0644	edit dl rm
usr_10.txt	29200	0644	edit dl rm
usr_11.txt	13025	0644	edit dl rm
usr_12.txt	13433	0644	edit dl rm
usr_20.txt	13733	0644	edit dl rm
usr_21.txt	18456	0644	edit dl rm
usr_22.txt	14904	0644	edit dl rm
usr_23.txt	12744	0644	edit dl rm
usr_24.txt	20827	0644	edit dl rm
usr_25.txt	19176	0644	edit dl rm
usr_26.txt	8259	0644	edit dl rm
usr_27.txt	17709	0644	edit dl rm
usr_28.txt	16020	0644	edit dl rm
usr_29.txt	20259	0644	edit dl rm
usr_30.txt	22658	0644	edit dl rm
usr_31.txt	10399	0644	edit dl rm
usr_32.txt	5378	0644	edit dl rm
usr_40.txt	23554	0644	edit dl rm
usr_41.txt	65272	0644	edit dl rm
usr_42.txt	13853	0644	edit dl rm
usr_43.txt	7409	0644	edit dl rm
usr_44.txt	28948	0644	edit dl rm
usr_45.txt	17680	0644	edit dl rm
usr_50.txt	4554	0644	edit dl rm
usr_51.txt	25517	0644	edit dl rm
usr_52.txt	13498	0644	edit dl rm
usr_90.txt	16778	0644	edit dl rm
usr_toc.txt	9886	0644	edit dl rm
various.txt	32432	0644	edit dl rm
version4.txt	13911	0644	edit dl rm
version5.txt	308529	0644	edit dl rm
version6.txt	576942	0644	edit dl rm
version7.txt	674698	0644	edit dl rm
version8.txt	1599852	0644	edit dl rm
version9.txt	1611325	0644	edit dl rm
vim9.txt	91753	0644	edit dl rm
vim9class.txt	41040	0644	edit dl rm
visual.txt	22625	0644	edit dl rm
vi_diff.txt	57404	0644	edit dl rm
windows.txt	58706	0644	edit dl rm
workshop.txt	371	0644	edit dl rm

Edit: /usr/share/vim/vim91/doc/usr_52.txt (13498B)

*usr_52.txt*	For Vim version 9.1.  Last change: 2022 Jun 04

VIM USER MANUAL - by Bram Moolenaar

Write larger plugins

When plugins do more than simple things, they tend to grow big.  This file
explains how to make sure they still load fast and how to split them up in
smaller parts.

|52.1|	Export and import
|52.2|	Autoloading
|52.3|	Autoloading without import/export
|52.4|	Other mechanisms to use
|52.5|	Using a Vim9 script from legacy script

==============================================================================
*52.1*	Export and import

Vim9 script was designed to make it easier to write large Vim scripts.  It
looks more like other script languages, especially Typescript.  Also,
functions are compiled into instructions that can be executed quickly.  This
makes Vim9 script a lot faster, up to a 100 times.

The basic idea is that a script file has items that are private, only used
inside the script file, and items that are exported, which can be used by
scripts that import them.  That makes very clear what is defined where.

Let's start with an example, a script that exports one function and has one
private function: >

vim9script

export def GetMessage(count: string): string
	   var nr = str2nr(count)
	   var result = $'To {nr} we say '
	   result ..= GetReply(nr)
	   return result
	enddef

def GetReply(nr: number): string
	  if nr == 42
	     return 'yes'
	  elseif nr = 22
	     return 'maybe'
	  else
	     return 'no'
	  endif
	enddef

The `vim9script` command is required, `export` only works in a |Vim9| script.

The `export def GetMessage(...` line starts with `export`, meaning that this
function can be called by other scripts.  The line `def GetReply(...` does not
start with `export`, this is a script-local function, it can only be used
inside this script file.

Now about the script where this is imported.  In this example we use this
layout, which works well for a plugin below the "pack" directory:
	.../plugin/theplugin.vim
	.../lib/getmessage.vim

Assuming the "..." directory has been added to 'runtimepath', Vim will look
for plugins in the "plugin" directory and source "theplugin.vim".  Vim does
not recognize the "lib" directory, you can put any scripts there.

The above script that exports GetMessage() goes in lib/getmessage.vim.  The
GetMessage() function is used in plugin/theplugin.vim: >

vim9script

import "../lib/getmessage.vim"
	command -nargs=1 ShowMessage echomsg getmessage.GetMessage(<f-args>)

The `import` command uses a relative path, it starts with "../", which means
to go one directory up.  For other kinds of paths see the `:import` command.

How we can try out the command that the plugin provides: >
	ShowMessage 1
<	To 1 we say no ~
>
	ShowMessage 22
<	To 22 we say maybe ~

Notice that the function GetMessage() is prefixed with the imported script
name "getmessage".  That way, for every imported function used, you know what
script it was imported from.  If you import several scripts each of them could
define a GetMessage() function: >

vim9script

import "../lib/getmessage.vim"
	import "../lib/getother.vim"
	command -nargs=1 ShowMessage echomsg getmessage.GetMessage(<f-args>)
	command -nargs=1 ShowOther echomsg getother.GetMessage(<f-args>)

If the imported script name is long or you use it in many places, you can
shorten it by adding an "as" argument: >
	import "../lib/getmessage.vim" as msg
	command -nargs=1 ShowMessage echomsg msg.GetMessage(<f-args>)

RELOADING

One thing to keep in mind: the imported "lib/getmessage.vim" script will be
sourced only once.  When it is imported a second time sourcing it will be
skipped, since the items in it have already been created.  It does not matter
if this import command is in another script, or in the same script that is
sourced again.

This is efficient when using a plugin, but when still developing a plugin it
means that changing "lib/getmessage.vim" after it has been imported will have
no effect.  You need to quit Vim and start it again. (Rationale: the items
defined in the script could be used in a compiled function, sourcing the
script again may break those functions).

USING GLOBALS

Sometimes you will want to use global variables or functions, so that they can
be used anywhere.  A good example is a global variable that passes a
preference to a plugin.  To avoid other scripts using the same name, use a
prefix that is very unlikely to be used elsewhere.  For example, if you have a
"mytags" plugin, you could use: >

g:mytags_location = '$HOME/project'
	g:mytags_style = 'fast'

==============================================================================
*52.2*	Autoloading

After splitting your large script into pieces, all the lines will still be
loaded and executed the moment the script is used.  Every `import` loads the
imported script to find the items defined there.  Although that is good for
finding errors early, it also takes time.  Which is wasted if the
functionality is not often used.

Instead of having `import` load the script immediately, it can be postponed
until needed.  Using the example above, only one change needs to be made in
the plugin/theplugin.vim script: >
	import autoload "../lib/getmessage.vim"

Nothing in the rest of the script needs to change.  However, the types will
not be checked.  Not even the existence of the GetMessage() function is
checked until it is used.  You will have to decide what is more important for
your script: fast startup or getting errors early.  You can also add the
"autoload" argument later, after you have checked everything works.

AUTOLOAD DIRECTORY

Another form is to use autoload with a script name that is not an absolute or
relative path: >
	import autload "monthlib.vim"

This will search for the script "monthlib.vim" in the autoload directories of
'runtimepath'.  With Unix one of the directories often is "~/.vim/autoload".
It will also search under 'packpath', under "start".

The main advantage of this is that this script can be easily shared with other
scripts.  You do need to make sure that the script name is unique, since Vim
will search all the "autoload" directories in 'runtimepath', and if you are
using several plugins with a plugin manager, it may add a directory to
'runtimepath', each of which might have an "autoload" directory.

Without autoload: >
	import "monthlib.vim"

Vim will search for the script "monthlib.vim" in the import directories of
'runtimepath'.  Note that in this case adding or removing "autoload" changes
where the script is found.  With a relative or absolute path the location does
not change.

==============================================================================
*52.3*	Autoloading without import/export

*write-library-script*
A mechanism from before import/export is still useful and some users may find
it a bit simpler.  The idea is that you call a function with a special name.
That function is then in an autoload script.  We will call that one script a
library script.

The autoload mechanism is based on a function name that has "#" characters: >

mylib#myfunction(arg)

Vim will recognize the function name by the embedded "#" character and when
it is not defined yet search for the script "autoload/mylib.vim" in
'runtimepath'.  That script must define the "mylib#myfunction()" function.
Obviously the name "mylib" is the part before the "#" and is used as the name
of the script, adding ".vim".

You can put many other functions in the mylib.vim script, you are free to
organize your functions in library scripts.  But you must use function names
where the part before the '#' matches the script name.  Otherwise Vim would
not know what script to load.  This is where it differs from the import/export
mechanism.

If you get really enthusiastic and write lots of library scripts, you may
want to use subdirectories.  Example: >

netlib#ftp#read('somefile')

Here the script name is taken from the function name up to the last "#". The
"#" in the middle are replaced by a slash, the last one by ".vim".  Thus you
get "netlib/ftp.vim".  For Unix the library script used for this could be:

~/.vim/autoload/netlib/ftp.vim

Where the function is defined like this: >

def netlib#ftp#read(fname: string)
		#  Read the file fname through ftp
	enddef

Notice that the name the function is defined with is exactly the same as the
name used for calling the function.  And the part before the last '#'
exactly matches the subdirectory and script name.

You can use the same mechanism for variables: >

var weekdays = dutch#weekdays

This will load the script "autoload/dutch.vim", which should contain something
like: >

var dutch#weekdays = ['zondag', 'maandag', 'dinsdag', 'woensdag',
		\ 'donderdag', 'vrijdag', 'zaterdag']