Re: RFE: honor 'eol' setting regardless of 'binary' flag.

Am 2014-07-13 22:22, schrieb Linda A. Walsh:
> Christian Brabandt wrote:
>>> Trying to claim POSIX compliance as a justification for this
>>> behavior
>>> is what is silly. vim was born out of a desire for more than such.
>>> Someone is using POSIX
>>> to justify not having it be a choice.
>>>
>>> That's what is silly.
>>>
>>
>> No it is not. POSIX is pretty clear here and Vim is actually adhering
>> to the standard. If you like it or not. Being ironically won't make
>> you more convincing.
>> ----
> POSIX defines the behavior for "vi" as well. Vim isn't vi. If you
> want to talk POSIX, then you can only talk about vim without
> extensions
> and only having the POSIX compliant subset that is known as "vi".

I am sorry, but are you claiming, POSIX standard is not valid for Vim?
That is a strange understanding
from "POSIX.1-2008 defines a standard operating system interface and
environment..."

> You are claiming that a non-POSIX behavior of changing a file from
> containing 0 lines, to one that has 1 line is POSIX compatible.

I am not sure what you are trying to say here.

> No where does it say that a LF should be added at the end of file.

Implicitly it does, by the definitions you have have been given before.

,----
| The vi (visual) utility is a screen-oriented *text* editor. Only the
| open and visual modes of the editor are described in POSIX.1-2008; see
| the line editor ex for additional editing capabilities used in vi. The
| user can switch back and forth between vi and ex and execute ex
commands
| from within vi.
|
| This reference page uses the term edit buffer to describe the current
| working *text*. No specific implementation is implied by this term.
All
| editing changes are performed on the edit buffer, and no changes to it
| shall affect any file until an editor command writes the file.
`----

Note the empasis on text. That means, it has to delimit a line with a
newline.
The argument about cating files has been given before and is a very good
reason, btw.

> Many unix config files don't have LF's at the end of file; they can
> be redundent and confusing.

Which ones? I haven't seen any unix config file, that was that broken.

> If I want to know the answer to a question
> and store the answer in a file as 'yes' or 'no', if vim changes that to
> 'yes\n' or 'yes\r\n', is corrupting a text file. It changes it's
> meaning.

Why should Vim change you file, if you don't save it?

Best,
Christian

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.