vim-runtime: Byte Order Marker (BOM) automatically set when opening files with .wiki extension

[Matthias Buchmeier]

Binary package hint: vim-runtime

Ubuntu release: gutsy
source package: vim-runtime 1:7.1-056+2ubuntu2

What I expect to happen:
Vim should only set the bomb option (resulting in writing of byte order marker BOM)
if necesary (not for utf-8)
and not overriding set nobomb user configuration.
(The BOM will cause problems with many applications)

Whats happening instead:
The bomb option is automatically set even for utf-8 files and even though
set nobomb is specified in .vimrc.

The bug seems to be located in the file /usr/share/vim/vim71/ftplugin/flexwiki.vim,
which is sourced when opening files with the extension .wiki .
Vim will automatically "set bomb" option resulting in a BOM byte at the beginning of the file,
no matter if the original file did not have a BOM and overriding an explicit nobomb option
in the .vimrc configuration file.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Matthias Buchmeier (m-buchmeier)]

On Sat, 29 Nov 2008, Daniel T Chen wrote:

> Date: Sat, 29 Nov 2008 23:31:58 -0000
> From: Daniel T Chen <email address hidden>
> Reply-To: Bug 196162 <email address hidden>
> To: <email address hidden>
> Subject: [Bug 196162] Re: vim-runtime: Byte Order Marker (BOM) automatically
> set when opening files with .wiki extension
>
> Is this symptom still reproducible in 8.10 or 9.04?

The symptom is still reproducible in 8.04. You can easily check
the bug by creating a file with .wiki extension, e.g.:
touch test.wiki
then opening it with gvim:
gvim test.wiki
then you check with the ":set" command if "bomb" flag is set.

>
> ** Changed in: vim (Ubuntu)
> Status: New => Incomplete
>
> --
> vim-runtime: Byte Order Marker (BOM) automatically set when opening files with .wiki extension
> https://bugs.launchpad.net/bugs/196162
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “vim” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: vim-runtime
>
> Ubuntu release: gutsy
> source package: vim-runtime 1:7.1-056+2ubuntu2
>
> What I expect to happen:
> Vim should only set the bomb option (resulting in writing of byte order marker BOM)
> if necesary (not for utf-8)
> and not overriding set nobomb user configuration.
> (The BOM will cause problems with many applications)
>
> Whats happening instead:
> The bomb option is automatically set even for utf-8 files and even though
> set nobomb is specified in .vimrc.
>
> The bug seems to be located in the file /usr/share/vim/vim71/ftplugin/flexwiki.vim,
> which is sourced when opening files with the extension .wiki .
> Vim will automatically "set bomb" option resulting in a BOM byte at the beginning of the file,
> no matter if the original file did not have a BOM and overriding an explicit nobomb option
> in the .vimrc configuration file.
>

###############################################
# Dr. Matthias Buchmeier #
# Institut für Angewandte Physik #
# Corrensstrasse 2-4 #
# Westfälische Wilhelms-Universität #
# 48149 Münster #
# Germany #
# #
# Tel: [phone] #
# Fax: 33513 #
# Mobile: [phone] #
# Email: <email address hidden> #
###############################################

[Ralph Janke (txwikinger)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Will Gray (graywh)]

This has been fixed upstream.