On Thu, Jun 18, 2009 at 03:46:16PM +0200, Ivan Čukić wrote:
> I have no idea why that doesn't work for me then. It also appears in stable 
> debian (zsh 4.3.6).

4.3.6 did not have the fix; the version you reported the bug against does.
Are you sure it's doing something wrong in 4.3.10?

> I've attached my .zshrc file.
> 
> > Where are you adding a backslash in zsh-mime-setup?
> there are two places with the following line wrapped (as if the file was 
> edited with automatic hard word wrapping enabled)
>    print -r " ... $line" >&2
> 
> In the case of zsh-mime-setup, I just removed the line break instead of 
> adding 
> backslashes.
> 
> The first is line 290:
> 290 »·······  print -r " handler for type $type:
> 291   $line" >&2
> 
> And the second is 302:
> 302 »·······print -r "Skipping handler for already defined type $type:
> 303   $line" >&2

This seems like a low-risk solution.

Index: Functions/MIME/zsh-mime-setup
===================================================================
RCS file: /cvsroot/zsh/zsh/Functions/MIME/zsh-mime-setup,v
retrieving revision 1.7
diff -u -r1.7 zsh-mime-setup
--- Functions/MIME/zsh-mime-setup       20 Nov 2008 18:12:32 -0000      1.7
+++ Functions/MIME/zsh-mime-setup       18 Jun 2009 14:08:30 -0000
@@ -293,8 +293,8 @@
          else
            print -r "Adding" >&2
          fi
-         print -r " handler for type $type:
-  $line" >&2
+         print -r " handler for type $type:" >&2
+         print -r "  $line" >&2
        fi
        type_handler_map[$type]=$line
        type_flags_map[$type]=$flags
@@ -305,8 +305,8 @@
          print -r "  with flags $flags" >&2
        fi
       elif [[ -n $o_verbose ]]; then
-       print -r "Skipping handler for already defined type $type:
-  $line" >&2
+       print -r "Skipping handler for already defined type $type:" >&2
+       print -r "  $line" >&2
        if [[ -n $flags ]]; then
          print -r " with flags $flags" >&2
        fi



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to