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: Thu, 21 Nov 2013 09:54:09 -0600 [thread overview]
Message-ID: <5B64D4F5-E822-46FA-8FD2-62CA6B3F1AF2@corpus-callosum.com> (raw)
In-Reply-To: <CAGGHmKF57Uf+bUxJf8nM3vER6oH8qmVVN-=aykMGgCw1cFJVKg@mail.gmail.com>
Just don’t upgrade to 10.9 yet:
http://support.apple.com/kb/HT5293?viewlocale=en_US&locale=en_US
http://xquartz.macosforge.org/landing/
You can install XQuartz and keep going, but the upgrade from
earlier releases does delete X11 rather ruthlessly.
-jas
On Nov 21, 2013, at 9:03 AM, Steven Stallion <sstallion@gmail.com> wrote:
> On Thu, Nov 21, 2013 at 4:40 AM, Mark van Atten <vanattenmark@gmail.com> wrote:
>> For the moment, I prefer this to drawterm-cocoa because there is no
>> flicker, and window borders remain intact when reshaping with B1 or
>> B2.
>
> Ah! That drives me nuts too, though it is nice to get proper
> fullscreen support. I've submitted a patch to rio that disables the
> resizing on sources. Take a look at patch/rio-noresize. After that,
> just start rio with -R. It's a hack, but it serves my sanity quite
> well!
>
> Steve
>
next prev parent reply other threads:[~2013-11-21 15:54 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 [this message]
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
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=5B64D4F5-E822-46FA-8FD2-62CA6B3F1AF2@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).