9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Plan9Ports libdraw open-in-same-window
Date: Thu,  9 Mar 2006 13:36:12 -0800	[thread overview]
Message-ID: <DBEDD72A-0D90-4D69-A59E-9B22B3D39D13@telus.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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"
command, and it all seems to work pretty well, at least with rio as
my WM (my window program isn't ICCCM compliant, and I really don't
know or want to know enough X11 to fix it).  I'm also using a little
hack new-namespace script to generate new namespaces on demand and
propagate the parent namespace sockets to it (thanks to Eric
Quanstrom for the suggestion on how to make them nicely
hierarchical).  Does anybody want these?  I'd love for someone with a
different usage pattern than me to try them out.

On a possibly related note, I use synergy to manage my mouse pointer
from my mac to my linux box (which is running my dev environment).
Every time I switch screens it propagates my cut buffer to X11.
Sometimes the buffer contains object acme doesn't understand, and it
generates an error message.  If the window those messages are going
to isn't set to scroll it eventually freezes until I scroll down or
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.)

Paul

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEEJ/MpJeHo/Fbu1wRArV1AJ9EX7zHXKye0NADu52X5f9msWaJlACfcTWJ
/r4r8FGNTDuZBT719adglDQ=
=ceOP
-----END PGP SIGNATURE-----


             reply	other threads:[~2006-03-09 21:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 21:36 Paul Lalonde [this message]
2006-03-09 21:40 ` Russ Cox
2006-03-09 22:21   ` Paul Lalonde
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=DBEDD72A-0D90-4D69-A59E-9B22B3D39D13@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).