From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan9Ports libdraw open-in-same-window
Date: Thu, 9 Mar 2006 14:21:47 -0800 [thread overview]
Message-ID: <27850944-1541-4254-8F51-31D4FD5B741E@telus.net> (raw)
In-Reply-To: <26acc9fbc3bcba8d124b9496c3d7a99a@swtch.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I don't know what you mean by even when not using 9term. For an
example of use: in a win in acme I call perforce with EDITOR=sam; sam
takes over my acme window until I'm done, as expected. Can you give
me an example?
I didn't go hack a rio to run in a window, though - it's not a
libdraw tool under p9p.
The acme errors that spew are of the flavour:
/home/plalonde/plan9/bin/acme: cannot handle selection request for
'text/plain;charset=UTF-8' (239)
and happen when X11 gets a selection passed to it by synergy (the
multi-computer mouse/keyboard sharing tool).
Paul
On 9-Mar-06, at 1:40 PM, Russ Cox wrote:
>> I have a patch to libdraw that makes graphical applications open in
>> the window that invoked them, as in Plan 9. I've added a "window"
>
> Even if you're not using a 9term to invoke them?
>
>> make the window scroll. What's the right way to fix that? (this is
>> particularly disastrous if you opened acme in the 9term window this
>> output is going to - there is no way to set the 9term to scroll, and
>> it won't let me save my work.)
>
> Presumably there should be a way to make 9term scroll
> while its window has been taken over. But you could
> just silence the error message instead. What is generating
> the error message?
>
> Russ
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEEKp7pJeHo/Fbu1wRAv6aAKCuvWGc5KiRo3NvpVxk2XjsXgOogQCdETOs
TbrNt+ibVcAFDaGLv4ZcNk4=
=yJFB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-03-09 22:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 21:36 Paul Lalonde
2006-03-09 21:40 ` Russ Cox
2006-03-09 22:21 ` Paul Lalonde [this message]
2006-03-10 0:38 ` Russ Cox
2006-03-10 1:00 ` Paul Lalonde
2006-03-10 1:14 ` Russ Cox
2006-03-10 3:15 ` Paul Lalonde
2006-03-10 3:34 ` Russ Cox
2006-03-10 4:26 ` Paul Lalonde
2006-03-10 3:35 ` Russ Cox
2006-03-10 6:50 ` Bruce Ellis
2006-03-10 14:25 ` Russ Cox
2006-03-10 13:55 ` erik quanstrom
2006-03-10 14:29 ` Russ Cox
2006-03-10 14:53 ` erik quanstrom
2006-03-10 15:03 ` Russ Cox
2006-03-10 15:21 ` erik quanstrom
2006-03-10 15:26 ` Russ Cox
2006-03-10 17:08 ` erik quanstrom
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=27850944-1541-4254-8F51-31D4FD5B741E@telus.net \
--to=plalonde@telus.net \
--cc=9fans@cse.psu.edu \
/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).