Your message dated Wed, 3 May 2006 12:29:22 -0400
with message-id <[email protected]>
has caused the Debian Bug report #365811,
regarding vim: setting eol does not mark the buffer modified
to be marked as having been forwarded to the upstream software
author(s) Bram Moolenaar <[email protected]>.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Re: Bug#365811: vim: setting eol does not mark the buffer modified
Wed, 3 May 2006 12:29:22 -0400
Regarding the bug report below, should 'eol' be an option that changes
the modified state of a buffer when it is toggled (similar to what
happens if 'fenc' is changed)?
On Tue, May 02, 2006 at 10:51:41PM -0700, Andrew Pimlott wrote:
> Setting the eol option does not mark the buffer modified, even when it
> would cause a change in the contents of the file:
> % echo -n hello > out
> % ls -l out
> -rw-rw-r-- 1 andrew andrew 5 2006-04-06 15:46 out
> % vim out
> Note the [noeol].
> :set eol
> Note no [+].
> :set modified?
> % ls -l out
> -rw-rw-r-- 1 andrew andrew 6 2006-04-06 15:48 out
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[email protected]>
--- End Message ---