From michael.john.kirk at gmail.com  Mon Jan 10 21:08:46 2011
From: michael.john.kirk at gmail.com (Michael Kirk)
Date: Mon, 10 Jan 2011 13:08:46 -0800
Subject: Bug#609599: vim-runtime: Error detected while processing
	/usr/share/vim/vim73/ftplugin/ruby.vim: line 83
Message-ID: <20110110210846.7412.78868.reportbug@jackpine.hemlock.ath.cx>

Package: vim-runtime
Version: 2:7.3.035+hg~8fdc12103333-1
Severity: minor

When I open a ruby file

fish$ vim File.rb
Error detected while processing /usr/share/vim/vim73/ftplugin/ruby.vim:
line 83

>>>>>> /usr/share/vim/vim73/ftplugin/ruby.vim
 80     if &shellxquote == "'"
 81       let s:ruby_path = system('ruby -e "' . s:code . '"')
 82     else
 83       let s:ruby_path = system("ruby -e '" . s:code . "'")
 84     endif

I'm using fish as my shell.

I'm not sure of the repercussions of this error, vim starts more-or-less normally after a bit.

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

vim-runtime depends on no packages.

Versions of packages vim-runtime recommends:
ii  vim          2:7.3.035+hg~8fdc12103333-1 Vi IMproved - enhanced vi editor
ii  vim-tiny     2:7.3.035+hg~8fdc12103333-1 Vi IMproved - enhanced vi editor -

vim-runtime suggests no packages.

-- no debconf information




From chris4 at epoxycoating.biz  Mon Jan 10 15:47:58 2011
From: chris4 at epoxycoating.biz (chris)
Date: 10 Jan 2011 23:47:58 +0800
Subject: <ADV>Lowest Prices For Waterproofing+Painting+Upgrading
Message-ID: <EASIBOOK-DBsXJB7oDa00371b63@Easibook-DB>

<P><img src="cid:cid0" /></P>
<P><img src="cid:cid1" /></P>
<P><img src="cid:cid2" /></P>
<P><SPAN style="FONT-SIZE: 8pt; mso-bidi-font-size: 10.0pt" lang=EN-US><FONT face=Garamond>------UNSUBSCRIBE INSTRUCTIONS------<BR>*Your privacy is extremely important to us. You're receiving e-mail from us because you previously requested information at </FONT></SPAN><B style="mso-bidi-font-weight: normal"><I style="mso-bidi-font-style: normal"><U><SPAN style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 8pt" lang=EN-US><A href="http://sbmspainter.wordpress.com">http//www.sbmspainter.wordpress.com</A></SPAN></U></I></B><SPAN style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 10pt" lang=EN-US> </SPAN><SPAN style="FONT-SIZE: 8pt; mso-bidi-font-size: 10.0pt" lang=EN-US><FONT face=Garamond>If this e-mail was sent in error, or if you wish to unsubscribe </FONT></SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt; mso-bidi-font-size: 10.0pt" lang=EN-US><A href="mailto:chrisselvam at yahoo.com"><FONT color=#0000ff face=Garamond>mailto:chrisselvam at yahoo.com</FONT></A></SPAN><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 8pt; mso-bidi-font-size: 10.0pt" lang=EN-US> </SPAN><SPAN style="FONT-SIZE: 8pt; mso-bidi-font-size: 10.0pt" lang=EN-US><FONT face=Garamond>to stop receiving emails.This email is in compliance with the regulations pertaining</FONT></SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt; mso-bidi-font-size: 10.0pt" lang=EN-US><FONT face=Garamond>&nbsp;to CANSPAM<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: 12pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char; mso-layout-grid-align: none" class=MsoNormal><SPAN style="LETTER-SPACING: 0.05pt; FONT-FAMILY: 'Times New Roman','serif'; COLOR: black; FONT-SIZE: 10pt" lang=EN-US>.</SPAN><SPAN style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 10pt" lang=EN-US><o:p></o:p></SPAN></P>
<P>&nbsp;</P>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110110/bd5f207b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 27348 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110110/bd5f207b/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 72558 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110110/bd5f207b/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 8352 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110110/bd5f207b/attachment-0005.gif>

From jamessan at debian.org  Mon Jan 10 21:37:03 2011
From: jamessan at debian.org (James Vega)
Date: Mon, 10 Jan 2011 16:37:03 -0500
Subject: Bug#609599: vim-runtime: Error detected while processing
	/usr/share/vim/vim73/ftplugin/ruby.vim: line 83
In-Reply-To: <20110110210846.7412.78868.reportbug@jackpine.hemlock.ath.cx>
References: <20110110210846.7412.78868.reportbug@jackpine.hemlock.ath.cx>
Message-ID: <AANLkTikdOqgFqZoLMUf8Z0NxC-860Er481edVNwkBd8c@mail.gmail.com>

On Mon, Jan 10, 2011 at 4:08 PM, Michael Kirk
<michael.john.kirk at gmail.com> wrote:
> When I open a ruby file
>
> fish$ vim File.rb
> Error detected while processing /usr/share/vim/vim73/ftplugin/ruby.vim:
> line 83
>
>>>>>>> /usr/share/vim/vim73/ftplugin/ruby.vim
> ?80 ? ? if &shellxquote == "'"
> ?81 ? ? ? let s:ruby_path = system('ruby -e "' . s:code . '"')
> ?82 ? ? else
> ?83 ? ? ? let s:ruby_path = system("ruby -e '" . s:code . "'")
> ?84 ? ? endif
>
> I'm using fish as my shell.
>
> I'm not sure of the repercussions of this error, vim starts more-or-less normally after a bit.

Vim uses POSIX-compatible syntax for running commands in the shell
(unless using one of the few non-POSIX shells it recognizes).
Obviously, Fish strays fairly far from POSIX so your best bet it to tell
Vim to use a different shell.  It may be possible to tweak the
shell-related options (like 'shellxquote', 'shellquote', etc.) but it's
easier just to change the shell.  Here's what I used to have in my vimrc
when I used fish:

  if $SHELL =~ 'fish'
    set shell='/bin/sh'
  endif

-- 
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <jamessan at debian.org>




From owner at bugs.debian.org  Wed Jan 12 03:51:03 2011
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 12 Jan 2011 03:51:03 +0000
Subject: Bug#609599: marked as done (vim-runtime: Error detected while
	processing /usr/share/vim/vim73/ftplugin/ruby.vim: line 83)
References: <20110112034836.GD28487@jamessan.com>
	<20110110210846.7412.78868.reportbug@jackpine.hemlock.ath.cx>
Message-ID: <handler.609599.D609599.129480412717106.ackdone@bugs.debian.org>

Your message dated Tue, 11 Jan 2011 22:48:36 -0500
with message-id <20110112034836.GD28487 at jamessan.com>
and subject line Re: Bug#609599: vim-runtime: Error detected while processing /usr/share/vim/vim73/ftplugin/ruby.vim: line 83
has caused the Debian Bug report #609599,
regarding vim-runtime: Error detected while processing /usr/share/vim/vim73/ftplugin/ruby.vim: line 83
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
609599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609599
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Kirk <michael.john.kirk at gmail.com>
Subject: vim-runtime: Error detected while processing
 /usr/share/vim/vim73/ftplugin/ruby.vim: line 83
Date: Mon, 10 Jan 2011 13:08:46 -0800
Size: 2622
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110112/23308a5d/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: James Vega <jamessan at debian.org>
Subject: Re: Bug#609599: vim-runtime: Error detected while processing
 /usr/share/vim/vim73/ftplugin/ruby.vim: line 83
Date: Tue, 11 Jan 2011 22:48:36 -0500
Size: 5239
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110112/23308a5d/attachment-0001.eml>

From lyorobi at gmail.com  Thu Jan 13 11:48:12 2011
From: lyorobi at gmail.com (lyorobi at gmail.com)
Date: Thu, 13 Jan 2011 14:48:12 +0300
Subject: =?UTF-8?Q?Hitt=C3=A9l_az_EMFESZ-nek_=C3=A9s_tov=C3=A1bbra_is_j=C3=B3_=C3?=
	=?UTF-8?Q?=A1rat_akarsz=3F?=
Message-ID: <85c1b49ab0c6ad6363e9e3c06a6b1c97@serverpolis.com>

Szia! 

Ez az elm?lt napok legfontosabb cikke az Indexen! 

http://4szoba.hu/cikk/tippek/2308-gazarak-a-foldjen-jartunk-hogyan-lesz-annyi

Az Emfesz bed?lt, mi meg itt maradtunk a slamasztik?ban!

Olvasd el a cikket, mert fontos inf? van benne, k?l?n?sen a
v?g?n l?v? ?rakat bemutat? t?bl?zat! Itt feh?ren-feket?n
kider?l, kin?l mennyi az annyi! 

Ne hagyd magad megvezetni! Egy m?sik cikk ?rja, hogy a multik m?r
gy?lnek a v?rszagra ?s az ? szerz?d?s?ket tolj?k az orrod
al?!

Ne higgy nekik, csak a saj?t szemednek ?s j?zan bel?t?sodnak! 

Tov?bbi inform?ci??rt ?ratkozz fel a h?rlevelemre:
http://www.penzvisszaterites.sokoldal.hu/regisztracios_lap

?dv:

Robi, aki hozz?d hasonl?an megette a nagyon-gaz.hu aj?nlat?t..



 




From contact at proxedit.com  Sun Jan 16 16:27:45 2011
From: contact at proxedit.com (CASA ANNONCES)
Date: Sun, 16 Jan 2011 16:27:45 +0000
Subject: CASA ANNONCES NUMERO 829
Message-ID: <SERVEUR33ZCHusMjQHt00034f20@serveur33>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110116/90aa0db6/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CASA ANNONCES NUMERO 829.pdf
Type: application/octetstream
Size: 687874 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110116/90aa0db6/attachment-0001.bin>

From math.parent at gmail.com  Sat Jan 29 13:46:19 2011
From: math.parent at gmail.com (Mathieu Parent)
Date: Sat, 29 Jan 2011 14:46:19 +0100
Subject: Bug#611444: Enable syntax highlighting by default
Message-ID: <20110129134619.6193.72656.reportbug@tourthieu.sathieu.net>

Package: vim
Version: 2:7.2.445+hg~cb94c42c0e1a-1
Severity: wishlist

Hello,

Please enable syntax highlighting by default.

This can be done by uncommenting the following line in /etc/vim/vimrc:
syntax on


Regards

Mathieu Parent



-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim depends on:
ii  libacl1      2.2.49-4                    Access control list shared library
ii  libc6        2.11.2-9                    Embedded GNU C Library: Shared lib
ii  libgpm2      1.20.4-3.3                  General Purpose Mouse - shared lib
ii  libncurses5  5.7+20100313-5              shared libraries for terminal hand
ii  libselinux1  2.0.96-1                    SELinux runtime shared libraries
ii  vim-common   2:7.2.445+hg~cb94c42c0e1a-1 Vi IMproved - Common files
ii  vim-runtime  2:7.2.445+hg~cb94c42c0e1a-1 Vi IMproved - Runtime files

vim recommends no packages.

Versions of packages vim suggests:
pn  ctags                         <none>     (no description available)
pn  vim-doc                       <none>     (no description available)
pn  vim-scripts                   <none>     (no description available)

-- no debconf information




From owner at bugs.debian.org  Sat Jan 29 14:33:06 2011
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 29 Jan 2011 14:33:06 +0000
Subject: Processed: Re: Bug#611444: Enable syntax highlighting by default
In-Reply-To: <20110129143208.GA30534@jamessan.com>
References: <20110129143208.GA30534@jamessan.com>
Message-ID: <handler.s.C.129631153918503.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tag 611444 wontfix
Bug #611444 [vim] Enable syntax highlighting by default
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
611444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611444
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From owner at bugs.debian.org  Sat Jan 29 14:33:08 2011
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 29 Jan 2011 14:33:08 +0000
Subject: Bug#611444: marked as done (Enable syntax highlighting by default)
References: <20110129143208.GA30534@jamessan.com>
	<20110129134619.6193.72656.reportbug@tourthieu.sathieu.net>
Message-ID: <handler.611444.D611444.129631153918512.ackdone@bugs.debian.org>

Your message dated Sat, 29 Jan 2011 09:32:08 -0500
with message-id <20110129143208.GA30534 at jamessan.com>
and subject line Re: Bug#611444: Enable syntax highlighting by default
has caused the Debian Bug report #611444,
regarding Enable syntax highlighting by default
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
611444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611444
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Mathieu Parent <math.parent at gmail.com>
Subject: Enable syntax highlighting by default
Date: Sat, 29 Jan 2011 14:46:19 +0100
Size: 3262
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110129/ca127f96/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: James Vega <jamessan at debian.org>
Subject: Re: Bug#611444: Enable syntax highlighting by default
Date: Sat, 29 Jan 2011 09:32:08 -0500
Size: 4602
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110129/ca127f96/attachment-0001.eml>

From jamessan at debian.org  Sat Jan 29 15:40:00 2011
From: jamessan at debian.org (James Vega)
Date: Sat, 29 Jan 2011 10:40:00 -0500
Subject: Bug#611444: Enable syntax highlighting by default
In-Reply-To: <20110129143208.GA30534@jamessan.com>
References: <20110129134619.6193.72656.reportbug@tourthieu.sathieu.net>
	<20110129143208.GA30534@jamessan.com>
Message-ID: <20110129154000.GB30534@jamessan.com>

On Sat, Jan 29, 2011 at 09:32:08AM -0500, James Vega wrote:
> tag 611444 wontfix
> thanks
> 
> On Sat, Jan 29, 2011 at 02:46:19PM +0100, Mathieu Parent wrote:
> > Please enable syntax highlighting by default.
> > 
> > This can be done by uncommenting the following line in /etc/vim/vimrc:
> > syntax on
> 
> You're more than welcome to do that in your own ~/.vimrc file or to
> modify /etc/vim/vimrc yourself (although I wouldn't recommend it) but
> that won't be done by the packaging.
> 
> Turning on syntax highlighting also enable filetype plugins and as
> described in /usr/share/doc/vim/NEWS.Debian.gz (quoted below) enabling
> this before the user's vimrc is sourced prevents the user from being
> able to change certain portions of Vim's behavior.
> 
>   Filetype plugins are no longer enabled by default because certain actions
>   (like preventing the loading of the default menus) *must* occur before
>   filetype detection is enabled.  By enabling filetype plugins (and detection)
>   in debian.vim, we were preventing the user from being able to make changes to
>   Vim's behavior.  Filetype plugins can be re-enabled via
>   "filetype plugin on".

As another data point:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/572627

-- 
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <jamessan at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110129/8fbf9e62/attachment.pgp>

From andreimpopescu at gmail.com  Sun Jan 30 15:46:49 2011
From: andreimpopescu at gmail.com (Andrei POPESCU)
Date: Sun, 30 Jan 2011 17:46:49 +0200
Subject: Bug#611544: ftplugin/po.vim: Patch to enhance handling of fuzzy
	strings with --previous msgid in po files
Message-ID: <20110130154649.2755.54080.reportbug@think.homelan>

Package: vim-scripts
Version: 20091011
Severity: wishlist
Tags: patch

Hello,

I tried to contact the upstream author regarding this patch, but I got 
no response. The diff part needs more work.

[sniped irrelevant system info]

Thanks,
Andrei
-------------- next part --------------
--- /usr/share/vim-scripts/ftplugin/po.vim	2009-10-11 19:24:05.000000000 +0300
+++ .vim/ftplugin/po.vim	2011-01-30 17:39:35.000000000 +0200
@@ -1,8 +1,8 @@
 " Vim ftplugin for PO file (GNU gettext) editing.
 " Maintainer:	Aleksandar Jelenak <ajelenak AT yahoo.com>
-" Last Change:	Tue, 12 Apr 2005 13:49:55 -0400
+" Last Change:	Tue, 30 Jan 2011 17:25:32 +0200
 "
-" *** Latest version: http://www.vim.org/scripts/script.php?script_id=695 ***
+" *** Based on the version at: http://www.vim.org/scripts/script.php?script_id=695 ***
 "
 " DESCRIPTION
 "     This file is a Vim ftplugin for editing PO files (GNU gettext -- the GNU
@@ -19,7 +19,7 @@
 "     Move to the next fuzzy translation              <S-F5>      \f
 "     Move to the previous fuzzy translation          <S-F6>      \b
 "     Label the translation fuzzy                     <S-F7>      \z
-"     Remove the fuzzy label                          <S-F8>      \r
+"     Remove the fuzzy label and previous msgid       <S-F8>      \r
 "     Show msgfmt statistics for the file(*)          <S-F11>     \s
 "     Browse through msgfmt errors for the file(*)    <S-F12>     \e
 "     Put the translator info in the header           \t          \t
@@ -36,7 +36,7 @@
 "     Move to the next fuzzy translation              <S-F5>      \f
 "     Move to the previous fuzzy translation          <S-F6>      \b
 "     Label the translation fuzzy                     <S-F7>      \z
-"     Remove the fuzzy label                          <S-F8>      \r
+"     Remove the fuzzy label and previous msgid       <S-F8>      \r
 "     Split-open the file under cursor                  gf        gf
 "     Show msgfmt statistics for the file(*)          <S-F11>     \s
 "     Browse through msgfmt errors for the file(*)    <S-F12>     \e
@@ -45,6 +45,10 @@
 "     ---------------------------------------------------------------
 "     (*) Only available on UNIX computers.
 "
+"     Command
+"     ===============================================================
+"     Use a hidden buffer to highlight changes        :DiffMsgid
+"
 "     Remarks:
 "     - "S" in the above key mappings stands for the <Shift> key and "\" in
 "       fact means "<LocalLeader>" (:help <LocalLeader>), which is "\" by
@@ -69,6 +73,10 @@
 "       program via the global variable 'g:po_msgfmt_args'. All arguments are
 "       allowed except the "-o" for output file. The default value is
 "       "-vv?-c".
+"     - The :DiffMsgid command works only if --previous was used with msgmerge
+"       (or equivalent options in other .po tools).
+"       TODO
+"       The substitute does not work for strings that are only one line
 "
 "     But there's even more!
 "
@@ -212,7 +220,7 @@
    endwhile
 endf
 
-" Remove fuzzy description from the translation.
+" Remove previous msgid and fuzzy flag.
 if !hasmapto('<Plug>RemoveFuzzy')
    if gui
       imap <buffer> <unique> <S-F8> <Plug>RemoveFuzzy
@@ -222,16 +230,12 @@
       nmap <buffer> <unique> <LocalLeader>r <Plug>RemoveFuzzy
    endif
 endif
-inoremap <buffer> <unique> <Plug>RemoveFuzzy <ESC>{vap:call <SID>RemoveFuzzy()<CR>i
-nnoremap <buffer> <unique> <Plug>RemoveFuzzy {vap:call <SID>RemoveFuzzy()<CR>
+inoremap <buffer> <unique> <Plug>RemoveFuzzy <ESC>{vap:call <SID>RemoveFuzzy()<CR>gv<ESC>}i
+nnoremap <buffer> <unique> <Plug>RemoveFuzzy {vap:call <SID>RemoveFuzzy()<CR>gv<ESC>}
 
-fu! <SID>RemoveFuzzy()
-   let line = getline(".")
-   if line =~ '^#,\s*fuzzy$'
-      exe "normal! dd"
-   elseif line =~ '^#,\(.*,\)\=\s*fuzzy'
-      exe 's/,\s*fuzzy//'
-   endif
+fu! <SID>RemoveFuzzy() range
+   execute ':''<,''>global/^#,\sfuzzy$\|^#|\s.*".*"$/d'
+   execute ':''<,''>s/,\s*fuzzy//e'
 endf
 
 " Show PO translation statistics. (Only available on UNIX computers for now.)
@@ -404,4 +408,33 @@
    endif
 endf
 
+" This copies everything to a new, hidden buffer, so we can use the builtin
+" diff capabilities of vim. Built on an idea of J?rgen Kr?mer from the vim
+" users mailing list
+fu! DiffPreviousString()
+    %yank
+    new
+    put!
+    " this replaces the current msgid with the old one, so that diff
+    " can highlight the changes. Currently doesn't work with
+    " msgids that are only in one (the first) line
+    " example:
+    " ------------------------
+    " #, fuzzy 
+    " #| msgid "previous text"
+    " msgid "new text"
+    " msgstr "translation"
+    "
+    " ------------------------
+    %s/^\(#| msgid ""\n\(\_.\{-\}\n\)msgid ""\n\)\(\_.\{-\}\n\)\(msgstr ""\)/\=submatch(1).substitute(submatch(2), '#| ', '', 'g').submatch(4)/
+    nohls
+    diffthis
+    hide
+    diffthis
+    set fdc=0
+    set nofen
+endf
+
+command DiffMsgid call DiffPreviousString()
+
 unlet gui

From ntyni at debian.org  Sun Jan 30 19:26:54 2011
From: ntyni at debian.org (Niko Tyni)
Date: Sun, 30 Jan 2011 21:26:54 +0200
Subject: Bug#611573: vim: missing dependency on libperl
Message-ID: <20110130192653.GA4073@madeleine.local.invalid>

Package: vim-gtk
Version: 2:7.3.035+hg~8fdc12103333-1
User: debian-perl at lists.debian.org
Usertags: perl-5.12-transition

When the vim Perl bindings were changed to dynamic loading, the packages
stopped depending on libperl5.10. I can see that a hard dependency may
not be wanted, but perhaps a recommendation or at least a suggestion
would be in order?

The lack of any dependency on libperl is going to be a problem when Perl
is upgraded to a newer upstream version, in particular with the upcoming
Perl 5.12 transition.

The full name of the library ends up in the vim.gtk binary, so the Perl
support stops working when the library changes to libperl5.12.3 (and it
probably would with a hypothetical 5.10.2 too, for that matter, even if
it was ABI compatible.)

While binNMUing vim will fix this, the package dependencies will not
indicate that in any way. This makes it rather easy for the release team
to miss the binNMU requirement altogether and consequently makes it more
difficult to keep track of the transition status.

As dpkg-shlibdeps can not help here and I can't see an obviously clean
and correct solution, perhaps it would be OK to cheat a bit and do
something like

 Recommends: libperl5.10
 Depends: perl-base (>= 5.10.1-17), perl-base (<< 5.10.2~)

in a binNMU safe way? The alternatives I see are worse, such as

 Recommends: libperl5.10
 Conflicts: libperl5.10 (<< 5.10.1-17), libperl5.10 (>= 5.10.2~), libperl5.12

which doesn't even work if we reach libperl5.14 for wheezy.

OTOH, if we do allow a hard dependency on libperl it comes down to

 Depends: libperl5.10 (>= 5.10.1-17), libperl5.10 (<< 5.10.2~)

which would probably be my preferred solution.

Please let me know what you think. I can try to come up with a patch
once I know your preference.

I wonder if this applies to the other interpreters like Python too?
-- 
Niko Tyni   ntyni at debian.org




From jamessan at debian.org  Sun Jan 30 23:01:08 2011
From: jamessan at debian.org (James Vega)
Date: Sun, 30 Jan 2011 18:01:08 -0500
Subject: Bug#611573: vim: missing dependency on libperl
In-Reply-To: <20110130192653.GA4073@madeleine.local.invalid>
References: <20110130192653.GA4073@madeleine.local.invalid>
Message-ID: <AANLkTimHVyWczYKwHpTcwvytxUXGWXkz0GZaX1gcjRWD@mail.gmail.com>

On Sun, Jan 30, 2011 at 2:26 PM, Niko Tyni <ntyni at debian.org> wrote:
> When the vim Perl bindings were changed to dynamic loading, the packages
> stopped depending on libperl5.10. I can see that a hard dependency may
> not be wanted, but perhaps a recommendation or at least a suggestion
> would be in order?

Yeah, I've been intending to add some indication that the libraries for
the language bindings should be installed.  Recommends would probably be
good since it'll make sure the libraries are installed in the common
case but allow people who want control over it to remove them.

> The lack of any dependency on libperl is going to be a problem when Perl
> is upgraded to a newer upstream version, in particular with the upcoming
> Perl 5.12 transition.
>
> The full name of the library ends up in the vim.gtk binary, so the Perl
> support stops working when the library changes to libperl5.12.3 (and it
> probably would with a hypothetical 5.10.2 too, for that matter, even if
> it was ABI compatible.)

Hmm, would it make sense to try and change this so it only uses the name
libperl5.10 instead of libperl5.10.1?

> While binNMUing vim will fix this, the package dependencies will not
> indicate that in any way. This makes it rather easy for the release team
> to miss the binNMU requirement altogether and consequently makes it more
> difficult to keep track of the transition status.
>
> As dpkg-shlibdeps can not help here and I can't see an obviously clean
> and correct solution, perhaps it would be OK to cheat a bit and do
> something like
>
> ?Recommends: libperl5.10
> ?Depends: perl-base (>= 5.10.1-17), perl-base (<< 5.10.2~)

Well, the intention of switching to dynamic loading of the language
binding libraries was to allow people not to install them.  As such, I'd
prefer not to require that users have to install related packages even
if they choose not to install the language binding.

Maybe I could build a throwaway version of Vim with the language
bindings built-in so dpkg-shlibdeps can do its detection and then use
that information for the Recommends?  Would that be sufficient for
whatever mechanism determines that packages should be binNMUed for
library transitions pick up Vim?

I'd be interested in how other packages which do dynamic loading of
libraries handle this situation.

> I wonder if this applies to the other interpreters like Python too?

I'd assume it applies to all of the bindings whenever they need a
transition.  I'd be surprised if this is the first package to do dynamic
loading and need binNMUs when the library it loads changes.  Maybe we
can find precedent somewhere else?

-- 
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <jamessan at debian.org>