From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] drawterm osx-x11 on x86_64
Date: Mon, 25 Nov 2013 10:12:32 -0600 [thread overview]
Message-ID: <70705F39-42AB-4CAA-A63D-98D5D9D94DF3@corpus-callosum.com> (raw)
In-Reply-To: <CALAsyW2yF9z820cWZw+q_FuYfF14kTDy+4nWvhMrPBx27Nmo2w@mail.gmail.com>
On Nov 22, 2013, at 3:18 AM, Mark van Atten <vanattenmark@gmail.com> wrote:
> Well, I wrote `the current sources', but that was wrong: I just
> checked bitbucket again and saw your commits of the last few hours. So
> I pulled the updates and rebuilt. To my surprise, the phenomena remain
> exactly the same. This time I got a message though:
rio flickers natively, you just have to be on a really slow machine
to see it. Or in this case a slow cpu server (virtualbox) or a slow
network connection to the cpu server (wifi to a remote site in my case).
The recent drawterm-cocoa changes clean up full screen changes.
> objc[3785]: Object 0x7fb261297930 of class NSConcreteMapTable
> autoreleased with no pool in place - just leaking - break on
> objc_autoreleaseNoPool() to debug
This morning’s push you get rid of that autoreleasepool warning.
next prev parent reply other threads:[~2013-11-25 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 10:40 Mark van Atten
2013-11-21 14:58 ` Jeff Sickel
2013-11-21 15:16 ` erik quanstrom
2013-11-21 15:03 ` Steven Stallion
2013-11-21 15:54 ` Jeff Sickel
2013-11-22 0:02 ` Jeff Sickel
2013-11-22 9:05 ` Mark van Atten
2013-11-22 9:18 ` Mark van Atten
2013-11-25 16:12 ` Jeff Sickel [this message]
2013-11-25 17:44 ` Mark van Atten
2013-11-26 14:36 ` Mark van Atten
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=70705F39-42AB-4CAA-A63D-98D5D9D94DF3@corpus-callosum.com \
--to=jas@corpus-callosum.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).