Changes between Initial Version and Version 1 of Ticket #2784, comment 3


Ignore:
Timestamp:
03/23/2017 11:13:48 AM (6 years ago)
Author:
dashbad
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2784, comment 3

    initial v1  
    1 I have come across this bug because my execute script is failing on Linux, because Ampersands are being escaped to ^^^&. 
     1I have come across this bug because my execute script is failing on Linux, because Ampersands are being escaped to  
     2{{{ 
     3^^^& 
     4}}} 
     5 
    26 
    37Steps to reproduce: 
    48 
    591. Write bash script: 
    6  
     10{{{ 
    711#!/bin/bash 
    812exec 1> >(logger -s -t $(basename $0)) 2>&1 
    913export name="$1" 
    1014echo $name 
    11  
     15}}} 
    12162. Set script as execute script 
    13173. Trigger script for a torrent with an ampersand in the name 
    1418 
    15 The syslog shows that the ampersand in the name has been converted to ^^^& 
     19The syslog shows that the ampersand in the name has been converted to  
     20{{{ 
     21^^^& 
     22}}} 
    1623 
    17 Can this change be rolled back/modified so it doesn't impact non-Windows users. 
     24Can this change be rolled back/modified so it doesn't impact non-Windows users?