blob: d7eb03271f2a8ba13a19904f9e2c86f7b74a5fcb (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
MNV REFERENCE MANUAL by Bram Moolenaar
and Somebody Else
and Another Person
MNV USER MANUAL by Bram Moolenaar
and Somebody Else
and Another Person
MNV HELP FILE FORMAT
Issue #17721 (Strange >mnv highlighting in help documentation?)~
*restore-cursor* *last-position-jump* >mnv
augroup RestoreCursor
autocmd!
autocmd BufReadPost *
\ let line = line("'\"")
\ | if line >= 1 && line <= line("$") && &filetype !~# 'commit'
\ && index(['xxd', 'gitrebase'], &filetype) == -1
\ && !&diff
\ | execute "normal! g`\""
\ | endif
augroup END
URLs~
*g:zig_recommended_style*
By default the following indentation options are set, in accordance with Zig's
recommended style (https://ziglang.org/documentation/master/): >
NOTE, WARNING and DEPRECATED~
When you 'send a file to MNV', MNV changes to that file's directory. Note,
however, that any long directory names will appear in their short (MS-DOS)
form on some Windows versions. This is a limitation of the Windows "Send To"
mechanism.
EXAMPLE LANGUAGES~
*mnv9-mix*
There is one way to use both legacy and MNV9 syntax in one script file: >mnv9
" legacy MNV script comments may go here
if !has('mnv9script')
" legacy MNV script commands go here
finish
endif
mnv9script
# MNV9 script commands go here
This allows for writing a script that takes advantage of the MNV9 script
syntax if possible, but will also work on a MNV version without it.
mnv:tw=78:ts=8:noet:ft=help:norl:
|
