blocks|key|545715|text|将新选项包含在：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|545716|if+version+>=+703
++set+rnu+...
endif|code-block|syntax|javascript|545717|有关要使用的版本号的详细信息，请查看v:version的帮助：|offset|length|style|CODE|545718|++++++++++++++++++++++++++++++++++++++++*v:version*+*version-variable*
v:version+++++++Version+number+of+Vim:+Major+version+number+times+100+plus
++++++++++++++++minor+version+number.++Version+5.0+is+500.++Version+5.1+(5.01)
++++++++++++++++is+501.++Read-only.++"version"+also+works,+for+backwards
++++++++++++++++compatibility.
++++++++++++++++Use+%7Chas()%7C+to+check+if+a+certain+patch+was+included,+e.g.:+>
++++++++++++++++++++++++if+has("patch123")
<+++++++++++++++Note+that+patch+numbers+are+specific+to+the+version,+thus+both
++++++++++++++++version+5.0+and+5.1+may+have+a+patch+123,+but+these+are
++++++++++++++++completely+different.|545719|entityMap^0|0|0|I|9|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Wrap the new options in:

<pre><code>if version &gt;= 703
 set rnu ...
endif
</code></pre>

Check the help for <code>v:version</code> for more info on the version number to use:

<pre><code> *v:version* *version-variable*
v:version Version number of Vim: Major version number times 100 plus
 minor version number. Version 5.0 is 500. Version 5.1 (5.01)
 is 501. Read-only. "version" also works, for backwards
 compatibility.
 Use |has()| to check if a certain patch was included, e.g.: &gt;
 if has("patch123")
&lt; Note that patch numbers are specific to the version, thus both
 version 5.0 and 5.1 may have a patch 123, but these are
 completely different.
</code></pre>

blocks|key|328933|text|我想说这个问题没有得到回答。考虑在具有更高vim版本的计算机A上创建的Session.vim。在源代码控制中，当另一台计算机B试图打开Session.vim时，就会触发错误。必须手动包装版本号是没有意义的，因为这应该是一个自动化的过程。有了这种行为，新版本将不得不在保存会话时自动将新命令包装在版本号中-这是7.3所不能做的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328934|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would say this question is not answered. Consider a Session.vim created on computer A which has the later vim version. In source control when another computer B tries to open the Session.vim the errors are triggered. It makes no sense to have to manually wrap a version number for what should be an automated process. With this behaviour the new version would have to automatically wrap a new command in a version number when saving a session - something which 7.3 does not do.

blocks|key|545807|text|可能值得对实际支持的功能进行更细粒度的检查，而不是版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|545808|例如：|545809|if+has('persistent_undo')
++set+undofile
++set+undodir=/tmp
endif

"+Some+options+can+only+be+checked+with+exists('%2Boption');+I'm+not+sure+why
if+exists('%2Brelativenumber')
++set+rnu
endif

if+has('cryptv')
++set+cryptmethod=blowfish
end|code-block|syntax|javascript|545810|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

It might be worth doing more fine-grained checking for actual supported features rather than versions.

E.g.:

<pre><code>if has('persistent_undo')
 set undofile
 set undodir=/tmp
endif

" Some options can only be checked with exists('+option'); I'm not sure why
if exists('+relativenumber')
 set rnu
endif

if has('cryptv')
 set cryptmethod=blowfish
end
</code></pre>

blocks|key|545843|text|您可以忽略silent!+...中的任何错误，比如silent!+set+undofile|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|545844|entityMap^0|5|B|P|K|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

You can ignore any error with <code>silent! ...</code>, like <code>silent! set undofile</code>

blocks|key|545926|text|有时，一个选项是合法的，但在当前环境中不可用。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|545927|$+vi
Error+detected+while+processing+/home/username/.vimrc:
line++++9:
Unknown+option:+indentexpr=|code-block|syntax|javascript|545928|要测试选项是否存在，并避免出现不可用的错误，请执行以下操作：|545929|if+exists("&indentexpr")
++:set+indentexpr=
endif|545930|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Sometimes an option is legitimate, but not available in the current environment. For example:

<pre><code>$ vi
Error detected while processing /home/username/.vimrc:
line 9:
Unknown option: indentexpr=
</code></pre>

To test whether an option exists or not, and avoid an error if not available:

<pre><code>if exists("&amp;indentexpr")
 :set indentexpr=
endif
</code></pre>

I tote the same .vimrc between machines that have both Vim 7.2 and 7.3 installed. The machines with Vim 7.2 complain about my 7.3-specific options every time I open a file:

<pre><code>Error detected while processing /home/spiffytech/.vimrc:
line 72:
E518: Unknown option: rnu
line 73:
E518: Unknown option: undofile
line 74:
E518: Unknown option: undodir=/tmp
line 75:
E518: Unknown option: cryptmethod=blowfish
Press ENTER or type command to continue
</code></pre>

How can I make Vim ignore these errors and not prompt me to hit enter whenever I open files?

Ignore "Unknown option" errors in vimrc

我在同时安装了Vim7.2和Vim7.3的机器之间携带相同的.vimrc。每次我打开一个文件时，安装Vim 7.2的机器都会抱怨我的7.3特定选项：Error detected while processing /home/spiffytech/.vimrc:line   72:E518: Unknown option...

问忽略vimrc中的“未知选项”错误
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问忽略vimrc中的“未知选项”错误EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问忽略vimrc中的“未知选项”错误
EN