vim-puppet syntax highlighting scripts are not effective
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The scripts from vim-puppet are installed to `/usr/share/
Here is an example site.pp file:
file { '/etc/motd':
contents => 'Hello, world!',
}
To reproduce:
1. Run "vim site.pp"
Expected behavior:
Syntax highlighting works. Running ":set filetype?" reveals that the filetype is "puppet".
Observed behavior:
Syntax highlighting does not work. Running ":set filetype?" shows there is no filetype set. On some files, some other script detects the filetype as "conf".
If I run "vim site.pp" and then ":scriptnames" this is what I get:
1: /usr/share/
2: /usr/share/
3: /usr/share/
4: /usr/share/
5: /usr/share/
6: /usr/share/
7: ~/.vimrc
8: /usr/share/
9: /usr/share/
10: /usr/share/
11: /usr/share/
12: /usr/share/
13: /usr/share/
14: /usr/share/
15: /usr/share/
16: /usr/share/
17: /usr/share/
18: /usr/share/
Since most of these scripts are installed into /usr/share/
This is what I get after running "vim site.pp" and then ":scriptnames" after doing this.
1: /usr/share/
2: /usr/share/
3: /usr/share/
4: /usr/share/
5: /usr/share/
6: /usr/share/
7: /usr/share/
8: ~/.vimrc
9: /usr/share/
10: /usr/share/
11: /usr/share/
12: /usr/share/
13: /usr/share/
14: /usr/share/
15: /usr/share/
16: /usr/share/
17: /usr/share/
18: /usr/share/
19: /usr/share/
20: /usr/share/
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vim-puppet 3.4.3-1
ProcVersionSign
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Nov 8 12:28:14 2014
InstallationDate: Installed on 2014-04-29 (193 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitec
SourcePackage: puppet
UpgradeStatus: No upgrade log present (probably fresh install)
The package description for "vim-puppet" says:
# As per the Debian vim policy, installed addons are not activated
# automatically, but the "vim-addon-manager" tool can be used for this
# purpose.
Not sure if this is also the Ubuntu policy for vim addons, but since this package is unmodified from its Debian version, that's what you see.