Groups | Search | Server Info | Login | Register
Groups > comp.editors > #106842
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | comp.editors |
| Subject | Re: Vim - gzip'ed text file - noeol ? |
| Date | 2025-10-03 08:20 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <10bo10b$1iht1$1@dont-email.me> (permalink) |
| References | <10ahu13$4mb9$1@dont-email.me> <20251003091134.53dc9b8a@ryz.dorfdsl.de> |
On Fri, 3 Oct 2025 09:11:34 +0200, Marco Moock wrote: > On 18.09.2025 23:36 Uhr Janis Papanagnou wrote: > >> What I was wondering about, though, was that it displays the text file >> with the marker "[noeol]" despite the text file's last line is >> terminated correctly by a '\n'. - A bug? (Observed with Vim 7.3) > > I can confirm this with 9.1.1230-2. > > EOL exists, vim can find it and even after saving the file, the message > still occurs. The problem is that Vim wants to assume that every line ends with a newline character, but it doesn’t want you to be able to navigate to newline characters -- they’re supposed to be invisible, or something. Other more reasonably-designed editors are capable of distinguishing between files where the last line ends with a newline, and ones where it doesn’t. Vim cannot.
Back to comp.editors | Previous | Next — Previous in thread | Next in thread | Find similar
Vim - gzip'ed text file - noeol ? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-09-18 23:36 +0200
Re: Vim - gzip'ed text file - noeol ? Marco Moock <mm@dorfdsl.de> - 2025-10-03 09:11 +0200
Re: Vim - gzip'ed text file - noeol ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-03 08:20 +0000
Re: Vim - gzip'ed text file - noeol ? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-10-03 11:02 +0200
csiph-web