9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] OSX Drawterm hangs on close
Date: Sun,  6 Apr 2008 15:25:26 -0600	[thread overview]
Message-ID: <14ec7b180804061425p6a5afb03waaea3f2ad18db5ef@mail.gmail.com> (raw)
In-Reply-To: <fdaa5df1d850283d74934f57417963bd@9netics.com>

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.
>
>
>


  reply	other threads:[~2008-04-06 21:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06  3:06 Michaelian Ennis
2008-04-06  3:15 ` andrey mirtchovski
2008-04-06  3:16   ` erik quanstrom
2008-04-06  3:44     ` andrey mirtchovski
2008-04-06 20:07       ` Michaelian Ennis
2008-04-06 20:52         ` andrey mirtchovski
2008-04-06 21:22           ` Skip Tavakkolian
2008-04-06 21:25             ` andrey mirtchovski [this message]
2008-04-08 13:34     ` Anant Narayanan
2008-04-08 14:32       ` Jeff Sickel
2008-04-08 20:27         ` Pietro Gagliardi
2008-04-08 21:09           ` Skip Tavakkolian
2008-06-24  8:29             ` underspecified
2008-06-24 12:51       ` Uriel
2008-06-24 13:17         ` Pietro Gagliardi
2008-06-24 13:23           ` Bruce Ellis
2008-06-24 13:24           ` sqweek
2008-06-24 13:36             ` erik quanstrom
2008-06-24 13:25           ` a
2008-06-24 13:28           ` Francisco J Ballesteros
2008-06-24 13:17         ` Bruce Ellis
2008-06-24 17:24         ` Russ Cox
2008-06-24 17:45         ` matt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14ec7b180804061425p6a5afb03waaea3f2ad18db5ef@mail.gmail.com \
    --to=mirtchovski@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).