Re: emacs lilypond-mode and the midi command

[James E. Bailey]

On 07.03.2009, at 23:44, Tim McNamara wrote:

> > On Mar 7, 2009, at 4:05 AM, James E. Bailey wrote:
> >
> > > On OSX, the lilypond mode for emacs doesn't properly escape  
> > > filenames.
> > > open -a 'Mighty MIDI' /Users/jamesebailey/Documents/James Music/ 
> > > Choral Music/Windhauch/Windhauch.midi
> > > 2009-03-07 10:59:31.767 open[465] No such file: /Users/ 
> > > jamesebailey/Documents/James
> >
> > I'm having trouble making sense of what you are trying to do with  
> > this command and from where you are trying to do it.
>
> <snip>
>
> Addendum:  I was able to replicate this bheavior in Bash under  
> Terminal.  The problem appears to be how Bash handles spaces in  
> filenames.  Weird, in this day and age you'd think that shells  
> would be intelligent enough to cope with this.  There is a new  
> revision of Bash out in the past few weeks, which perhaps gets  
> around this.  I wonder if lilypond-mode is for some reason calling  
> to the shell and running into a problem there; IMO it shouldn't, it  
> should use the standard Emacs commands.
>
> If double quotes are put around the path, that seems to properly  
> escape them, although even this was flakey on my Mac:
>
>     "/Users/jamesebailey/Documents/James Music/Choral Music/ 
> Windhauch/Windhauch.midi"
>
> Another option might be:
>
>      /Users/jamesebailey/Documents/"James Music"/"Choral Music"/ 
> Windhauch/Windhauch.midi
>
> Even then I am not sure that this will open in Emacs with this syntax.

*I* can send this command to bash through emacs just fine. The  
problem is that I don't know how to change the way the command is  
sent through lilypond-mode. And, as previously stated, this was a  
problem with the way lilypond opened pdf's, maybe I'll see if I can  
apply that fix to the midi...