Hi Mario, Some followup questions: Could you try to launch the file command in the same way you would launch mhwaveedit, i.e.:
file "name with spaces.wav" and see if that works. Also, to make sure you are actually launching the program and not some alias or shell script wrapper, could you try these commands in a terminal: which mhwaveedit ls -l `which mhwaveedit` Best regards, Magnus Mario Vano wrote: > Magnus Hjorth wrote: >> Hi Mario, >> >> This sounds strange, because I open and save files with spaces in their >> names all of the time and never had any problems. > > I do too, but the problem does not occur from inside the file open and > save dialogs - it only happens with files passed in from shells. > There's no problem at all from inside mhwaveedit. > >> >> First, what happens when you open the file. Does the program say "file >> not found", or is it something else? > > I can repeatably create the problem like this on Debian Etch with all > normal updates running mhwaveedit 1.4.9-1 (as supplied by Debian). > > I am using a known good wave file > > /home/mvano/sessions/orange/live/export/export.wav > > I open a terminal window in the directory containing that file and > copy the file to a file named: > > /home/mvano/sessions/orange/live/export/name with spaces.wav > > I then try to pass it to mhwaveedit from the terminal window by using > command completion to escape the file name, with either command: > > mhwaveedit name\ with\ spaces.wav > > or > > mhwaveedit "name with spaces.wav" > > > A gnome error box appears that says: > > The file /home/mvano/sessions/orange/live/export/name does not exist! > > once I click OK, then another gnome error box appears that says: > > The file /home/mvano/sessions/orange/live/export/with does not exist! > > Then an empty mhwaveedit window appears behind that. > > once I click OK, then another gnome error box appears that says: > > The file /home/mvano/sessions/orange/live/export/spaces.wav does not > exist! > > Then another empty mhwaveedit window appears > > clicking on OK dismisses the message but does nothing more. > > Closing any of the empty windows causes mhwaveedit to quit. > > No error messages are sent to the terminal that launched mhwaveedit. > > The same thing happens opening that file from nautilus. > > The file can be opened just fine by starting mhwaveedit from the > desktop menus, and then using the open command to browse to it and > open it with the gnome standard file dialog. > > The same thing happens with any wave file in a locally mounted windows > volume if it's in a directory like "My Documents". A space anywhere in > the path breaks the name into multiple arguments. > > From what you are saying, I'm guessing that this is a screwup > associated with the Debian Etch package. However, It's nearly > impossible to build local versions of audio software dependent on jack > or many other libraries that will work with the rest of the Debian > audio packages because of their loony changes to library and file > names. It's hard to believe that this still open source software, > since it's nearly impossible to build local variants any more. > > If you can't duplicate this problem any other way, I can try to build > a private local version for testing only and see if I can learn more. > > thanks again, > > Mario > > _______________________________________________ Mhwaveedit-discuss mailing list [email protected] https://mail.gna.org/listinfo/mhwaveedit-discuss
