Oh, I know the parsing itself is trivial in _that_ example. My point was that the Exec string varies according to how the binary is to be called. Some examples on my system:
nautilus --no-desktop burn:/// ooffice -draw %U firefox %u yelp ghelp xdg-open ~/.wine/drive_c My guess is that these will also vary from system to system and with time. As you can see, it is not always the case that the binary name is in the last part of the string or any other standard location that would guarantee a match. What would essentially amount to hacking it to find all existing (and future?) formats of these will most definitely only work for a subset of the indexed items out there. I don't know, maybe I'm just being too picky, do you think that having only some of these working is an acceptable compromise? -- J. Carlos Navea On Sun, Sep 14, 2008 at 9:15 PM, Alex Launi <[EMAIL PROTECTED]> wrote: > It should be trivial to parse out the last part of that string. Just find > the space (if there is even one, for the case where the binary has > arguments) after the last / and chop out what's in the middle, that should > be the binary name. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en -~----------~----~----~----~------~----~------~--~---
