From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <14ec7b180804061425p6a5afb03waaea3f2ad18db5ef@mail.gmail.com> Date: Sun, 6 Apr 2008 15:25:26 -0600 From: "andrey mirtchovski" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <14ec7b180804061352w3147f35fs6e14e7ceca61751d@mail.gmail.com> Subject: Re: [9fans] OSX Drawterm hangs on close Topicbox-Message-UUID: 89b1f0ac-ead3-11e9-9d60-3106f5b1d025 no, they should go to the program, since it's the one that set up the listener, et al. the applescript does the equivalent of opening the terminal and running a program in it, with keyboard and mouse events going directly to the program. besides, i haven't used the script in years, preferring to start from the terminal instead. On Sun, Apr 6, 2008 at 3:22 PM, Skip Tavakkolian <9nut@9netics.com> wrote: > wouldn't the appleevents go to the drawterm applescript you > and Paul posted a while back? this one: > > do shell script "cd ~ && drawterm -a somebox -c somebox" > > so maybe the applescript needs to field or forward those? > > > > > i've lost my notes on this, but basically you need to figure out why > > the drawterm Carbon event handlers are not being called. it could be a > > configuration option that we're not setting or something more > > sinister. i don't know enough osx to be able to say. > > > > another manifestation of the same bug which may be easier to debug, is > > when you do apple-Q while in full-screen mode. the apple-q never > > arrives at the keyboard handler for drawterm and consequently the code > > never does a proper "exit". what's the difference between fullscreen > > and windowed mode according to OSX is beyond me. > > > > i'm sorry, i know this doesn't help much. > > >