9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mark van Atten <vanattenmark@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] once more: drawterm osx-x11 on x86-64
Date: Fri, 27 Feb 2015 01:00:24 +0100	[thread overview]
Message-ID: <CALAsyW0=a0Py+nkRbXv1WV08irO1_HdQeTHE3WeE7q+aBv8f-w@mail.gmail.com> (raw)

A while ago, I reported on a problem I had with flicker and broken window edges
in drawterm-cocoa CONF=osx-x11. See the email copied below. It led to a brief
exchange.

With my present configuration, that problem remains:
OSX 10.9.5
drawterm-cocoa 2014-12-02

However, I just tried rsc's drawterm 2013-07-02,
and there the problem is absent.

I take it there are not many users of drawterm on OSX,
either jas' or rsc's distribution, who
use the x11 version -- are there? I'd be interested
to compare notes.

Best wishes,
Mark.



From: Mark van Atten <vanattenmark@gma...>
Subject: drawterm osx-x11 on x86_64
Date: Thu, 21 Nov 2013 11:40:14 +0100

For the record---to compile drawterm
(http://code.google.com/p/drawterm/) with CONF=osx-x11 on x86_64 (in
my case running 10.8.5), just add the required substitution to the
makefile:

Make.osx-x11

20 - arch=`uname -m|sed 's/i.86/386/;s/Power Macintosh/power/'`; \
20 + arch=`uname -m|sed 's/i.86/386/;s/Power
Macintosh/power/;s/x86_64/amd64/'`; \

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.

Mark.



             reply	other threads:[~2015-02-27  0:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27  0:00 Mark van Atten [this message]
2015-02-27 22:40 ` Mark van Atten
2015-02-27 23:10 ` Jeff Sickel
2015-02-27 23:27   ` Mark van Atten
2015-02-28  1:19     ` Jeff Sickel
2015-02-28  2:14       ` Steven Stallion
2015-02-28  8:07         ` cinap_lenrek
2015-02-28  8:13           ` lucio
2015-02-28  8:18             ` cinap_lenrek
2015-02-28  8:29               ` Bakul Shah
2015-03-02  7:55                 ` erik quanstrom
2015-03-02  8:47                   ` Steve Simon
2015-02-28  9:17       ` Mark van Atten
2015-02-28  0:39   ` yy
2015-02-28  1:09   ` Sean Hinchee
2015-02-28  1:35     ` Jeff Sickel
2015-02-28 18:05 sl
2015-02-28 18:29 ` Bakul Shah
2015-03-10 17:32 michaelian ennis

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='CALAsyW0=a0Py+nkRbXv1WV08irO1_HdQeTHE3WeE7q+aBv8f-w@mail.gmail.com' \
    --to=vanattenmark@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).