Your message dated Sun, 30 Sep 2007 18:16:29 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#56212: vim: \n corrupts viminfo
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(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 ---
Package: vim
Version: N/A
Severity: normal
I eddited a file called '\n\n\n' (were the \n realy were newlines)
now my viminfo file is corrupt. The newline were insert right away in the file
instead of being escaped or quoted in anyway.
I guess sim. things can happen with other special chars (maybe also ")
viminfo: Missing '>' in line: ^I"^I2^I0^@
Which I think referes to this part:
--- .viminfo ---
# File marks:
'0 2 0 ~/
'1 1 0 ~/test
'2 1 0 ~/.article.4095
'3 25 0 ~/.article.4095
'4 36 8 /tmp/mutt-Aleph-3976-2
'5 31 8 /tmp/mutt-Aleph-1675-78
'6 30 0 /tmp/mutt-Aleph-1675-21
'7 28 13 /tmp/mutt-Aleph-23044-12
'8 15 0 /tmp/mutt-Aleph-23044-10
'9 26 1 /tmp/mutt-Aleph-23044-8
# History of marks within files (newest to oldest):
> ~/
" 2 0
> ~/test
" 1 0
> /usr/share/vim/vim55/doc/help.txt.gz
" 1 0
> /usr/share/vim/vim55/doc/options.txt.gz
" 656 9
--- .viminfo ---
(I can send the whole file if it is needed.)
Greetings
Alexander N. Benner
-- System Information
Debian Release: potato
Kernel Version: Linux Aleph.Christen.Net 2.2.14 #2 Fri Jan 14 01:19:29 CET 2000
i586 unknown
--- End Message ---
--- Begin Message ---
tag 56212 - wontfix
thanks
On Tue, Jan 25, 2000 at 04:25:15PM +0100, Alexander N. Benner wrote:
> I eddited a file called '\n\n\n' (were the \n realy were newlines)
> now my viminfo file is corrupt. The newline were insert right away in the file
> instead of being escaped or quoted in anyway.
I've just retested this and Vim appears to properly handle this
situation. As such, I'm closing the bug.
James
--
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
--- End Message ---
