Pat Thoyts <patthoyts@xxxxxxxxx> wrote:
> On 6 June 2013 09:17, Stefan Haller <stefan@xxxxxxxxxxxxxxxx> wrote:
> > +## On Mac, bring the current Wish process window to front
> > +
> > +if {[tk windowingsystem] eq "aqua"} {
> > + exec osascript -e [format {
> > + tell application "System Events"
> > + set frontmost of processes whose unix id is %d to true
> > + end tell
> > + } [pid] ]
> > +}
>
> Seems fine to me. I can't test this as I have no access to this
> platform. Possibly you should run this in a catch statement so it can
> ignore any errors and I would tend to use the 'auto_execok' command to
> ensure that osascript actually exists. Something like
>
> set arg [format {tell application......}]
> catch {exec {*}[auto_execok osascript] -e $arg [pid]}
>
> but possibly this is guaranteed to exist on all macs which would make
> the above redundant. What I'm thinking is you dont want the app to
> exit just because something goes wrong in this call.
I don't think we need auto_execok here, as osascript is available on
every Mac system. We might even specify the exact path, it's always
/usr/bin/osascript. Is that preferable?
I agree that "catch" might be a good idea though. It raises two
questions though:
1) Should we make the same change in gitk then? It already has the same
code without the catch (released in 1.8.3 already, btw).
2) Should we think about some way of sharing code between gitk and
git gui, so that these kinds of changes don't have to be made twice?
--
Stefan Haller
Berlin, Germany
http://www.haller-berlin.de/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html