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
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
vim (2:8.0.0022-1) unstable; urgency=medium
Vim now ships with a defaults.vim file which, when the user has no vimrc,
enables some options that have historically been disabled by default. This
is described in more detail at ":help defaults.vim".
Since defaults.vim is loaded when the user's vimrc would typically be
loaded, it will override any settings in /etc/vim/vimrc(.local). In order
to disable the loading of defaults.vim, add
let g:skip_defaults_vim = 1
to /etc/vim/vimrc(.local).
-- James McCoy <jamessan@debian.org> Tue, 04 Oct 2016 20:28:02 -0400
vim (2:7.4.2330-1) unstable; urgency=medium
The Python language bindings have been switched from python2 to python3.
If you have plugins/addons that use Python, they may need to be updated to
support python3.
Similarly, python3 specific packages may need to be installed to re-enable
plugins (e.g., python-powerline is replaced by python3-powerline) or plugin
features.
-- James McCoy <jamessan@debian.org> Wed, 07 Sep 2016 22:12:11 -0400
vim (2:7.3.154+hg~74503f6ee649-1) unstable; urgency=low
The vim-lesstif package has been removed in favor of the new vim-athena
package. The intent behind both packages is to provide a lighter-weight GUI
package as well as one that allows using XFLD fonts. The Athena toolkit,
however, has broader usage and reduces divergences with downstream
distributions.
-- James Vega <jamessan@debian.org> Sun, 27 Feb 2011 12:45:40 -0500
vim (2:7.2c.000-1) experimental; urgency=low
The autoindent option is no longer enabled by default because:
- 'autoindent' is rather naïve and turning on filetype-specific indentation
(via "filetype indent on") is usually a better choice.
- not having any automatic indenting enabled by default prevents new users
from encountering the bad indentation issue when pasting text.
Filetype plugins are no longer enabled by default because certain actions
(like preventing the loading of the default menus) *must* occur before
filetype detection is enabled. By enabling filetype plugins (and detection)
in debian.vim, we are preventing the user from being able to make changes to
Vim's behavior. Filetype plugins can be re-enabled via
"filetype plugin on".
-- James Vega <jamessan@debian.org> Thu, 07 Aug 2008 12:25:39 -0400
vim (1:7.1.285-1) unstable; urgency=low
Due to popular demand (and general conformity with other filetype plugins),
the debchangelog and debcontrol filetype plugins no longer enable folding by
default. If you wish to enable their folding, you can add the following
commands to your ~/.vimrc for debchangelog and debcontrol, respectively:
let g:debchangelog_fold_enable = 1
let g:debcontrol_fold_enable = 1
-- James Vega <jamessan@debian.org> Sun, 30 Mar 2008 12:42:35 -0400
vim (1:7.1-022+1) unstable; urgency=low
* /usr/share/vim/addons/ is no longer in the vim runtimepath
This is intended to avoid arbitrarly clashes among addons installed
system-wide and enabled by default, and to set up a common ground for Vim
extensions of various kinds. From now on vim addons won't be enabled by
default upon installation but will need to be enabled on a per-addon basis
either in a system-wide manner (affecting all users of the system) or by
each user who wants to use them. A tool exists for helping with addon
management: it is called "vim-addons" and is shipped by the package
"vim-addon-manager"; all vim addon packages should recommend it.
For more information see the VIM packaging policy (available on the web at
http://pkg-vim.alioth.debian.org/vim-policy.html/index.html) and the
manual page of vim-addons, available in the vim-addon-manager package.
-- Stefano Zacchiroli <zack@debian.org> Thu, 19 Jul 2007 23:28:44 +0200
|
