GNOME Bugzilla – Bug 597890
wrong argument passing to Meld with dirnames containing white spaces
Last modified: 2009-10-17 12:52:54 UTC
using synchronize Directories fails when the pathes contain white spaces Error Message is produced by Meld then...
just confirmed it myself again...without white spaces it works fine
What version of gcmd? And what's your setup for differ (Settings...|Programs|Diff)?
Gnome Commander Version was 1.2.5 installed from Ubuntu Repository for Ubuntu 8.04LTS differ is configured as meld %s today I updated to 1.2.8 (compiled from source) - I will test if bug still exists and report later
now updated to GCMDer 1.2.8 Path1: ~/workspace = /home/danny/workspace Path2: /media/disk/Dokumente und Einstellungen/Danny/workspace Meld answers with Error Message "Wrong number of Arguments (found 4)" suppose the whitespaces are handled wrong the 2 pathes will split up like this: /home/danny/workspace /media/disk/Dokumente und Einstellungen/Danny/workspace and now we have 4 Arguments!
Could you, please, run gcmd from terminal and attach the output when comparing files with white spaces in the path?
danny@PC01Linux:~$ gnome-commander (gnome-commander:10916): Gtk-WARNING **: unable to find signal handler for object(GnomeCmdDir:0x845c218) with func(0x809b530) and data(0x8325d68) (gnome-commander:10916): Gtk-WARNING **: unable to find signal handler for object(GnomeCmdDir:0x845c218) with func(0x809b1d0) and data(0x8325d68) (gnome-commander:10916): Gtk-WARNING **: unable to find signal handler for object(GnomeCmdDir:0x845c218) with func(0x809c660) and data(0x8325d68) (gnome-commander:10916): Gtk-WARNING **: unable to find signal handler for object(GnomeCmdDir:0x845c218) with func(0x8097e00) and data(0x8325d68) »meld /media/disk/Dokumente und Einstellungen/Danny/workspace /home/danny/workspace« wird ausgeführt
Created attachment 145230 [details] [review] Bug 597890.patch Please verify if the attached patch is working for you.
sorry for asking - how to apply the patch? I normaly only code for myself and do not need patching :-)
patch -p1 < 'Bug 597890.patch' in your src root dir
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.